github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-22 22:56:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

doc: add two notes on section related to configuration files

Browse Source 
Add notes to the documention mentioning that after postgres or repmgr
upgrades (postgres major upgrades), there are some changes that need
to be taken care of.

Signed-off-by: Martín Marqués <martin.marques@2ndquadrant.com>
This commit is contained in:
Martín Marqués
2020-08-05 17:54:25 -03:00
committed by Ian Barwick
parent 2371f30f8a
commit 22f2ee3050
1 changed files with 24 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
doc/configuration-file.xml
View File

@@ -211,5 +211,29 @@ conninfo='host=node1 user=repmgr dbname=repmgr connect_timeout=2'</programlistin
</para>
</note>
<note>
<para>
When upgrading the PostgreSQL cluster to a new major version, updating the &repmgr; configuration file
may be needed. In particular, if default package locations for <option>pg_bindir</option> and
<option>data_directory</option> are used, both these options in <filename>repmgr.conf</filename>
will need to be updated accordingly.
</para>
</note>
<note>
<para>
If the location of the configuration file changed after a PostgreSQL major upgrade, the
<option>config_file</option> field from the <structname>repmgr.nodes</structname> table will
need to reflect this change. This can be accomplished by forcing all nodes to register
again with the new configuration file. This will effectively update the <option>config_file</option>
field in <structname>repmgr.nodes</structname>. To accomplished this, just
execute <link linkend="repmgr-primary-register">
<command>repmgr primary register --force -f /path/to/repmgr.conf</command></link>
on the primary node, and then <link linkend="repmgr-standby-register">
<command>repmgr standby register --force -f /path/to/repmgr.conf</command></link>
on all the standby nodes (don't forget the witness, if there is one).
</para>
</note>
</sect2>
</sect1>