| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Sergei Kornilov <sk(at)zsrv(dot)org>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Date: | 2018-11-26 13:16:40 |
| Message-ID: | 20181126131640.GD14598@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Mon, Nov 26, 2018 at 02:06:36PM +0100, Peter Eisentraut wrote:
> What is the reason for allowing multiple recovery_target_* settings and
> taking the last one?
This came originally to check that recovery.conf handles correctly its
recovery targets when multiple ones are defined with the last one
winning, as users may want to append additional targets in an existing
recovery.conf. I have not checked the code in details, but I think that
we should be careful to keep that property, even with EXEC_BACKEND.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2018-11-26 13:22:56 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Previous Message | Peter Eisentraut | 2018-11-26 13:06:36 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2018-11-26 13:22:56 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Previous Message | Peter Eisentraut | 2018-11-26 13:06:36 | Re: pgsql: Integrate recovery.conf into postgresql.conf |