The consequenses of interrupted vacuum

From: Bill Moran <wmoran(at)potentialtech(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: The consequenses of interrupted vacuum
Date: 2016-10-27 14:22:43
Message-ID: 20161027102243.452b0bfb944bc77fe7724a83@potentialtech.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Very specific question:
Does interrupting a VACUUM (not FULL) rollback all the work it has done
so far, or is the work done on a page by page basis such that at least
some of the pages in the table have been vacuumed?

I'm asking for cases of large tables where autovacuum frequently gets
interrupted. I'm trying to understand if the partial runs are at least
making _some_ progress so the next vacuum has less to do, or if this is
a serious problem that I need to fiddle with tuning to fix.

--
Bill Moran <wmoran(at)potentialtech(dot)com>

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Scott Mead 2016-10-27 14:27:18 Re: Remove Standby (SLAVE) from Primary (MASTER) - Postgres9.1
Previous Message Joanna Xu 2016-10-27 14:12:30 Re: Remove Standby (SLAVE) from Primary (MASTER) - Postgres9.1