Re: Possible corruption by CreateRestartPoint at promotion
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: michael@paquier.xyz
Cc: nathandbossart@gmail.com, pgsql-hackers@lists.postgresql.org,
masao.fujii@oss.nttdata.com
Date: 2022-04-28T02:43:57Z
Lists: pgsql-hackers
At Thu, 28 Apr 2022 09:12:13 +0900, Michael Paquier <michael@paquier.xyz> wrote in
> On Wed, Apr 27, 2022 at 11:09:45AM -0700, Nathan Bossart wrote:
> > On Wed, Apr 27, 2022 at 02:16:01PM +0900, Michael Paquier wrote:
> >> - if (ControlFile->state == DB_IN_ARCHIVE_RECOVERY &&
> >> - ControlFile->checkPointCopy.redo < lastCheckPoint.redo)
> >> - {
> >> 7ff23c6 has removed the last call to CreateCheckpoint() outside the
> >> checkpointer, meaning that there is one less concurrent race to worry
> >> about, but I have to admit that this change, to update the control
> >> file's checkPoint and checkPointCopy even if we don't check after
> >> ControlFile->checkPointCopy.redo < lastCheckPoint.redo would make the
> >> code less robust in ~14. So I am questioning whether a backpatch
> >> is actually worth the risk here.
> >
> > IMO we should still check this before updating ControlFile to be safe.
>
> Sure. Fine by me to play it safe.
Why do we consider concurrent check/restart points here while we don't
consider the same for ControlFile->checkPointCopy?
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
Commits
-
Fix control file update done in restartpoints still running after promotion
- 60e956eb825c 10.22 landed
- 4525151d4c2f 11.17 landed
- 7e59b1219109 12.12 landed
- 2e9559b30239 13.8 landed
- 6dced63b411b 14.4 landed
- 7863ee4def65 15.0 landed