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

From: Yorick Peterse <yorickpeterse(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: [PATCH] Document the order of changing certain settings when using hot-standby servers
Date: 2017-04-06 21:00:34
Message-ID: 63a9816d-9f3d-0ad3-c012-ae3dbcc789b9@gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

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.

Previously this was not explicitly mentioned and could lead to one
thinking they can just apply the setting to all servers in parallel,
resulting in standby servers refusing to start.

The exact phrasing currently used in the patch may be a bit rough, I'm
open to suggestions on how to best improve the writing.

The patch is based on the master branch and applies cleanly to it.

Yorick

Attachment Content-Type Size
document-hot-standby-config-order.patch text/x-patch 1.2 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2017-04-06 21:05:21 Re: increasing the default WAL segment size
Previous Message Andres Freund 2017-04-06 20:50:19 Re: parallel explain analyze support not exercised