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 18539.1218675190@sss.pgh.pa.us
Whole thread Raw
In response to 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  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Does anyone see a need for having TOAST tables be individually
> configurable for autovacuum?  I've finally come around to looking at
> being able to use ALTER TABLE for autovacuum settings, and I'm wondering
> if we need to support that case.

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.

            regards, tom lane

pgsql-hackers by date:

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