Date: Tue, 5 Nov 2019 10:21:23 -0300
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Fujii Masao <masao.fujii@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>,
	pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: doc: Further clarify how recovery target parameters are
 applied
Message-ID: <20191105132123.GA1578@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAHGQGwF7tLDk=M5tGZx=ROy_o2-n9fQ5v6-fnzBNF1yWxoEZoA@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On 2019-Oct-18, Fujii Masao wrote:

> > Thanks for improving the documentation.
> >
> > +     In this mode, the parameters from both this section and <xref
> > +     linkend="runtime-config-wal-recovery-target"/> will be used.  Parameters
> > +     from <xref linkend="runtime-config-replication-standby"/> will not be
> > +     used.
> >
> > The latter description seems not true. hot_standby and
> > max_standby_archive_delay in "runtime-config-replication-standby"
> > are used during archive recovery. So something like the following
> > change would need to be applied, I think. Patch attached.

This has not been applied, right?  Can you send a complete patch?

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services