From: Gauri Kanekar <meetgaurikanekar@gmail.com>
To: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Replication Syatem
Date: Tue, 29 Apr 2008 10:41:33 +0530
Message-ID: <7e4ba9550804282211s5568dc75l557e057fd1c33c2@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.64.0804290104570.2503@westnet.com>
References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com>
<60wsmh64f6.fsf@dba2.int.libertyrms.com>
<7e4ba9550804282155u655e3ab5o38d2e659b485530d@mail.gmail.com>
<Pine.GSO.4.64.0804290104570.2503@westnet.com>
But unless we do full vacuum the space is not recovered. Thats y we prefer
full vacuum.
~ Gauri
On Tue, Apr 29, 2008 at 10:38 AM, Greg Smith <gsmith@gregsmith.com> wrote:
> 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
>
--
Regards
Gauri
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: meetgaurikanekar@gmail.com, gsmith@gregsmith.com
Subject: Re: Replication Syatem
In-Reply-To: <7e4ba9550804282211s5568dc75l557e057fd1c33c2@mail.gmail.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