Re: PANIC during crash recovery of a recently promoted standby
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>
Cc: pavan.deolasee@gmail.com, alvherre@2ndquadrant.com, pgsql-hackers@postgresql.org
Date: 2018-07-02T13:41:05Z
Lists: pgsql-hackers
On Mon, Jul 02, 2018 at 04:25:13PM +0900, Kyotaro HORIGUCHI wrote: > When minRecoveryPoint is invalid, there're only two possible > cases. It may be at very beginning of archive reovery or may be > running a crash recovery. In the latter case, we have detected > crash recovery before redo starts. So we can turn off > updateMinRecoveryPoint immediately and no further check is > needed and it is (I think) easier to understand. Er, you are missing the point that updateMinRecoveryPoint is also used by processes, like the checkpointer, other than the startup process, which actually needs to update minRecoveryPoint and rely on the default value of updateMinRecoveryPoint which is true... I am planning to finish wrapping this patch luckily on Wednesday JST time, or in the worst case on Thursday. I got this problem on my mind for a couple of days now and I could not find a case where the approach taken could cause a problem. Opinions are welcome. -- Michael
Commits
-
Prevent references to invalid relation pages after fresh promotion
- 56535dcdc9e2 9.3.24 landed
- f352f43d3f10 9.4.19 landed
- 23eef5cd7ffc 9.5.14 landed
- 8d68ee6f31ca 9.6.10 landed
- 6716f2f96256 10.5 landed
- 9a1bd8271172 11.0 landed
- 3c64dcb1e35d 12.0 landed