From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Matthew T. O'Connor <matthew@zeut.net>
Cc: Otto Blomqvist <o.blomqvist@secomintl.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: pg_autovacuum not having enough suction ?
Date: Fri, 25 Mar 2005 18:18:13 -0500
Message-ID: <16180.1111792693@sss.pgh.pa.us> (raw)
In-Reply-To: <200503252313.j2PNDFA24795@candle.pha.pa.us>
References: <200503252313.j2PNDFA24795@candle.pha.pa.us>
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Tom Lane wrote:
>> I'm not sure if autovacuum could be taught to do that --- it could
>> perhaps launch a vacuum as soon as it notices a large fraction of the
>> table got deleted, but do we really want to authorize it to launch
>> VACUUM FULL?
> One problem with VACUUM FULL would be autovacuum waiting for an
> exclusive lock on the table. Anyway, it is documented now as a possible
> issue.
I don't care too much about autovacuum waiting awhile to get a lock.
I do care about other processes getting queued up behind it, though.
Perhaps it would be possible to alter the normal lock queuing semantics
for this case, so that autovacuum's request doesn't block later
arrivals, and it can only get the lock when no one is interested in the
table. Of course, that might never happen, or by the time it does
there's no point in VACUUM FULL anymore :-(
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, pgman@candle.pha.pa.us, matthew@zeut.net, o.blomqvist@secomintl.com
Subject: Re: pg_autovacuum not having enough suction ?
In-Reply-To: <16180.1111792693@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