Re: pgsql: Add a note about another issue that needs to be considered before - Mailing list pgsql-committers

From Gregory Stark
Subject Re: pgsql: Add a note about another issue that needs to be considered before
Date
Msg-id 87myts67ow.fsf@oxford.xeocode.com
Whole thread Raw
In response to pgsql: Add a note about another issue that needs to be considered before  (tgl@postgresql.org (Tom Lane))
Responses Re: pgsql: Add a note about another issue that needs to be considered before
List pgsql-committers
"Tom Lane" <tgl@postgresql.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!

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Document txid functions.
Next
From: mkz@pgfoundry.org (User Mkz)
Date:
Subject: plproxy - plproxy: explicit type casting for result fields