From: Chris Browne <cbbrowne@acm.org>
To: pgsql-performance@postgresql.org
Subject: Re: Autovacuum / full vacuum
Date: Wed, 18 Jan 2006 11:54:21 -0500
Message-ID: <60d5ipcw8y.fsf@dba2.int.libertyrms.com> (raw)
References: <dqigaf$1b98$1@news.hub.org>
<20060117145649.GE21092@phlogiston.dyndns.org>
<608xteerfh.fsf@dba2.int.libertyrms.com>
<20060117173046.GA4296@surnet.cl>
<604q42elzl.fsf@dba2.int.libertyrms.com>
<20592.1137526372@sss.pgh.pa.us>
<034701c61c46$f427df20$f20214ac@bite.lt>
mind@bi.lt ("Mindaugas") writes:
>> >> Even a database-wide vacuum does not take locks on more than one
>> >> table. The table locks are acquired and released one by one, as
>> >> the operation proceeds.
>>
>> > Has that changed recently? I have always seen "vacuumdb" or SQL
>> > "VACUUM" (without table specifications) running as one long
>> > transaction which doesn't release the locks that it is granted
>> > until the end of the transaction.
>>
>> You sure? It's not supposed to, and watching a database-wide
>> vacuum with "select * from pg_locks" doesn't look to me like it
>> ever has locks on more than one table (plus the table's indexes and
>> toast table).
>
> Are there some plans to remove vacuum altogether?
I don't see that on the TODO list...
http://www.postgresql.org/docs/faqs.TODO.html
To the contrary, there is a whole section on what functionality to
*ADD* to VACUUM.
--
let name="cbbrowne" and tld="acm.org" in String.concat "@" [name;tld];;
http://www.ntlug.org/~cbbrowne/finances.html
"There are two types of hackers working on Linux: those who can spell,
and those who can't. There is a constant, pitched battle between the
two camps."
--Russ Nelson (Linux Kernel Summary, Ver. 1.1.75 -> 1.1.76)
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: cbbrowne@acm.org
Subject: Re: Autovacuum / full vacuum
In-Reply-To: <60d5ipcw8y.fsf@dba2.int.libertyrms.com>
* 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