| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Sergei Kornilov <sk(at)zsrv(dot)org>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Date: | 2018-11-26 18:09:43 |
| Message-ID: | 20181126180943.fdj3dkajqtqifekb@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2018-Nov-26, Stephen Frost wrote:
> I would think we'd have the different GUCs and then the check functions
> would only validate that they're valid inputs and then when we get to
> the point where we're starting to do recovery we check and make sure
> we've been given a sane overall configuration- which means that only
> *one* is set, and it matches the recovery target requested.
I don't quite understand why it isn't sensible to specify more than one
and just stop recovery (or whatever) when at least one of them becomes
true. Maybe I want to terminate just before commit of transaction
12345, but no later than 2018-11-11 12:47 in any case.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-11-26 18:15:06 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Previous Message | Tom Lane | 2018-11-26 17:41:49 | pgsql: Improve regression test coverage for psql output formats. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2018-11-26 18:15:06 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Previous Message | Daniel Verite | 2018-11-26 17:47:32 | Re: csv format for psql |