From: Michael Sawyers <msawyers@iii.com>
To: pgsql-admin@postgresql.org
Subject: Re: Massive table bloat
Date: Tue, 11 Dec 2012 11:41:30 -0800 (PST)
Message-ID: <1355254890292-5736150.post@n5.nabble.com> (raw)
In-Reply-To: <CAFwQ8rckXcujW2PqG1raNBExea83PUoTr=SXRARUYYrxRZT7mQ@mail.gmail.com>
References: <1355242268184-5736111.post@n5.nabble.com>
<CAFwQ8rckXcujW2PqG1raNBExea83PUoTr=SXRARUYYrxRZT7mQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Political reasons have ruled out the dump and reload options, but restoring
the entire database took several hours. I'm also restricted on version
because newer versions of postgres are not supported with that specific
product, including maintenance updates.
So I'm trying to fix things in place which is where some of the difficulty
is coming in. I did test the the restored database on a dev machine, with
vacuum full, alter table, and cluster table all taking a relatively short
window of time.
I'm just trying to get the best method based on the limitations I have been
handed. Right now it seems like clustering the table on an index, then
dropping that cluster flag might be the cleanest way, but I'm just not 100%
sure.
--
View this message in context: http://postgresql.1045698.n5.nabble.com/Massive-table-bloat-tp5736111p5736150.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: <1355254890292-5736150.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