Force VACUUM to recalculate oldestXmin even when we haven't changed our

Tom Lane <tgl@sss.pgh.pa.us>

Commit: 794e3e81a0e8068de2606015352c1254cb071a78
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: 2009-09-01T04:46:49Z
Releases: 9.0.0
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.

Files

PathChange+/−
src/backend/access/transam/varsup.c modified +16 −7
src/backend/commands/vacuum.c modified +4 −3
src/include/access/transam.h modified +2 −2