[Bucardo-general] fsm and vm files generated under $PGDATA/base

akp geek akpgeek at gmail.com
Tue Mar 2 21:43:16 UTC 2010

The only reason I got concerned is after I started the replication  process,
the size of my $PGDATA on master is about 849M and on the slave is 7.8G.
It's growing tremondously. I am not able to figure out why.

All I have one master is bucardo and the database that I am trying to
replicate. That's it. any clue why the size of base directory is getting


On Tue, Mar 2, 2010 at 4:18 PM, Rosser Schwarz <rosser.schwarz at gmail.com>wrote:

> On Tue, Mar 2, 2010 at 1:56 PM, akp geek <akpgeek at gmail.com> wrote:
> >              During the replication process , files are getting generated
> in
> > $PGDATA/base directory. Some of the file end up with _fsm and some _vm.
> The *_fsm files are used for a relation's Free Space Map, which tracks
> ... free space in the relation (tuples/pages which are known dead and
> re-usable).  The *_vm files store the Visibility Map, which is a list
> of pages containing only tuples visible to all transactions.  They're
> generated and used by Postgres' autovacuum daemon.  Like the *.1, *.2
> ... *.N files that Postgres creates to partition tables' disk files at
> one gbyte boundaries, you'll want to leave them alone.
> See sections 53.3 and 53.4 of TFM for 8.4 for further details.
> rls
> --
> :wq
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://mail.endcrypt.com/pipermail/bucardo-general/attachments/20100302/4bb68826/attachment-0001.html 

More information about the Bucardo-general mailing list