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
