| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Sergei Kornilov <sk(at)zsrv(dot)org>, Atsushi Torikoshi <atorik(at)gmail(dot)com> |
| Cc: | Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: replay pause vs. standby promotion |
| Date: | 2020-03-23 15:57:56 |
| Message-ID: | 0ecd1d4e-e8ed-887a-c800-4d250fe5eced@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020/03/24 0:17, Sergei Kornilov wrote:
> Hello
>
>> You meant that the promotion request should cause the recovery
>> to finish immediately even if there are still outstanding WAL records,
>> and cause the standby to become the master?
>
> Oh, I get your point. But yes, I expect that in case of promotion request during a pause, the user (me too) will want to have exactly the current state, not latest available in WALs.
Basically I'd like the promotion to make the standby replay all the WAL
even if it's requested during pause state. OTOH I understand there
are use cases where immediate promotion is useful, as you explained.
So, +1 to add something like "pg_ctl promote -m immediate".
But I'm afraid that now it's too late to add such feature into v13.
Probably it's an item for v14....
Regards,
--
Fujii Masao
NTT DATA CORPORATION
Advanced Platform Technology Group
Research and Development Headquarters
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2020-03-23 16:00:24 | Re: Define variables in the approprieate scope |
| Previous Message | Fujii Masao | 2020-03-23 15:57:15 | Re: replay pause vs. standby promotion |