diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2018-11-28 12:36:49 +0100 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2018-11-28 13:55:54 +0100 |
| commit | f2cbffc7a6183a359b339cfed65e9d609de756f0 (patch) | |
| tree | d15bf1bbe2a53623d2477aa6a60a2e7b3285a984 /src/test/modules/commit_ts | |
| parent | eae9143d9a70116a8ac4b3195454942140e5afb5 (diff) | |
| download | postgresql-f2cbffc7a6183a359b339cfed65e9d609de756f0.tar.gz postgresql-f2cbffc7a6183a359b339cfed65e9d609de756f0.zip | |
Only allow one recovery target setting
The previous recovery.conf regime accepted multiple recovery_target*
settings and used the last one. This does not translate well to the
general GUC system. Specifically, under EXEC_BACKEND, the settings
are written out not in any particular order, so the order in which
they were originally set is not available to new processes.
Rather than redesign the GUC system, it was decided to abandon the old
behavior and only allow one recovery target setting. A second setting
will cause an error. However, it is allowed to set the same parameter
multiple times or unset a parameter and set a different one.
Discussion: https://www.postgresql.org/message-id/flat/27802171543235530%40iva2-6ec8f0a6115e.qloud-c.yandex.net#701a59c837ad0bf8c244344aaf3ef5a4
Diffstat (limited to 'src/test/modules/commit_ts')
0 files changed, 0 insertions, 0 deletions