Horton

Re: autovacuum not prioritising for-wraparound tables

Robert Haas <robertmhaas@gmail.com>

View thread View on postgr.es
From: Robert Haas <robertmhaas@gmail.com>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Andres Freund <andres@2ndquadrant.com>, Kevin Grittner <kgrittn@ymail.com>, Josh Berkus <josh@agliodbs.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2013-02-02T15:43:43Z
Lists: pgsql-hackers 
On Fri, Feb 1, 2013 at 6:09 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> As an aside, it does seem like log_autovacuum_min_duration=0 should
> log whether a scan_all was done, and if so what relfrozenxid got set
> to.

That would be nifty.

> [1] I don't know why it is that a scan_all vacuum with a
> freeze_min_age of 50m (or a freezeLimit of 50 million ago) will not
> set relfrozenxid to a higher value than that if it discovers that it
> can, but it doesn't seem to.

That also seems very much worth fixing.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

  1. COPY FREEZE and mark committed on fresh tables.

  2. Add vacuum_freeze_table_age GUC option, to control when VACUUM should