From: Alvaro Herrera <alvherre@commandprompt.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org, Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings
Date: Wed, 13 Aug 2008 21:28:34 -0400
Message-ID: <20080814012834.GG4672@alvh.no-ip.org> (raw)
In-Reply-To: <18539.1218675190@sss.pgh.pa.us>
References: <20080813212838.GA4683@alvh.no-ip.org>
<18539.1218675190@sss.pgh.pa.us>
Tom Lane wrote:
> 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.
Yeah, Magnus was suggesting this syntax:
ALTER TABLE foo SET toast_autovacuum_enable = false;
and the like.
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: alvherre@commandprompt.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings
In-Reply-To: <20080814012834.GG4672@alvh.no-ip.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox