| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Date: | 2018-11-26 16:39:49 |
| Message-ID: | 29465041543250389@iva4-f774db2b5297.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Hello
> 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.
How about something like attached patch?
regards, Sergei
| Attachment | Content-Type | Size |
|---|---|---|
| disallow_multiple_recovery_targets_v001.patch | text/x-diff | 8.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-11-26 17:21:18 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Previous Message | David Steele | 2018-11-26 15:56:29 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2018-11-26 16:43:20 | Re: B-tree cache prefetches |
| Previous Message | Dagfinn Ilmari =?utf-8?Q?Manns=C3=A5ker?= | 2018-11-26 16:34:32 | [PATCH] Improve tab completion for CREATE TABLE |