| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | leif(at)lako(dot)no, michael(at)paquier(dot)xyz, masao(dot)fujii(at)gmail(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pause recovery if pitr target not reached |
| Date: | 2020-01-27 11:16:02 |
| Message-ID: | 0ab2dae6-9f3d-01bb-d760-9d94b90f92dc@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-01-15 05:02, Kyotaro Horiguchi wrote:
> FWIW, I restate this (perhaps) more clearly.
>
> At Wed, 15 Jan 2020 11:02:24 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
>> recvoery_target_* is not cleared after startup. If a server crashed
>> just after the last shutdown checkpoint, any recovery_target_* setting
>> prevents the server from starting regardless of its value.
>
> recvoery_target_* is not automatically cleared after a successful
> archive recovery. After that, if the server crashed just after the
> last shutdown checkpoint, any recovery_target_* setting prevents the
> server from starting regardless of its value.
Thank you for this clarification. Here is a new patch that addresses
that and also the other comments raised about my previous patch.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| v6-0001-Fail-if-recovery-target-is-not-reached.patch | text/plain | 6.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Asim Rama Praveen | 2020-01-27 11:40:55 | Re: Replication & recovery_min_apply_delay |
| Previous Message | Kyotaro Horiguchi | 2020-01-27 10:54:01 | Re: [PATCH] /src/backend/access/transam/xlog.c, tiny improvements |