Re: [PERFORM] autovacuum: use case for indenpedent TOAST table autovac settings - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [PERFORM] autovacuum: use case for indenpedent TOAST table autovac settings
Date
Msg-id 1218707461.5343.435.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: [PERFORM] autovacuum: use case for indenpedent TOAST table autovac settings  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Re: gsoc, oprrest function for text search take 2
Next
From: Jan Urbański
Date:
Subject: Re: gsoc, oprrest function for text search take 2