"Tom Lane" <tgl(at)postgresql(dot)org> writes:
> Log Message:
> Add a note about another issue that needs to be considered before
> changing the TOAST size thresholds.
FWIW I found another issue with this variable when I was experimenting with
small block sizes. If you set the target <= the tuple header the toaster
breaks. This is because it's doing unsigned arithmetic (Size is unsigned). I
think the right solution is just to change it to use plain int32 arithmetic
I don't think this affects the default thresholds because even with the
maximum number of columns (1600) the null bitmap can't be as large as 2kB (the
most it can get to is 200 bytes).
Ask me about EnterpriseDB's PostGIS support!
In response to
pgsql-hackers by date
|Next:||From: Gokulakannan Somasundaram||Date: 2007-11-05 15:20:33|
|Subject: Re: Fwd: Clarification about HOT|
|Previous:||From: Magnus Hagander||Date: 2007-11-05 15:17:15|
|Subject: Re: Slow regression tests on windows|
pgsql-committers by date
|Next:||From: User Mkz||Date: 2007-11-05 15:43:42|
|Subject: plproxy - plproxy: explicit type casting for result fields|
|Previous:||From: Bruce Momjian||Date: 2007-11-05 14:51:08|
|Subject: pgsql: Document txid functions.|