From: | Andrew Hannon <ahannon(at)fiksu(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Repercussions of Cancelled Autovacuum |
Date: | 2012-01-16 01:24:36 |
Message-ID: | DA0EE1E3-8327-44CE-BC60-F674B62A3BFF@fiksu.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello,
We have a large(ish) table that had a series of delete statements executed against it (culling most of the rows in the table). This triggered a time consuming autovacuum, which we allowed to run for 2+ days (and were planning to allow to run to completion). However, it ended up getting cancelled unexpectedly, and is now running once again. I have some questions:
1. My understanding is the autovacuum will block most (all?) DDL statements executed on it, and pg will cancel it if a user requests a conflicting lock. I don't believe either of these things occurred. Are there any other circumstances that will cancel an autovacuum?
2. Is autovacuum incremental? Or, does it effectively roll back and start fresh, having to redo all of the work of the last couple of days?
Thank you!
Andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Cefull Lo | 2012-01-16 13:50:42 | Re: time zone problem |
Previous Message | David Waddy | 2012-01-15 21:20:08 | Re: How to return latest results without a polygon intersect? |