| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(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-01 12:41:46 |
| Message-ID: | 701fecc5-9e7e-5714-fefb-75aff571b3e5@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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? That has some appeal because it simplify
this whole space significantly, but perhaps it would be too confusing
for end users?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-11-01 12:49:15 | Re: Add a GUC variable that control logical replication |
| Previous Message | Peter Eisentraut | 2019-11-01 12:33:32 | Re: pglz performance |