| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | akp geek <akpgeek(at)gmail(dot)com> |
| Cc: | Scott Mead <scott(dot)lists(at)enterprisedb(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: FSM and VM file |
| Date: | 2010-03-03 09:41:18 |
| Message-ID: | 4B8E2EBE.7040903@archonet.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
> my master is 8.3 and slave is 8.4
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.
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben Eliott | 2010-03-03 09:57:37 | Re: createdb but revoke dropdb |
| Previous Message | Richard Huxton | 2010-03-03 09:17:11 | Re: createdb but revoke dropdb |