database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-29 10:41:53 +03:00
Code Activity

Install recycled WAL segments with current timeline ID during recovery.

Browse Source 
This is a follow-up to the earlier fix, which changed the recycling logic
to recycle WAL segments under the current recovery target timeline. That
turns out to be a bad idea, because installing a recycled segment with
a TLI higher than what we're recovering at the moment means that the recovery
logic will find the recycled WAL segment and try to replay it. It will fail,
but but the mere presence of such a WAL segment will mask any other, real,
file with the same log/seg, but smaller TLI.

Per report from Mitsumasa Kondo. Apply to 9.1 and 9.2, like the previous
fix. Master was already doing this differently; this patch makes 9.1 and
9.2 to do the same thing as master.
This commit is contained in:
Heikki Linnakangas
2013-04-30 16:31:21 +03:00
parent 841c9b6ba1
commit 4aed94f166
1 changed files with 11 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
src/backend/access/transam/xlog.c
View File

@ -8566,10 +8566,18 @@ CreateRestartPoint(int flags)
PrevLogSeg(_logId, _logSeg);
/*
* Update ThisTimeLineID to the recovery target timeline, so that
* we install any recycled segments on the correct timeline.
* Update ThisTimeLineID to the timeline we're currently replaying,
* so that we install any recycled segments on that timeline.
*
* There is no guarantee that the WAL segments will be useful on the
* current timeline; if recovery proceeds to a new timeline right
* after this, the pre-allocated WAL segments on this timeline will
* not be used, and will go wasted until recycled on the next
* restartpoint. We'll live with that.
*/
ThisTimeLineID = GetRecoveryTargetTLI();
SpinLockAcquire(&xlogctl->info_lck);
ThisTimeLineID = XLogCtl->lastCheckPoint.ThisTimeLineID;
SpinLockRelease(&xlogctl->info_lck);
RemoveOldXlogFiles(_logId, _logSeg, endptr);