Autovacuum will eventually free your extra pages regarding index bloat but
it takes multiple runs.
You could also use reindex instead of vacuum full since you are only
interested in the index.
For the table there may be other options but they depend on your pattern of
writes.
On Thu, Mar 17, 201
On Thu, Mar 17, 2016 at 10:57 AM, bricklen wrote:
> On Thu, Mar 17, 2016 at 7:27 AM, Mike Blackwell
> wrote:
>
>> I have a large table with numerous indexes which has approximately
>> doubled in size after adding a column - every row was rewritten and 50% of
>> the tuples are dead. I'd like to
I have a large table with numerous indexes which has approximately doubled
in size after adding a column - every row was rewritten and 50% of the
tuples are dead. I'd like to reclaim this space, but VACUUM FULL cannot
seem to finish within the scheduled downtime.
Any suggestions for reclaiming th
On Thu, Mar 17, 2016 at 7:27 AM, Mike Blackwell
wrote:
> I have a large table with numerous indexes which has approximately doubled
> in size after adding a column - every row was rewritten and 50% of the
> tuples are dead. I'd like to reclaim this space, but VACUUM FULL cannot
> seem to finish
Just to throw some extreme ideas out there, you could stand up a postgres
on some other server, pg_dump your current database and use that dump to
build up your second postgres. Use that new postgres when your system goes
live again after downtime. Restoring from a dump means your database would
no
