Re: [HACKERS] [PATCH] Document the order of changing certain settings when using hot-standby servers

On 9/1/17 13:00, Robert Haas wrote: > Now you're proposing to add: > > 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

Re: [HACKERS] [PATCH] Document the order of changing certain settings when using hot-standby servers

On Thu, Apr 13, 2017 at 8:29 AM, Yorick Peterse wrote: > 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

Re: [HACKERS] [PATCH] Document the order of changing certain settings when using hot-standby servers

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

Re: [HACKERS] [PATCH] Document the order of changing certain settings when using hot-standby servers

Hi Yorick, > should do so on any standby servers first, before applying the changes to What you actually meant probably was "do so on ALL standby servers first", right? -- Best regards, Aleksander Alekseev signature.asc Description: PGP signature

Re: [HACKERS] [PATCH] Document the order of changing certain settings when using hot-standby servers

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

Re: [HACKERS] [PATCH] Document the order of changing certain settings when using hot-standby servers

Hi Yorick, > Attached is an updated version of the patch that corrects the order in > the documentation. Looks promising. I would recommend to add this patch to the next commitfest [1]. Otherwise there is a chance that it will be lost. [1] https://commitfest.postgresql.org/14/ -- Best

Re: [HACKERS] [PATCH] Document the order of changing certain settings when using hot-standby servers

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

Re: [HACKERS] [PATCH] Document the order of changing certain settings when using hot-standby servers

Aleksander, Yorick, * Aleksander Alekseev (a.aleks...@postgrespro.ru) wrote: > > 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

Re: [HACKERS] [PATCH] Document the order of changing certain settings when using hot-standby servers

Hi Yorick, > 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)

[HACKERS] [PATCH] Document the order of changing certain settings when using hot-standby servers

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