Thursday, August 14, 2008

Re: [HACKERS] [PERFORM] autovacuum: use case for indenpedent TOAST table autovac settings

On Wed, 2008-08-13 at 21:30 -0400, Tom Lane wrote:
> Alvaro Herrera <alvherre@commandprompt.com> writes:
> > Tom Lane wrote:
> >> It seems like we'll want to do it somehow. Perhaps the cleanest way is
> >> to incorporate toast-table settings in the reloptions of the parent
> >> table. Otherwise dump/reload is gonna be a mess.
>
> > My question is whether there is interest in actually having support for
> > this, or should we just inherit the settings from the main table. My
> > gut feeling is that this may be needed in some cases, but perhaps I'm
> > overengineering the thing.
>
> It seems reasonable to inherit the parent's settings by default, in any
> case. So you could do that now and then extend the feature later if
> there's real demand.

Yeh, I can't really see a reason why you'd want to treat toast tables
differently with regard to autovacuuming. It's one more setting to get
wrong, so no thanks.

--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support


--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

No comments: