The attached patch updates the hot-standby documentation (in the high
availability section) so it explicitly mentions that certain settings
need to be applied to servers in a particular order. For example, it
states that if you increase a certain setting (e.g. max_connections) you
need to do so on
Ha! It seems I indeed had it the other way around. I suppose that's what
happens when writing a patch late at night. Somewhat ironically I did
have the other correct in my Git commit message.
Attached is an updated version of the patch that corrects the order in
the documentation.
Yorick
diff
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
Done! It can be found at https://commitfest.postgresql.org/14/1110/
Thanks for reviewing thus far :)
Yorick
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
