From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
Cc: | Leif Gunnar Erlandsen <leif(at)lako(dot)no>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pause recovery if pitr target not reached |
Date: | 2019-11-05 02:52:07 |
Message-ID: | CAHGQGwHxhzymBjuLM4+o1vkNY3Zwd77SaM-NfbvY3R5kKejzkw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Nov 1, 2019 at 9:41 PM Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>
> On 2019-10-21 08:44, Fujii Masao wrote:
> > Probably we can use standby mode + recovery target setting for
> > the almost same purpose. In this configuration, if end-of-WAL is reached
> > before recovery target, the startup process keeps waiting for new WAL to
> > be available. Then, if recovery target is reached, the startup process works
> > as recovery_target_action indicates.
>
> So basically get rid of recovery.signal mode and honor recovery target
> parameters in standby mode?
Yes, currently not only archive recovery mode but also standby mode honors
the recovery target settings.
> That has some appeal because it simplify
> this whole space significantly, but perhaps it would be too confusing
> for end users?
This looks less confusing than extending archive recovery. But I'd like to
hear more opinions about that.
Regards,
--
Fujii Masao
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2019-11-05 03:04:25 | Re: Run-time pruning for ModifyTable |
Previous Message | Bruce Momjian | 2019-11-05 02:48:19 | Re: PostgreSQL 12 installation fails because locale name contained non-english characters |