From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: pgsql-performance@postgresql.org, Pg Hackers <pgsql-hackers@postgresql.org>
Subject: Re: autovacuum: use case for indenpedent TOAST table autovac settings
Date: Wed, 13 Aug 2008 20:53:10 -0400
Message-ID: <18539.1218675190@sss.pgh.pa.us> (raw)
In-Reply-To: <20080813212838.GA4683@alvh.no-ip.org>
References: <20080813212838.GA4683@alvh.no-ip.org>
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
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: tgl@sss.pgh.pa.us, alvherre@commandprompt.com, pgsql-hackers@postgresql.org
Subject: Re: autovacuum: use case for indenpedent TOAST table autovac settings
In-Reply-To: <18539.1218675190@sss.pgh.pa.us>
* 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