| From: | Sergei Kornilov <sk(at)zsrv(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Date: | 2018-11-26 13:22:56 |
| Message-ID: | 16874231543238576@iva4-24c534b4e3ac.qloud-c.yandex.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Hi
> What is the reason for allowing multiple recovery_target_* settings and
> taking the last one? Could we change this aspect to make this behave
> better?
Correct response to user configuration, similar to old recovery.conf logic or other GUC - we allow redefine with rule "latest win".
I think we can disallow using multiple recovery_target_* settings. But currently i have no good idea how this check can be done in check_* callbacks.
regards, Sergei
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-11-26 15:18:52 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| Previous Message | Michael Paquier | 2018-11-26 13:16:40 | Re: pgsql: Integrate recovery.conf into postgresql.conf |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Surafel Temesgen | 2018-11-26 13:25:41 | Re: COPY FROM WHEN condition |
| Previous Message | Michael Paquier | 2018-11-26 13:16:40 | Re: pgsql: Integrate recovery.conf into postgresql.conf |