Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?
Date
Msg-id 21364.1244758432@sss.pgh.pa.us
Whole thread Raw
In response to Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Responses Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?
List pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes:
>>> It seems to me that MAIN might be a more useful option if it was
>>> more aggressive about avoiding out-of-line storage; perhaps only if
>>> the row doesn't fit by itself on a single page?
>> 
>> Yeah I think we're on the same page there.
> Cool.
>> We've been talking about a number of ideas for making toast more
>> flexible but there are clearly an infinite number of permutations
>> and the trick will be figuring out how to present the useful ones
>> without making things too complicated for the user to control.
> So it would be premature to submit a patch for changing this behavior?

No, I don't think so, since there's no apparent need for a control knob.
You just change the limit that's applied during the last phase of
toast_insert_or_update.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?
Next
From: Bruce Momjian
Date:
Subject: Re: AlterTableCreateToastTable API still not right for pg_migrator