| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Leif Gunnar Erlandsen <leif(at)lako(dot)no>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pause recovery if pitr target not reached |
| Date: | 2019-10-19 19:45:11 |
| Message-ID: | 4b29d878-15c1-6681-840b-14e88a8f995f@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-09-17 13:23, Leif Gunnar Erlandsen wrote:
> This patch allows PostgreSQL to pause recovery before PITR target is reached
> if recovery_target_time is specified.
>
> Missing WAL's could then be restored from backup and applied on next restart.
>
> Today PostgreSQL opens the database in read/write on a new timeline even when
> PITR tareg is not reached.
I think this idea is worth thinking about. I don't think this should be
specific to a time-based recovery target. This could apply for example
to a target xid as well. Also, there should be a way to get the old
behavior. Perhaps this whole thing should be a new
recovery_target_action, say, 'pause_unless_reached'.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ariadne Conill | 2019-10-19 19:49:29 | Re: jsonb_set() strictness considered harmful to data |
| Previous Message | Tomas Vondra | 2019-10-19 19:27:23 | Re: jsonb_set() strictness considered harmful to data |