mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-22 22:56:29 +00:00
standby follow: don't restart server (PostgreSQL 13 and later)
As of PostgreSQL 13, changes to the fundamental replication configuration can be applied with a simple SIGHUP, no restart required. In case the old behaviour is desired, i.e. a full restart to apply the configuration changes, the new configuration parameter "standby_follow_restart" can be set. This parameter has no effect in PostgreSQL 12 and earlier.
This commit is contained in:
@@ -79,11 +79,24 @@
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
<link linkend="repmgr-standby-follow">repmgr standby follow</link>:
|
||||
In PostgreSQL 13 and later, a standby no longer requires a restart to
|
||||
follow a new upstream node.
|
||||
</para>
|
||||
<para>
|
||||
The old behaviour (always restarting the standby to follow a new node)
|
||||
can be restored by setting the configuration file parameter
|
||||
<varname>standby_follow_restart</varname> to <literal>true</literal>.
|
||||
</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>
|
||||
<link linkend="repmgr-node-check">repmgr node check</link>:
|
||||
option <option>--db-connection</option> added to check if &repmgr; can connect to the database on the
|
||||
local node.
|
||||
option <option>--db-connection</option> added to check if &repmgr;
|
||||
can connect to the database on the local node.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
|
||||
Reference in New Issue
Block a user