From: | Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> |
---|---|
To: | Michael Sawyers <msawyers(at)iii(dot)com> |
Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Massive table bloat |
Date: | 2012-12-11 21:12:01 |
Message-ID: | CAL_0b1t39J6=PNR5Ff4sEFS7C1mNyLKSRe7mR+Ze5p0JtU3R1w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Tue, Dec 11, 2012 at 1:09 PM, Sergey Konoplev <gray(dot)ru(at)gmail(dot)com> wrote:
> On Tue, Dec 11, 2012 at 8:11 AM, Michael Sawyers <msawyers(at)iii(dot)com> wrote:
>> We have a table currently using 33gb worth of space for only 152mb worth of
>> data because of bad processes or autovacuum not being aggressive enough. I
>> was able to confirm the size difference by doing a create table as select
>> along with a second test of restoring the table from the dump file to a dev
>> machine.
>
> You can use pgcompactor (http://code.google.com/p/pgtoolkit/) to
> gently reduce bloat. It does not use heavy locks, processes both
> tables and indexes, determines if one is bloated and tested on 8.4.
Sorry, forget to mention. It does not need an extra space and does not
required a service window.
--
Sergey Konoplev
Database and Software Architect
http://www.linkedin.com/in/grayhemp
Phones:
USA +1 415 867 9984
Russia, Moscow +7 901 903 0499
Russia, Krasnodar +7 988 888 1979
Skype: gray-hemp
Jabber: gray(dot)ru(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Sawyers | 2012-12-11 21:14:47 | Re: Massive table bloat |
Previous Message | Sergey Konoplev | 2012-12-11 21:09:43 | Re: Massive table bloat |