On Feb 5, 2007, at 10:45 AM, Simon Riggs wrote:
Jan suggested to me a while back that having a configurable toast
threshold would be a useful thing, when that table is also updated
reasonably frequently.
While we're in there it probably makes sense to allow a configurable
value for when to co
On 2/5/2007 11:52 AM, Tom Lane wrote:
"Simon Riggs" <[EMAIL PROTECTED]> writes:
Sounds like a good time to suggest making these values configurable,
within certain reasonable bounds to avoid bad behaviour.
Actually, given what we've just learned --- namely that choosing these
values at random
"Simon Riggs" <[EMAIL PROTECTED]> writes:
> Sounds like a good time to suggest making these values configurable,
> within certain reasonable bounds to avoid bad behaviour.
Actually, given what we've just learned --- namely that choosing these
values at random is a bad idea --- I'd want to see a wh
On Fri, 2007-02-02 at 15:11 -0500, Tom Lane wrote:
> 2. Fix TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET to be correctly
> calculated (properly allowing for line pointers) and to be MAXALIGN
> multiples. The threshold value should be exactly the size of the
> largest tuple that you can put four of
