Re: pgsql: Integrate recovery.conf into postgresql.conf

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Sergei Kornilov <sk(at)zsrv(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgsql: Integrate recovery.conf into postgresql.conf
Date: 2018-11-28 17:14:10
Message-ID: 894ffa03-174b-e5da-9b2f-99b98119aca7@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 27/11/2018 15:16, Sergei Kornilov wrote:
> Hi
>
>> The attached seems to be the simplest way to fix this. (Needs
>> documentation updates, test updates, error message refinement.)
>
> Thank you!
> I add documentation change, tests and rephrased error message.

I have committed it along these lines. It ended up being a bit more
involved, in order to support setting the same parameter multiple times
or unsetting one parameter and setting another. But it should pass now
on EXEC_BACKEND.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Geoghegan 2018-11-28 22:44:24 pgsql: Have BufFileSize() ereport() on FileSize() failure.
Previous Message Peter Eisentraut 2018-11-28 13:25:06 pgsql: Only allow one recovery target setting

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2018-11-28 17:30:38 Re: pg_stat_ssl additions
Previous Message Mark Dilger 2018-11-28 16:55:21 Re: "SELECT ... FROM DUAL" is not quite as silly as it appears