aboutsummaryrefslogtreecommitdiff
path: root/src/backend/postmaster/checkpointer.c
diff options
context:
space:
mode:
authorHeikki Linnakangas <heikki.linnakangas@iki.fi>2012-12-20 14:01:50 +0200
committerHeikki Linnakangas <heikki.linnakangas@iki.fi>2012-12-20 14:39:04 +0200
commit1a11d4609efaae39d9b7472fb965bca1c0aeda01 (patch)
tree718587c38569a268f5fe0fbbb51e201e9fcee3d9 /src/backend/postmaster/checkpointer.c
parent345fb82f1616b4d44d8a67a6c10e964400d29c09 (diff)
downloadpostgresql-1a11d4609efaae39d9b7472fb965bca1c0aeda01.tar.gz
postgresql-1a11d4609efaae39d9b7472fb965bca1c0aeda01.zip
Don't set ThisTimeLineID in checkpointer & bgwriter during recovery.
We used to set it to the current recovery target timeline, but the recovery target timeline can change during recovery, leaving ThisTimeLineID at an old value. That seems worse than always leaving it at zero to begin with. AFAICS there was no good reason to set it in the first place. ThisTimeLineID is not needed in checkpointer or bgwriter process, until it's time to write the end-of-recovery checkpoint, and at that point ThisTimeLineID is updated anyway.
Diffstat (limited to 'src/backend/postmaster/checkpointer.c')
-rw-r--r--src/backend/postmaster/checkpointer.c6
1 files changed, 0 insertions, 6 deletions
diff --git a/src/backend/postmaster/checkpointer.c b/src/backend/postmaster/checkpointer.c
index c8a68a1b227..0f05c7ee58c 100644
--- a/src/backend/postmaster/checkpointer.c
+++ b/src/backend/postmaster/checkpointer.c
@@ -347,12 +347,6 @@ CheckpointerMain(void)
PG_SETMASK(&UnBlockSig);
/*
- * Use the recovery target timeline ID during recovery
- */
- if (RecoveryInProgress())
- ThisTimeLineID = GetRecoveryTargetTLI();
-
- /*
* Ensure all shared memory values are set correctly for the config. Doing
* this here ensures no race conditions from other concurrent updaters.
*/