Would it make sense to have something easier to configure that recompiling
postgresql and managing a custom executable, say a block size that could be
configured from initdb and/or postmaster.conf, or maybe per-object settings
specified at creation time?
I love the idea of per-object block size setting according to expected workload;
My 0.02¤: wait to see whether the idea get some positive feedback by core
people before investing any time in that...

The per object would be a lot of work. A per initdb (so per cluster)
setting (block size, wal size...) would much easier to implement, but it
impacts for storage format.
large tables, larger block size may have less pain than interruption per 8KB
boundary to switch the block being currently focused on, even though random
access via index scan loves smaller block size.
Yep, as Tom noted, this is really workload specific.

--
Fabien.
From pgsql-hackers-owner@postgresql.org Fri Aug 23 11:43:33 2013
Received: from makus.postgresql.org ([2001:4800:7903:4::125])
  by malur.postgresql.org with esmtp (Exim 4.80)
  (envelope-from <pavel.stehule@gmail.com>)
  id 1VCpm9-0007AN-1h
  for pgsql-hackers@postgresql.org; Fri, 23 Aug 2013 11:43:33 +0000
Received: from mail-ea0-x22a.google.com ([2a00:1450:4013:c01::22a])
  by makus.postgresql.org with esmtp (Exim 4.80)
  (envelope-from <pavel.stehule@gmail.com>)
  id 1VCpm1-0002Og-KK
  for pgsql-hackers@postgresql.org; Fri, 23 Aug 2013 11:43:32 +0000
Received: by mail-ea0-f170.google.com with SMTP id h14so244068eak.15
         for <pgsql-hackers@postgresql.org>; Fri, 23 Aug 2013 04:43:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
         d=gmail.com; s=20120113;
         h=mime-version:in-reply-to:references:from:date:message-id:subject:to
          :cc:content-type;
         bh=ojC7xjvr7YMCgauhA9Lht038/8idVT3Jrh9PS4Xwf8o=;
         b=P9RS97KDMquTCQwtjJLVNUcyK0A5Acj4FcND07FUOeaFHEs7cumt8uqKzLWRzDTEfA
          w9ZT5QeS0qn52TOtmobpvTVveWLuMedywdS6aT/4w8OOmVc5LukAxuF3RZPiBGthowRl
          cwGQwbB5dcOFG1m1WwW7CD6k4ae2qXXfGLsY+Uhg0A9mihImzmoofGvrWNH5T7b9f5YZ
          FXXlscbjzPIuXuDAxzYmpdCDyCs/sKQfqomHufR4X9Xzw02dagFNCN1MB2upqWyAdVGr
          DsETiEMlw5ZuqOfNmB5yvoFwL2UVxOUpiYO/DjpfwFDz+X+GXK4DR9wPXsnrlK9pbymC
          uKmQ==
X-Received: by 10.14.219.198 with SMTP id m46mr25553575eep.41.1377258204468;
  Fri, 23 Aug 2013 04:43:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.14.143.196 with HTTP; Fri, 23 Aug 2013 04:42:44 -0700 (PDT)
In-Reply-To: <52171f0c.4060301@joh.to>
References: <5214b268.3070303@joh.to> <4264.1377094931@sss.pgh.pa.us>
  <cahyxu0wcj2eheyswdqxzqffxae35xlmeikg_whdr39fjrrhxga@mail.gmail.com>
  <5214d7c0.1000204@joh.to> <CAHyXU0x2VAitPRUTPst7rkjULyagdYDo1yS6Py+=+Db+rgvvxw@mail.gmail.com>
  <6656.1377100039@sss.pgh.pa.us> <cahyxu0xl=bgq2sav7ixsde5u3ntoohnl_gm3sr3-c3o7ha0vjq@mail.gmail.com>
  <CAFj8pRDFHqv7cKXP-K+ubzw6627hytt7bct4zxdbselxc1rcgg@mail.gmail.com>
  <521613df.60608@joh.to> <CAFj8pRA66rUnNemi_cwskVOhjCORLcgky=js3+D+ygsueft09w@mail.gmail.com>
  <52171f0c.4060301@joh.to>
From: Pavel Stehule <pavel.stehule@gmail.com>
Date: Fri, 23 Aug 2013 13:42:44 +0200
Message-ID: <CAFj8pRB121jGSdz-BzSiwFcLbATHxb5j7jot4FediQ+8qyrpua@mail.gmail.com>
Subject: Re: PL/pgSQL, RAISE and error context
To: Marko Tiikkaja <marko@joh.to>
Cc: Merlin Moncure <mmoncure@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>,
  Pgsql Hackers <pgsql-hackers@postgresql.org>
Content-Type: multipart/alternative; boundary=047d7b60399c0aba9d04e49bea6f
X-Pg-Spam-Score: -2.0 (--)
X-Archive-Number: 201308/1024
X-Sequence-Number: 232589

--047d7b60399c0aba9d04e49bea6f
Content-Type: text/plain; charset=UTF-8

2013/8/23 Marko Tiikkaja <marko@joh.to>
On 8/23/13 8:38 AM, Pavel Stehule wrote:

2013/8/22 Marko Tiikkaja <marko@joh.to>
I like the idea, but I think this should be a new verbosity level. With
this patch you would have to go full VERBOSE just to debug PL/pgSQL code
with NOTICEs and DEBUGs in it, and that output then becomes harder to
parse
with the useless C-code information.
do you prepare patch ?
I should have the time to produce one for the September commitfest, but if
you (or anyone else) want to work on this, I won't object.

My opinion at this very moment is that we should leave the the DEFAULT
verbosity alone and add a new one (call it COMPACT or such) with the
suppressed context for non-ERRORs.

The name is not important. What I would, for DEFAULT verbosity, to see a
context when RAISE EXCEPTION is used. It is a bug now, I think

Regards

Pavel


Regards,
Marko Tiikkaja
--047d7b60399c0aba9d04e49bea6f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">2013/8/23 Marko Tiikkaja <span dir=3D"ltr">&lt;<a href=3D"mailto:ma=
rko@joh.to" target=3D"_blank">marko@joh.to</a>&gt;</span><br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">

On 8/23/13 8:38 AM, Pavel Stehule wrote:<div class=3D"im"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
2013/8/22 Marko Tiikkaja &lt;<a href=3D"mailto:marko@joh.to" target=3D"_bla=
nk">marko@joh.to</a>&gt;<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I like the idea, but I think this should be a new verbosity level. =C2=A0Wi=
th<br>
this patch you would have to go full VERBOSE just to debug PL/pgSQL code<br=
>
with NOTICEs and DEBUGs in it, and that output then becomes harder to parse=
<br>
with the useless C-code information.<br>
<br>
</blockquote>
<br>
do you prepare patch ?<br>
</blockquote>
<br></div>
I should have the time to produce one for the September commitfest, but if =
you (or anyone else) want to work on this, I won&#39;t object.<br>
<br>
My opinion at this very moment is that we should leave the the DEFAULT verb=
osity alone and add a new one (call it COMPACT or such) with the suppressed=
  context for non-ERRORs.<br></blockquote><div><br><br></div><div>The name=
=C2=A0 is not important. What I would, for DEFAULT verbosity, to see a cont=
ext when RAISE EXCEPTION is used. It is a bug now, I think<br>

<br></div><div>Regards<br><br></div><div>Pavel<br></div><div>=C2=A0</div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">
<br>
<br>
Regards,<br>
Marko Tiikkaja<br>
</blockquote></div><br></div></div>

--047d7b60399c0aba9d04e49bea6f--

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 7 of 11 | next ›
Discussion Overview
grouppgsql-hackers @
categoriespostgresql
postedAug 22, '13 at 7:53p
activeAug 27, '13 at 9:04p
posts11
users8
websitepostgresql.org...
irc#postgresql

People

Translate

site design / logo © 2021 Grokbase