From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Jim C(dot) Nasby" <decibel(at)decibel(dot)org> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Zeugswetter Andreas ADI SD <ZeugswetterA(at)spardat(dot)at>, Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TOAST usage setting |
Date: | 2007-06-05 01:28:22 |
Message-ID: | 2544.1181006902@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Jim C. Nasby" <decibel(at)decibel(dot)org> writes:
> On Fri, Jun 01, 2007 at 01:50:12PM -0400, Bruce Momjian wrote:
>> The big question is do we want to drop the target tuple size down to
>> 512, and increase the chunk size to 8k for 8.3?
> If we do that people could see their disk space usage increase by up to
> 16x: currently 513 bytes fits in heap and takes (roughly) 513 bytes; if
> we make that change it would then get toasted and take 8K.
That argument is completely bogus --- having a toast chunk size of 8K
does not mean that smaller rows occupy 8K.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-06-05 03:46:08 | Re: pgsql: Create a GUC parameter temp_tablespacesthat allows selection of |
Previous Message | Tom Lane | 2007-06-05 01:25:41 | Re: Implicit casts with generic arrays |