| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | "Hardwick, Joe" <Joe(dot)Hardwick(at)fnis(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Crash after VACUUM FULL cancel |
| Date: | 2008-04-09 14:59:17 |
| Message-ID: | 20080409145917.GC5233@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hardwick, Joe wrote:
> We have a cronjob that runs nightly to do the VACUUM FULL ANALYZE on a
> few tables in each schema and occasionally we'll cancel one if they take
> longer than usual to run and block our morning loads.. This is the first
> time Postgres has had any trouble with it. Is cancelling a full vacuum
> a bad idea?
Yes -- this is a known problem but since VACUUM FULL is deprecated, the
most likely outcome is that it won't get fixed. Just don't cancel it.
You don't need VACUUM FULL anyway in most cases -- plain VACUUM ANALYZE
should be more than enough. For the rare cases that it's not, you can
use CLUSTER to compress the dead space.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2008-04-09 15:00:00 | Re: Disable Triggers |
| Previous Message | Syra.Didelez | 2008-04-09 14:55:42 | Re: Problem with windows Postgres 8.3.1 MSI binary distribution |