From: Michael Sawyers <msawyers@iii.com>
To: pgsql-admin@postgresql.org
Subject: Re: Massive table bloat
Date: Tue, 11 Dec 2012 11:50:08 -0800 (PST)
Message-ID: <1355255408530-5736151.post@n5.nabble.com> (raw)
In-Reply-To: <50C78B06.9000606@pinpointresearch.com>
References: <1355242268184-5736111.post@n5.nabble.com>
<50C78B06.9000606@pinpointresearch.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
The dump takes about 30 minutes and restore on an older dev machine took
several hours to complete.
I did create a cluster on the restored (un-bloated) table and it finished in
~10 minutes and I should have space for the extra copies since the actual
data is very small.
I had looked at pg_reorg, but the bosses don't want me using something that
hasn't been cleared, otherwise it looks pretty handy to have.
Thanks for the point about cluster being the current vacuum full, and for
the opinion in general. Someday I hope all our customer can use a more up
to date version and I'll be making it more a point if I end up filling some
DBA role here officially.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Massive-table-bloat-tp5736111p5736151.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: msawyers@iii.com
Subject: Re: Massive table bloat
In-Reply-To: <1355255408530-5736151.post@n5.nabble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox