| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Is Recovery actually paused? |
| Date: | 2020-10-19 14:10:49 |
| Message-ID: | CAFiTN-vcLLWEm8Zr=YK83rgYrT9pbC8VJCfa1kY9vL3AUPfu6g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
We have an interface to pause the WAL replay (pg_wal_replay_pause) and
to know whether the WAL replay pause is requested
(pg_is_wal_replay_paused). But there is no way to know whether the
recovery is actually paused or not. Actually, the recovery process
might process an extra WAL before pausing the recovery. So does it
make sense to provide a new interface to tell whether the recovery is
actually paused or not?
One solution could be that we convert the XLogCtlData->recoveryPause
from bool to tri-state variable (0-> recovery not paused 1-> pause
requested 2-> actually paused).
Any opinion on this?
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2020-10-19 14:15:48 | Re: speed up unicode normalization quick check |
| Previous Message | vignesh C | 2020-10-19 12:35:53 | Re: Parallel copy |