Subject: Re: Replication parameters in recovery.conf
To: Aleksandr Parfenov <a.parfenov@postgrespro.ru>, pgsql-docs@postgresql.org
References: <20171201141236.35f6a90d@asp437-24-g082ur>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <c359ca55-d30f-45d9-7119-f34a27be152e@2ndquadrant.com>
Date: Tue, 5 Dec 2017 21:19:55 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0)
 Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <20171201141236.35f6a90d@asp437-24-g082ur>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

On 12/1/17 06:12, Aleksandr Parfenov wrote:
> Reading a documentation regarding recovery.conf file I found that the
> reason to store 'stand-by mode' configuration inside that file is not
> clear.
> 
> IMHO, a little note in description of recovery.conf will clearify
> the situation. Something like "a stand-by is submode of recover mode"
> and that the file used during replication will help. Same as in
> recovery.conf.sample file will be fine too.
> 
> What the community thinks about it?

The reasons for this are basically all historical and we are trying to
get rid of it (by moving these settings to postgresql.conf, mostly).  So
I don't think we need to spend a lot of time rationalizing this at this
point.

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