Postgres Pro
Downloads
Home   >   mailing lists

Re: pgsql: Track the current XID wrap limit (or more accurately, the oldest - Mailing list pgsql-committers

From Heikki Linnakangas
Subject Re: pgsql: Track the current XID wrap limit (or more accurately, the oldest
Date
Msg-id 4A9B7242.3000903@enterprisedb.com
Whole thread Raw
In response to pgsql: Track the current XID wrap limit (or more accurately, the oldest  (tgl@postgresql.org (Tom Lane))
Responses Re: pgsql: Track the current XID wrap limit (or more accurately, the oldest
List pgsql-committers
Tree view 
Tom Lane wrote:
> Log Message:
> -----------
> Track the current XID wrap limit (or more accurately, the oldest unfrozen
> XID) in checkpoint records.  This eliminates the need to recompute the value
> from scratch during database startup, which is one of the two remaining
> reasons for the flatfile code to exist.

1. Cluster is close to the stop limit.
2. Autovacuum runs, updates pg_database and advances oldestXid. Phew!
3. Crash.

After recovery, oldestXid is reset to the old value, and you start
getting warnings again. However, everything seems fine in pg_database,
all the databases have been recently vacuumed. Does autovacuum ever run
to fix that? ISTM it won't.

--
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Track the current XID wrap limit (or more accurately, the oldest
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Change the autovacuum launcher to read pg_database directly,