From: Greg Smith <gsmith@gregsmith.com>
To: Gauri Kanekar <meetgaurikanekar@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Replication Syatem
Date: Tue, 29 Apr 2008 01:08:09 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0804290104570.2503@westnet.com> (raw)
In-Reply-To: <7e4ba9550804282155u655e3ab5o38d2e659b485530d@mail.gmail.com>
References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com>
<60wsmh64f6.fsf@dba2.int.libertyrms.com>
<7e4ba9550804282155u655e3ab5o38d2e659b485530d@mail.gmail.com>
On Tue, 29 Apr 2008, Gauri Kanekar wrote:
> Basically we have some background process which updates "table1" and we
> don't want the application to make any changes to "table1" while vacuum.
> Vacuum requires exclusive lock on "table1" and if any of the background or
> application is ON vacuum don't kick off.
VACUUM FULL needs an exclusive lock, the regular one does not in 8.1.
It's one of the reasons FULL should be avoided. If you do regular VACUUM
frequently enough, you shouldn't ever need to do a FULL one anyway.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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: gsmith@gregsmith.com, meetgaurikanekar@gmail.com
Subject: Re: Replication Syatem
In-Reply-To: <Pine.GSO.4.64.0804290104570.2503@westnet.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