Re: [HACKERS] Proposal for changes to recovery.conf API - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: [HACKERS] Proposal for changes to recovery.conf API
Date
Msg-id 31ef2f65-c0fa-36a8-8ef7-06422498063d@berkus.org
Whole thread Raw
In response to Re: [HACKERS] Proposal for changes to recovery.conf API  (David Steele <david@pgmasters.net>)
Responses Re: Proposal for changes to recovery.conf API  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On 03/02/2017 07:13 AM, David Steele wrote:
> Hi Simon,
> 
> On 2/25/17 2:43 PM, Simon Riggs wrote:
>> On 25 February 2017 at 13:58, Michael Paquier <michael.paquier@gmail.com> wrote:
>>
>>> - trigger_file is removed.
>>> FWIW, my only complain is about the removal of trigger_file, this is
>>> useful to detect a trigger file on a different partition that PGDATA!
>>> Keeping it costs also nothing..
>>
>> Sorry, that is just an error of implementation, not intention. I had
>> it on my list to keep, at your request.
>>
>> New version coming up.
> 
> Do you have an idea when the new version will be available?

Please?  Having yet another PostgreSQL release go by without fixing
recovery.conf would make me very sad.


-- 
Josh Berkus
Containers & Databases Oh My!



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Bizarre choice of case for RELKIND_PARTITIONED_TABLE
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] cast result of copyNode()