From: | akp geek <akpgeek(at)gmail(dot)com> |
---|---|
To: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: FSM and VM file |
Date: | 2010-03-02 21:47:46 |
Message-ID: | 2024a9fb1003021347n102d0498yec38504b06ba9fab@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I am doing a replication of one of the database and the size of the slave
database is growing exponentially . Right now the size of master db is 849M
and the slave is 7GB.
When I noticed the base directory on the slave , that's when I noticed the
fsm and vm files and raised the question.
is there any reason why this happens? or is there way to limit the size of
the file.
my master is 8.3 and slave is 8.4
Appreciate your help
Regards
On Tue, Mar 2, 2010 at 4:29 PM, Scott Mead <scott(dot)lists(at)enterprisedb(dot)com>wrote:
> Those are the free space map / visibility map files. There is going to be
> one of each for every relation.
>
> No worries :-) They are supposed to be there:
>
> http://wiki.postgresql.org/wiki/Segment_Visibility_Map
>
>
> Don't clean them up, doing so could be disastrous. Actually, if I were
> you, I would avoid doing ANY deletes / purges in the data directory.
> Everything in there is maintained by the engine.
>
> --Scott
>
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Kellerer | 2010-03-02 23:22:25 | Not all functions in schema pg_catalog are "visible" |
Previous Message | Scott Mead | 2010-03-02 21:29:47 | Re: FSM and VM file |