| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>, Atsushi Torikoshi <atorik(at)gmail(dot)com>, 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:15 |
| Message-ID: | 9f45c80f-6441-f006-1036-8f182c6fe774@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020/03/23 23:55, Robert Haas wrote:
> On Mon, Mar 23, 2020 at 10:36 AM Fujii Masao
> <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>> If we would like to have the promotion method to finish recovery
>> immediately, IMO we should implement something like
>> "pg_ctl promote -m fast". That is, we need to add new method into
>> the promotion.
>
> I think 'immediate' would be a better choice. One reason is that we've
> used the term 'fast promotion' in the past for a different feature.
> Another is that 'immediate' might sound slightly scary to people who
> are familiar with what 'pg_ctl stop -mimmediate' does. And you want
> people doing this to be just a little bit scared: not too scared, but
> a little scared.
+1
When I proposed the feature five years before, I used "immediate"
as the option value.
https://postgr.es/m/CAHGQGwHtvyDqKZaYWYA9zyyLEcAKiF5P0KpcpuNE_tsrGTFtQw@mail.gmail.com
Regards,
--
Fujii Masao
NTT DATA CORPORATION
Advanced Platform Technology Group
Research and Development Headquarters
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-03-23 15:57:56 | Re: replay pause vs. standby promotion |
| Previous Message | Maxim Ivanov | 2020-03-23 15:41:15 | Re: optimisation? collation "C" sorting for GroupAggregate for all deterministic collations |