Re: Is Recovery actually paused?
Kyotaro Horiguchi <horikyota.ntt@gmail.com>
From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
To: dilipbalaut@gmail.com
Cc: nagata@sraoss.co.jp, bharath.rupireddyforpostgres@gmail.com,
sawada.mshk@gmail.com, pgsql-hackers@lists.postgresql.org,
robertmhaas@gmail.com, simon@2ndquadrant.com
Date: 2021-02-09T06:05:43Z
Lists: pgsql-hackers
Sorry, I made a mistake here. At Tue, 09 Feb 2021 14:55:23 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in > At Tue, 9 Feb 2021 09:47:58 +0530, Dilip Kumar <dilipbalaut@gmail.com> wrote in > > APIs the wait logic can be implemented in the application code which > > is actually using these APIs and IMHO that will give better control to > > the users. > > Year, with the PoC pg_wal_replay_pause() can make a short wait as a > side-effect but the tri-state patch also can add a function to wait > for the state suffices. I said that it is surprising that pg_is_wal_replay_paused() waits for the state change. But I didn't say that pg_wal_replay_pause() shouldn't wait for the actual pause. 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