From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
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, 6 May 2003 07:32:45 -0700 (PDT)
Message-ID: <20030506073053.G7678-100000@megazone23.bigpanda.com> (raw)
In-Reply-To: <008801c313d6$ad89e390$0a03a8c0@fejleszt2>
On Tue, 6 May 2003, SZUCS Gabor wrote:
> Dear Achilleus,
>
> Dunno, it's a multiuser environment. However, I'll try asking everyone to
> stop working for a minute...
>
> ... oops, I just see that it finished about half an hour before (taking an
> amazing 76 minutes for ALTER TABLE to complete). About that time, I started
> and exited a client. Seems it solved the problem. Now "vacuum full analyze"
> finished in a couple of seconds.
>
> Do you have any idea about an explanation? Does vacuum wait for the end of
> each and every transaction?
Both alter table and vacuum full want to take exclusive locks on the
table IIRC. If say that transaction that was idle had done *anything* on
the table and was sitting open after that, both of those would wait until
the transaction released the lock.
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: sszabo@megazone23.bigpanda.com, surrano@mailbox.hu
Subject: Re: VACUUM FULL and ALTER TABLE do *nothing* in 7.3.2
In-Reply-To: <20030506073053.G7678-100000@megazone23.bigpanda.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