I have a problem with promoting from hot-standby that exclusive
checkpointing retards completion of promotion.
This checkpoint is "shutdown checkpoint" as a convention in
realtion to TLI increment according to the comment shown below. I
suppose "shutdown checkpoint" means exclusive checkpoint - in
other words, checkpoint without WAL inserts meanwhile.
> * one. This is not particularly critical, but since we may be
> * assigning a new TLI, using a shutdown checkpoint allows us to have
> * the rule that TLI only changes in shutdown checkpoints, which
> * allows some extra error checking in xlog_redo.
I depend on this and suppose we can omit it if latest checkpoint
has been taken so as to be able to do crash recovery thereafter.
This condition could be secured by my another patch for
checkpoint_segments on standby.
After applying this patch, checkpoint after archive recovery at
near the end of StartupXLOG() will be skiped on the condition
- WAL receiver has been launched so far. (using WalRcvStarted())
- XLogCheckpointNeeded() against replayEndRecPtr says no need of
What do you think about this?
This patch needs WalRcvStarted() introduced by my another patch.
NTT Open Source Software Center
== My e-mail address has been changed since Apr. 1, 2012.
pgsql-hackers by date
|Next:||From: Simon Riggs||Date: 2012-06-08 08:46:37|
|Subject: Re: [v9.3] Extra Daemons (Re: elegant and effective way for
running jobs inside a database)|
|Previous:||From: Kyotaro HORIGUCHI||Date: 2012-06-08 08:14:48|
|Subject: Checkpointer on hot standby runs without looking