Re: Proposal for changes to recovery.conf API
Fujii Masao <masao.fujii@gmail.com>
From: Fujii Masao <masao.fujii@gmail.com>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Bruce Momjian <bruce@momjian.us>,
Josh Berkus <josh@agliodbs.com>, Magnus Hagander <magnus@hagander.net>,
Michael Paquier <michael.paquier@gmail.com>, Andres Freund <andres@anarazel.de>, Abhijit Menon-Sen <ams@2ndquadrant.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-01-11T09:53:02Z
Lists: pgsql-hackers
On Tue, Jan 10, 2017 at 4:50 AM, Peter Eisentraut <peter.eisentraut@2ndquadrant.com> wrote: > On 1/1/17 4:14 PM, Simon Riggs wrote: >> OK, so here's the patch, plus doc cleanup patch. > > I don't think this patch is likely to succeed if we throw in more ideas > in every round. > > I think we have or are approaching agreement on moving recovery.conf > into postgresql.conf, making the settings reloadable, and adding signal > (formerly trigger) files to trigger recovery or standby. I think that > is a useful change, but it's already big enough and needs extensive > reviewing and testing. Agreed. It's better to focus on the "core" part of the patch firstly. Regards, -- Fujii Masao