aboutsummaryrefslogtreecommitdiff
path: root/src/tutorial/basics.source
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2013-04-30 16:31:21 +0300
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2013-04-30 17:50:10 +0300
commit424cc31a3785bd01108e6f4b20941c6442d3d2d0 (patch)
tree7702606b4ee5f73f7d5af1eededc508e9c252060 /src/tutorial/basics.source
parent93641341f0993131dfb90aa7ac4add3305d00b9c (diff)
downloadpostgresql-424cc31a3785bd01108e6f4b20941c6442d3d2d0.tar.gz
postgresql-424cc31a3785bd01108e6f4b20941c6442d3d2d0.zip
Install recycled WAL segments with current timeline ID during recovery.
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.
Diffstat (limited to 'src/tutorial/basics.source')
0 files changed, 0 insertions, 0 deletions