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

From Peter Eisentraut
Subject Re: [HACKERS] Proposal for changes to recovery.conf API
Date
Msg-id 9a1d1153-bbaa-f86f-182a-2e9f2ad4b7d8@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] Proposal for changes to recovery.conf API  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] Proposal for changes to recovery.conf API  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On 12/16/16 8:52 PM, Robert Haas wrote:
> If the explanation is just a few sentences long, I see no reason not
> to include it in the release notes.

As far as I can tell from the latest posted patch, the upgrade
instructions are

- To trigger recovery, create an empty file recovery.trigger instead of
recovery.conf.

- All parameters formerly in recovery.conf are now regular
postgresql.conf parameters.  For backward compatibility, recovery.conf
is read after postgresql.conf, but the parameters can now be put into
postgresql.conf if desired.

Some of that might be subject to patch review, but it's probably not
going to be much longer than that.  So I think that will fit well into
the usual release notes section.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Time to drop old-style (V0) functions?
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] pg_basebackups and slots