From: | Lewis Kapell <lkapell(at)setonhome(dot)org> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: TOAST behavior in 8.3 and 8.4 |
Date: | 2010-04-13 19:27:14 |
Message-ID: | 4BC4C592.7020400@setonhome.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks for the clarification.
In tuptoaster.h, just above the declaration of TOAST_TUPLES_PER_PAGE,
there is a comment which begins: "while these can be modified without
initdb..."
Does this mean that if I reduce the value of TOAST_TUPLE_THRESHOLD and
rebuild, I can use an existing database cluster without having to run
initdb again?
On 4/13/2010 3:02 PM, Kevin Grittner wrote:
> Lewis Kapell<lkapell(at)setonhome(dot)org> wrote:
>
>> I don't understand what that '256 bytes' refers to. That is a far
>> cry from 2kb. I would be grateful if anyone can fill in the
>> evident gap in my knowledge here.
>
> It doesn't try to compress anything unless the tuple (row instance)
> as a whole is above TOAST_TUPLE_THRESHOLD. In trying to reduce the
> tuple size, it won't consider compressing column values below a
> certain size. That is where the 256 versus 32 bytes comes in.
>
> -Kevin
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2010-04-13 19:37:29 | Re: TOAST behavior in 8.3 and 8.4 |
Previous Message | Alvaro Herrera | 2010-04-13 19:22:26 | Re: TOAST behavior in 8.3 and 8.4 |