Re: FSM and VM file
От
akp geek
Тема
Re: FSM and VM file
Дата
Msg-id
2024a9fb1003021347n102d0498yec38504b06ba9fab@mail.gmail.com
Ответ на
Re: FSM and VM file (Scott Mead)
Список
Дерево обсуждения
FSM and VM file akp geek <akpgeek@gmail.com>
Re: FSM and VM file Scott Mead <scott.lists@enterprisedb.com>
Re: FSM and VM file akp geek <akpgeek@gmail.com>
Re: FSM and VM file Richard Huxton <dev@archonet.com>
Re: FSM and VM file akp geek <akpgeek@gmail.com>
Re: FSM and VM file Devrim GÜNDÜZ <devrim@gunduz.org>
Re: FSM and VM file akp geek <akpgeek@gmail.com>
Re: FSM and VM file akp geek <akpgeek@gmail.com>
Re: FSM and VM file Richard Huxton <dev@archonet.com>
Re: FSM and VM file Richard Huxton <dev@archonet.com>
Re: FSM and VM file Thomas Kellerer <spam_eater@gmx.net>
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.lists@enterprisedb.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: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
В списке pgsql-general по дате отправления
