From: Tom Lane <tgl@sss.pgh.pa.us>
To: SZUCS Gabor <surrano@mailbox.hu>
Cc: pgsql-sql@postgresql.org
Subject: Re: VACUUM FULL and ALTER TABLE do *nothing* in 7.3.2
Date: Tue, 06 May 2003 10:35:04 -0400
Message-ID: <25098.1052231704@sss.pgh.pa.us> (raw)
In-Reply-To: <008801c313d6$ad89e390$0a03a8c0@fejleszt2>
References: <Pine.LNX.4.44.0305061552020.22644-100000@matrix.gatewaynet.com>
<008801c313d6$ad89e390$0a03a8c0@fejleszt2>
"SZUCS Gabor" <surrano@mailbox.hu> writes:
> Do you have any idea about an explanation? Does vacuum wait for the end of
> each and every transaction?
VACUUM FULL needs an exclusive lock on the target table. So does ALTER
TABLE. So yes, it will wait for any open transaction that has accessed
the table to complete.
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, surrano@mailbox.hu
Subject: Re: VACUUM FULL and ALTER TABLE do *nothing* in 7.3.2
In-Reply-To: <25098.1052231704@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