"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
> I also think that we ought to add TOAST_MAX_CHUNK_SIZE to the set of
> compiled-in parameters that are recorded in pg_control and checked for
> compatibility at startup (like BLCKSZ) --- this will prevent anyone from
> shooting themselves in the foot while experimenting.
Is there any reason to experiment with this? I would have thought we would
divorce TOAST_MAX_CHUNK_SIZE from TOAST_THRESHOLD and hard code it as the same
expression that's there now. Ie, the largest size that can fit in a page.
That doesn't mean it shouldn't go in pg_control of course but it would just be
a function of BLCKSIZE and the architecture alignment and not dependent on any
user configurable value.
In response to
pgsql-hackers by date
|Next:||From: Florian G. Pflug||Date: 2007-03-28 17:52:09|
|Subject: Re: CREATE INDEX and HOT - revised design|
|Previous:||From: Tom Lane||Date: 2007-03-28 17:35:54|
|Subject: Re: Arrays of Complex Types |