aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2006-07-20 00:46:56 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2006-07-20 00:46:56 +0000
commitf1418801501f4d1d6394f7bb0fed3de219ab159b (patch)
tree70e934d08214805f802bd4ea52d5e8b4cdf1ade4 /src/backend/tcop/postgres.c
parent74dac69e3c20487b0c2eacee05b4ff8ba12ce640 (diff)
downloadpostgresql-f1418801501f4d1d6394f7bb0fed3de219ab159b.tar.gz
postgresql-f1418801501f4d1d6394f7bb0fed3de219ab159b.zip
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.
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions