On 5 September 2017 at 06:47, Daniel Gustafsson <daniel@yesql.se> wrote:
>> On 27 Mar 2017, at 10:27, Simon Riggs <simon@2ndquadrant.com> wrote:
>>
>> On 7 March 2017 at 23:31, Josh Berkus <josh@berkus.org> wrote:
>>> 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.
>>
>> I share your pain, but there are various things about this patch that
>> make me uncomfortable. I believe we are looking for an improved design
>> not just a different design.
>>
>> I think the best time to commit such a patch is at the beginning of a
>> new cycle, so people have a chance to pick out pieces they don't like
>> and incrementally propose changes.
>>
>> So I am going to mark this MovedToNextCF, barring objections from
>> committers willing to make it happen in this release.
>
> Next CF has now become This CF, has there been any work on this highly sought
> after patch? Would be good to get closure on this early in the v11 cycle.
I've not worked on this at all, so it isn't ready for re-review and commit.
I get the "lets do it early" thing and will try to extract a subset in October.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services