| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Venkata B Nagothi <nag1010(at)gmail(dot)com> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: patch proposal |
| Date: | 2016-08-17 13:27:22 |
| Message-ID: | 20160817132722.GT4028@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Venkata,
* Venkata B Nagothi (nag1010(at)gmail(dot)com) wrote:
> Agreed. Additional option like "pause" would. As long as there is an option
> to ensure following happens if the recovery target is not reached -
>
> a) PG pauses the recovery at the end of the WAL
> b) Generates a warning in the log file saying that recovery target point
> is not reached (there is a patch being worked upon on by Thom on this)
> c) Does not open-up the database exiting from the recovery process by
> giving room to resume the replay of WALs
One thing to consider is just how different this is from simply bringing
PG up as a warm standby instead, with the warning added to indicate if
the recovery point wasn't reached.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ryan Murphy | 2016-08-17 13:28:22 | Re: Patch: initdb: "'" for QUOTE_PATH (non-windows) |
| Previous Message | Andrew Gierth | 2016-08-17 13:12:09 | Re: EXLCUDE constraints and Hash indexes |