Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1eKjFN-00014m-CJ
	for pgsql-docs@arkaria.postgresql.org; Fri, 01 Dec 2017 11:12:45 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.84_2)
	(envelope-from <pgsql-docs-owner+archive@lists.postgresql.org>)
	id 1eKjFM-0001xY-W7
	for pgsql-docs@arkaria.postgresql.org; Fri, 01 Dec 2017 11:12:44 +0000
Received: from makus.postgresql.org ([2001:4800:1501:1::229])
	by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256)
	(Exim 4.84_2)
	(envelope-from <a.parfenov@postgrespro.ru>)
	id 1eKjFM-0001xO-JH
	for pgsql-docs@lists.postgresql.org; Fri, 01 Dec 2017 11:12:44 +0000
Received: from mail.postgrespro.ru ([93.174.131.138])
	by makus.postgresql.org with esmtp (Exim 4.89)
	(envelope-from <a.parfenov@postgrespro.ru>)
	id 1eKjFJ-0003q3-59
	for pgsql-docs@postgresql.org; Fri, 01 Dec 2017 11:12:43 +0000
Received: from localhost (localhost [127.0.0.1])
	by mail.postgrespro.ru (Postfix) with ESMTP id 26CF221C1ED3
	for <pgsql-docs@postgresql.org>; Fri,  1 Dec 2017 14:12:38 +0300 (MSK)
X-Virus-Scanned: Debian amavisd-new at postgrespro.ru
Received: from asp437-24-g082ur (unknown [31.173.148.242])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(Client did not present a certificate)
	by mail.postgrespro.ru (Postfix) with ESMTPSA id CBE3921C1692
	for <pgsql-docs@postgresql.org>; Fri,  1 Dec 2017 14:12:37 +0300 (MSK)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru;
	s=mail; t=1512126757;
	bh=laBn7C768vukHykeNVpb11BUmq9tPduGmugxC9hY10g=;
	h=Date:From:To:Subject;
	b=OuRijIkcaNpr5jZQNwmDRHaKWWEZjC+gNxIbLiSGpFxrMAbkgulWQcR/Fv7JDyBSZ
	 bXjx0YKr/TpS1YRWcElaNyaZvXIvDTkS/+gbPvnMpggmFzWpm5lGcVlRhHZFEqT+/e
	 faHjZnYWga7V6Yzpzc8vJFEbYiXHMWnYQyxWZlX4=
Date: Fri, 1 Dec 2017 14:12:36 +0300
From: Aleksandr Parfenov <a.parfenov@postgrespro.ru>
To: pgsql-docs@postgresql.org
Subject: Replication parameters in recovery.conf
Message-ID: <20171201141236.35f6a90d@asp437-24-g082ur>
X-Mailer: Claws Mail 3.13.2 (GTK+ 2.24.30; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
List-Id: <pgsql-docs.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-docs@lists.postgresql.org>
List-Owner: <mailto:pgsql-docs-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-docs>
Precedence: bulk

Hello,

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?

-- 
Aleksandr Parfenov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company