"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> Well it certainly seems worth separating them. It does seem possible
> that recursive toasting effected some of the earlier results we looked
> Would you like me to do this, or will you?
I'm willing to do the code changes to separate TOAST_THRESHOLD from
the toast chunk size, but I do not have the time or facilities to do
any performance testing for different parameter choices. Anyone want
to work on that?
> I'd like to get some mechanism for reducing WAL volume into 8.3, whether
> its configurable toast or WAL reduction for UPDATEs. If for no other
> reason than making backup and availability solutions more manageable.
I think the WAL-reduction proposal needs more time and thought than is
feasible before 8.3. OTOH, tuning the TOAST parameters seems like
something we understand well enough already, we just need to put some
cycles into testing different alternatives. I would have no objection
to someone working on that during April and delivering a final patch
sometime before beta.
regards, tom lane
In response to
pgsql-hackers by date
|Next:||From: Teodor Sigaev||Date: 2007-03-29 16:11:50|
|Subject: Re: Warning on contrib/tsearch2|
|Previous:||From: Tom Lane||Date: 2007-03-29 15:45:05|
|Subject: Re: CREATE INDEX and HOT - revised design |