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

From: David Steele <david(at)pgmasters(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Abhijit Menon-Sen <ams(at)2ndQuadrant(dot)com>, 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>
Subject: Re: pgsql: Integrate recovery.conf into postgresql.conf
Date: 2018-11-26 15:56:29
Message-ID: 72494fee-3149-7fa9-f3f9-04268b6500ec@pgmasters.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 11/26/18 10:35 AM, Abhijit Menon-Sen wrote:
> At 2018-11-26 10:18:52 -0500, sfrost(at)snowman(dot)net wrote:
>>
>>> This came originally to check that recovery.conf handles correctly
>>> its recovery targets when multiple ones are defined with the last
>>> one winning […]
>>
>> Ugh, no, I don't agree that this property makes sense to keep and
>> since we're making these changes, I'd argue that it's exactly the
>> right time to do away with that.
>
> I strongly agree with everything Stephen said here.

+1.

--
-David
david(at)pgmasters(dot)net

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Sergei Kornilov 2018-11-26 16:39:49 Re: pgsql: Integrate recovery.conf into postgresql.conf
Previous Message Alvaro Herrera 2018-11-26 15:39:19 pgsql: Clarify that cross-row constraints are unsupported

Browse pgsql-hackers by date

  From Date Subject
Next Message Jakub Glapa 2018-11-26 16:00:30 Re: dsa_allocate() faliure
Previous Message Justin Pryzby 2018-11-26 15:52:08 Re: dsa_allocate() faliure