]> granicus.if.org Git - postgresql/commit
Don't try to truncate multixact SLRU files in checkpoints done during xlog
authorTom Lane <tgl@sss.pgh.pa.us>
Thu, 20 Jul 2006 00:46:42 +0000 (00:46 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Thu, 20 Jul 2006 00:46:42 +0000 (00:46 +0000)
commit9dc842f0832fd71eda826349a0c17ecf8ae93b84
tree6a837db443f3c8be9048cf3769ccb0cffa057714
parenta8e44f0b1bb02aac86a654bbb7474b1569769758
Don't try to truncate multixact SLRU files in checkpoints done during xlog
recovery.  In the first place, it doesn't work because slru's
latest_page_number isn't set up yet (this is why we've been hearing reports
of strange "apparent wraparound" log messages during crash recovery, but
only from people who'd managed to advance their next-mxact counters some
considerable distance from 0).  In the second place, it seems a bit unwise
to be throwing away data during crash recovery anwyway.  This latter
consideration convinces me to just disable truncation during recovery,
rather than computing latest_page_number and pushing ahead.
src/backend/access/transam/multixact.c