Re: FSM and VM file
| От | akp geek |
|---|---|
| Тема | Re: FSM and VM file |
| Дата | |
| Msg-id | 2024a9fb1003030532n90b6b6ta87bbdc49a9676df@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: FSM and VM file (Richard Huxton <dev@archonet.com>) |
| Ответы |
Re: FSM and VM file
Re: FSM and VM file |
| Список | pgsql-general |
Thank you all for the suggestions. I did a vacuum and the size has gone down drastically. But still it is not the same size as my master. I am looking into it
Appreicate your help
On Wed, Mar 3, 2010 at 4:41 AM, Richard Huxton <dev@archonet.com> wrote:
On 02/03/10 21:47, akp geek wrote: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.I'm guessing your slave isn't being vacuumed. Or, perhaps you have a long-running transaction on the slave that is preventing dead rows from being cleaned up.my master is 8.3 and slave is 8.4
Two useful commands:
vacuum verbose mytable;
This will show you how many rows/pages can/should be cleaned up.
SELECT pg_size_pretty( pg_total_relation_size('mytable') );
This will show you the size of "mytable" (formatted nicely).
--
Richard Huxton
Archonet Ltd
В списке pgsql-general по дате отправления: