Re: Replication Syatem - Mailing list pgsql-performance

From Pavan Deolasee
Subject Re: Replication Syatem
Date
Msg-id 2e78013d0804282247x35c0b796v80e77206c3b40489@mail.gmail.com
Whole thread Raw
In response to Re: Replication Syatem  ("Gauri Kanekar" <meetgaurikanekar@gmail.com>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: "Gauri Kanekar"
Date:
Subject: Re: Replication Syatem
Next
From: "Pavan Deolasee"
Date:
Subject: Re: Replication Syatem