aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2016-05-24 15:20:12 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2016-05-24 15:20:12 -0400
commita34c3dd50f661126ac51c794e63f7932fe657542 (patch)
tree8f03169bec40c127b2062e47a16c8e48797aa16d /src/backend/tcop/postgres.c
parente504d915bbf352ecfc4ed335af934e799bf01053 (diff)
downloadpostgresql-a34c3dd50f661126ac51c794e63f7932fe657542.tar.gz
postgresql-a34c3dd50f661126ac51c794e63f7932fe657542.zip
Avoid consuming an XID during vac_truncate_clog().
vac_truncate_clog() uses its own transaction ID as the comparison point in a sanity check that no database's datfrozenxid has already wrapped around "into the future". That was probably fine when written, but in a lazy vacuum we won't have assigned an XID, so calling GetCurrentTransactionId() causes an XID to be assigned when otherwise one would not be. Most of the time that's not a big problem ... but if we are hard up against the wraparound limit, consuming XIDs during antiwraparound vacuums is a very bad thing. Instead, use ReadNewTransactionId(), which not only avoids this problem but is in itself a better comparison point to test whether wraparound has already occurred. Report and patch by Alexander Korotkov. Back-patch to all versions. Report: <CAPpHfdspOkmiQsxh-UZw2chM6dRMwXAJGEmmbmqYR=yvM7-s6A@mail.gmail.com>
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions