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

From Tom Lane
Subject Re: [PERFORM] autovacuum: use case for indenpedent TOAST table autovac settings
Date
Msg-id 21063.1218677426@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PERFORM] autovacuum: use case for indenpedent TOAST table autovac settings  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: [PERFORM] autovacuum: use case for indenpedent TOAST table autovac settings  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
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.

            regards, tom lane

pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [PERFORM] autovacuum: use case for indenpedent TOAST table autovac settings
Next
From: Decibel!
Date:
Subject: Re: SeqScan costs