From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Mindaugas <mind@bi.lt>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Autovacuum / full vacuum
Date: Wed, 18 Jan 2006 13:55:21 -0300
Message-ID: <20060118165521.GC19933@surnet.cl> (raw)
In-Reply-To: <034701c61c46$f427df20$f20214ac@bite.lt>
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>
Mindaugas wrote:
> > >> 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?
No, but there are plans to make it as automatic and unintrusive as
possible. (User configuration will probably always be needed.)
--
Alvaro Herrera Developer, http://www.PostgreSQL.org
FOO MANE PADME HUM
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@alvh.no-ip.org, mind@bi.lt, tgl@sss.pgh.pa.us
Subject: Re: Autovacuum / full vacuum
In-Reply-To: <20060118165521.GC19933@surnet.cl>
* 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