Alexander KukushkinandGitHub 3d29cb7e50 Perform pg_ctl reload regardless of config changes (#1204) ...

It is possible that some config files are not controlled by Patroni and when somebody is doing reload via REST API or by sending SIGHUP to Patroni process the usual expectation is that postgres will also be reloaded, but it didn't happen when there were no changes in the postgresql section of Patroni config.

For example one might replace ssl_cert_file and ssl_key_file on the filesystem and starting from PostgreSQL 10 it just requires a reload, but Patroni wasn't doing it.

In addition to that fix the issue with handling of `wal_buffers`. The default value depends on `shared_buffers` and `wal_segment_size` and therefore Patroni was exposing pending_restart when the new value in the config was explicitly set to -1 (default).

Close https://github.com/zalando/patroni/issues/1198

2019-10-10 14:49:30 +02:00

..

steps

A couple of small improvements in acceptance tests (#1057)

2019-05-13 16:33:19 +02:00

backup_create.sh

Custom bootstrap (#454)

2017-07-18 15:12:58 +02:00

backup_restore.sh

Custom bootstrap (#454)

2017-07-18 15:12:58 +02:00

basic_replication.feature

[WIP] Standby cluster implementation (#679)

2018-09-07 10:10:56 +02:00

callback.sh

Permanent replication slots (#819)

2018-10-31 11:37:42 +01:00

cascading_replication.feature

Add synchronous replication support. (#314)

2016-10-19 16:12:51 +02:00

custom_bootstrap.feature

Custom bootstrap (#454)

2017-07-18 15:12:58 +02:00

environment.py

A couple of small improvements in acceptance tests (#1057)

2019-05-13 16:33:19 +02:00

patroni_api.feature

Perform pg_ctl reload regardless of config changes (#1204)

2019-10-10 14:49:30 +02:00

standby_cluster.feature

A couple of small improvements in acceptance tests (#1057)

2019-05-13 16:33:19 +02:00

watchdog.feature

Fix watchdog on Python 3 (#531)

2017-09-29 10:27:10 +02:00