| From: | "Leif Gunnar Erlandsen" <leif(at)lako(dot)no> |
|---|---|
| To: | "Peter Eisentraut" <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pause recovery if pitr target not reached |
| Date: | 2019-11-06 12:24:41 |
| Message-ID: | 70984256e4a76cfe0efd6f11af35c4ce@lako.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>"Peter Eisentraut" <peter(dot)eisentraut(at)2ndquadrant(dot)com> skrev 6. november 2019 kl. 08:32:
>
>> Btw., this discussion/patch seems related:
>> https://www.postgresql.org/message-id/flat/a3f650f1-fb0f-c913-a000-a4671f12a013(at)postgrespro(dot)ru
I have read through this other proposal. As far as I could see in the suggested patch, it does not solve the same problem.
It still stops recovery when the recovery process does not find any more WAL.
I would like the process to pause so administrator get to choose to find more WAL to apply.
My patch should probably be extended to include
RECOVERY_TARGET_XID, RECOVERY_TARGET_NAME, RECOVERY_TARGET_LSN as well as RECOVERY_TARGET_TIME.
---
Leif Gunnar Erlandsen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2019-11-06 12:27:05 | Re: Collation versioning |
| Previous Message | Dilip Kumar | 2019-11-06 12:10:52 | Re: Reorderbuffer crash during recovery |