Re: Is Recovery actually paused?
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: nagata@sraoss.co.jp
Cc: dilipbalaut@gmail.com, bharath.rupireddyforpostgres@gmail.com,
sawada.mshk@gmail.com, pgsql-hackers@lists.postgresql.org,
robertmhaas@gmail.com, simon@2ndquadrant.com
Date: 2021-02-08T08:32:46Z
Lists: pgsql-hackers
At Mon, 8 Feb 2021 14:12:35 +0900, Yugo NAGATA <nagata@sraoss.co.jp> wrote in > > > > I think the right fix should be that the state should never go from > > > > ‘paused’ to ‘pause requested’ so I think pg_wal_replay_pause should take > > > > care of that. > > > > > > It makes sense to take care of this in pg_wal_replay_pause, but I wonder > > > it can not handle the case that a user resume and pause again while a sleep. > > > > Right, we will have to check and set in the loop. But we should not > > allow the state to go from paused to pause requested irrespective of > > this. > > I agree with you. Is there any actual harm if PAUSED returns to REQUESETED, assuming we immediately change the state to PAUSE always we see REQUESTED in the waiting loop, despite that we allow change the state from PAUSE to REQUESTED via NOT_PAUSED between two successive loop condition checks? regards. -- Kyotaro Horiguchi NTT Open Source Software Center
Commits
-
Be clear about whether a recovery pause has taken effect.
- 32fd2b57d7f6 14.0 landed
-
Pause recovery for insufficient parameter settings
- 15251c0a60be 14.0 cited
-
Remove most volatile qualifiers from xlog.c
- 6ba4ecbf477e 9.5.0 cited