Re: pgsql: Add a note about another issue that needs to be considered before

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Tom Lane" <tgl(at)postgresql(dot)org>
Cc: <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Add a note about another issue that needs to be considered before
Date: 2007-11-05 15:19:43
Message-ID: 87myts67ow.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers


"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
everywhere.

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).

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's PostGIS support!

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message User Mkz 2007-11-05 15:43:42 plproxy - plproxy: explicit type casting for result fields
Previous Message Bruce Momjian 2007-11-05 14:51:08 pgsql: Document txid functions.

Browse pgsql-hackers by date

  From Date Subject
Next Message Gokulakannan Somasundaram 2007-11-05 15:20:33 Re: Fwd: Clarification about HOT
Previous Message Magnus Hagander 2007-11-05 15:17:15 Re: Slow regression tests on windows