pgsql: Force VACUUM to recalculate oldestXmin even when we haven't

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Force VACUUM to recalculate oldestXmin even when we haven't
Date: 2009-09-01 04:46:49
Message-ID: 20090901044649.B50B975331E@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Force VACUUM to recalculate oldestXmin even when we haven't changed our
own database's datfrozenxid, if the current value is old enough to be
forcing autovacuums or warning messages. This ensures that a bogus
value is replaced as soon as possible. Per a comment from Heikki.

Modified Files:
--------------
pgsql/src/backend/access/transam:
varsup.c (r1.85 -> r1.86)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/varsup.c?r1=1.85&r2=1.86)
pgsql/src/backend/commands:
vacuum.c (r1.392 -> r1.393)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/commands/vacuum.c?r1=1.392&r2=1.393)
pgsql/src/include/access:
transam.h (r1.69 -> r1.70)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/include/access/transam.h?r1=1.69&r2=1.70)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2009-09-01 13:49:04 Re: [COMMITTERS] pgsql: Move processing of startup-packet switches and GUC settings into
Previous Message Tom Lane 2009-09-01 04:15:45 pgsql: Actually, we need to bump the format identifier on twophase files