|From:||Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>|
|To:||"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>|
|Cc:||"Greg Stark" <stark(at)enterprisedb(dot)com>, "Shadar" <shauldar(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)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.
>> 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
regards, tom lane
|Next Message||Bruce Momjian||2009-06-11 22:21:44||pgsql: Document struct/union problem with pgindent.|
|Previous Message||Kevin Grittner||2009-06-11 22:03:24||Re: Modifying TOAST_TUPLE_THRESHOLD and TOAST_TUPLE_TARGET?|