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

From: Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>
To: Yorick Peterse <yorickpeterse(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] Document the order of changing certain settings when using hot-standby servers
Date: 2017-04-07 12:55:29
Message-ID: 20170407155529.7b9571e5@e754
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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)
> you need to do so on a primary first, before applying it to any
> secondaries.

I'm sorry to inform you that your description of max_connection is,
lets say, not quite accurate. I've just increased max_connections on a
standby without doing anything on a master and nothing wrong happened.

--
Best regards,
Aleksander Alekseev

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-04-07 13:06:23 Re: [PATCH] Document the order of changing certain settings when using hot-standby servers
Previous Message Michael Paquier 2017-04-07 12:31:51 Re: Implementation of SASLprep for SCRAM-SHA-256