From: Pavan Deolasee <pavan.deolasee@gmail.com>
To: Gauri Kanekar <meetgaurikanekar@gmail.com>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Replication Syatem
Date: Tue, 29 Apr 2008 11:17:05 +0530
Message-ID: <2e78013d0804282247x35c0b796v80e77206c3b40489@mail.gmail.com> (raw)
In-Reply-To: <7e4ba9550804282211s5568dc75l557e057fd1c33c2@mail.gmail.com>
References: <7e4ba9550804280638ie81dc23w472785c83cd38fcf@mail.gmail.com>
<60wsmh64f6.fsf@dba2.int.libertyrms.com>
<7e4ba9550804282155u655e3ab5o38d2e659b485530d@mail.gmail.com>
<Pine.GSO.4.64.0804290104570.2503@westnet.com>
<7e4ba9550804282211s5568dc75l557e057fd1c33c2@mail.gmail.com>
On Tue, Apr 29, 2008 at 10:41 AM, Gauri Kanekar
<meetgaurikanekar@gmail.com> wrote:
> But unless we do full vacuum the space is not recovered. Thats y we prefer
> full vacuum.
There is no point in recovering the space by moving tuples and
truncating the relation (that's what VACUUM FULL does) because you are
doing frequent updates on the table and that would again extend the
relation. If you run plain VACUUM, that would recover dead space and
update the free space maps. It may not be able to reduce the table
size, but you should not be bothered much about it because the
following updates/inserts will fill in the fragmented free space.
You may want to check your FSM settings as well to make sure that you
are tracking free space properly.
Thanks,
Pavan
--
Pavan Deolasee
EnterpriseDB http://www.enterprisedb.com
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: pavan.deolasee@gmail.com, meetgaurikanekar@gmail.com, gsmith@gregsmith.com
Subject: Re: Replication Syatem
In-Reply-To: <2e78013d0804282247x35c0b796v80e77206c3b40489@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