From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jonah H. Harris <jonah.harris@gmail.com>
Cc: Campbell, Lance <lance@uiuc.edu>
Cc: posgres support <pgsql-admin@postgresql.org>
Subject: Re: Enhancement request
Date: Fri, 30 Nov 2007 16:48:24 -0500
Message-ID: <7341.1196459304@sss.pgh.pa.us> (raw)
In-Reply-To: <36e682920711301332q1cce5db9qe44fb068fcd5608d@mail.gmail.com>
References: <B10E6810AC2A2F4EA7550D072CDE8760197E2C@SAB-FENWICK.sab.uiuc.edu>
<36e682920711301218m703b3c67s6f547fd7b9b60e7c@mail.gmail.com>
<7099.1196458205@sss.pgh.pa.us>
<36e682920711301332q1cce5db9qe44fb068fcd5608d@mail.gmail.com>
"Jonah H. Harris" <jonah.harris@gmail.com> writes:
> On Nov 30, 2007 4:30 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> AFAICS we are moving as fast as we can in the direction of auto vacuum
>> and analyze. Adding more frammishes to the manual commands seems like
>> gilding the buggy whip.
> Autovacuum will never be the be all end all.
No doubt, which is why no one has proposed removing the manual commands.
(Yet, anyway.) But adding complication to them is not going to be an
easy sale. We have limited manpower for development and we cannot
afford to get bogged down maintaining a codebase with enormous bloat
from useless legacy "features".
So: show me a use case for this that will still make sense in a
mostly-autovacuum world. I can see a need for manual vacuuming of
individual special-case tables, but I don't see why schema-wide
vacuuming is so useful as to justify diverting development effort to it.
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, jonah.harris@gmail.com, lance@uiuc.edu
Subject: Re: Enhancement request
In-Reply-To: <7341.1196459304@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