| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, 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:15:06 |
| Message-ID: | 20181126181506.fyrwk42kt2hp4qni@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2018-11-26 15:09:43 -0300, Alvaro Herrera wrote:
> 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.
+1
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-11-26 18:30:18 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Previous Message | Alvaro Herrera | 2018-11-26 18:09:43 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2018-11-26 18:21:41 | Re: allow online change primary_conninfo |
| Previous Message | Alvaro Herrera | 2018-11-26 18:09:43 | Re: pgsql: Integrate recovery.conf into postgresql.conf |