| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: doc: Further clarify how recovery target parameters are applied |
| Date: | 2019-11-05 13:21:23 |
| Message-ID: | 20191105132123.GA1578@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-11-05 16:42:38 | pgsql: Generate EquivalenceClass members for partitionwise child join r |
| Previous Message | Alvaro Herrera | 2019-11-05 13:11:01 | pgsql: Change pg_restore -f- to dump to stdout instead of to ./- |