From 387ec70322aaf60127537bc200e20791f0b415ae Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Wed, 1 Nov 2017 10:50:24 -0400 Subject: [PATCH] doc: Add to hot standby documentation Document the order of changing certain settings when using hot-standby servers. This is just a logical consequence of what was already documented, but it gives the users some more practical advice. Author: Yorick Peterse Reviewed-by: Aleksander Alekseev Reviewed-by: Robert Haas --- doc/src/sgml/high-availability.sgml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index 086d6abb30..aa780d360d 100644 --- a/doc/src/sgml/high-availability.sgml +++ b/doc/src/sgml/high-availability.sgml @@ -2147,7 +2147,12 @@ LOG: database system is ready to accept read only connections The setting of some parameters on the standby will need reconfiguration if they have been changed on the primary. For these parameters, the value on the standby must - be equal to or greater than the value on the primary. If these parameters + be equal to or greater than the value on the primary. + Therefore, if you want to increase these values, you should do so on all + standby servers first, before applying the changes to the primary server. + Conversely, if you want to decrease these values, you should do so on the + primary server first, before applying the changes to all standby servers. + If these parameters are not set high enough then the standby will refuse to start. Higher values can then be supplied and the server restarted to begin recovery again. These parameters are: -- 2.40.0