| From: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
|---|---|
| To: | Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: vacuum - reclaiming disk space. |
| Date: | 2016-03-17 17:01:57 |
| Message-ID: | CAKt_ZfvkmK_cuU-oKMY7Q5FgHP5wA_LAMB7_Q+-pbvmj7yLCKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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, 2016 at 7:27 AM, Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com>
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 within the scheduled downtime.
>
> Any suggestions for reclaiming the space without excessive downtime?
>
>
> * <Mike(dot)Blackwell(at)rrd(dot)com>*
>
--
Best Wishes,
Chris Travers
Efficito: Hosted Accounting and ERP. Robust and Flexible. No vendor
lock-in.
http://www.efficito.com/learn_more
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Kehlet | 2016-03-17 18:47:40 | which db caused postgres to stop serving due to wraparound prevention? |
| Previous Message | Robert McAlpine | 2016-03-17 16:57:23 | Re: vacuum - reclaiming disk space. |