Aleksander,
> What you actually meant probably was "do so on ALL standby servers
> first", right?
Good point, right now it can give you the idea that applying it to just
1 standby (instead of all of them) is good enough, when instead you
need to apply it to all of them.
Attached is an adjusted version of my changes to better reflect this.
Yorick
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index 51359d6236..8f382d0b93 100644
*** a/doc/src/sgml/high-availability.sgml
--- b/doc/src/sgml/high-availability.sgml
***************
*** 2098,2104 **** LOG: database system is ready to accept read only connections
be equal to or greater than the value on the primary. 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:
<itemizedlist>
<listitem>
--- 2098,2108 ----
be equal to or greater than the value on the primary. 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. If you want to increase these values you
! should do so on all standby servers first, before applying the changes to
! the primary. If you instead want to decrease these values you should do so
! on the primary first, before applying the changes to all standby servers.
! These parameters are:
<itemizedlist>
<listitem>
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
