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

Add section about upgrading

Browse Source
This commit is contained in:
Ian Barwick
2017-10-10 09:32:14 +09:00
parent 08878831fe
commit 034e501039
4 changed files with 28 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
doc/filelist.sgml
View File

@@ -44,6 +44,7 @@
<!ENTITY follow-new-primary SYSTEM "follow-new-primary.sgml"> <!ENTITY follow-new-primary SYSTEM "follow-new-primary.sgml">
<!ENTITY switchover SYSTEM "switchover.sgml"> <!ENTITY switchover SYSTEM "switchover.sgml">
<!ENTITY event-notifications SYSTEM "event-notifications.sgml"> <!ENTITY event-notifications SYSTEM "event-notifications.sgml">
<!ENTITY upgrading-repmgr SYSTEM "upgrading-repmgr.sgml">
<!ENTITY repmgrd-automatic-failover SYSTEM "repmgrd-automatic-failover.sgml"> <!ENTITY repmgrd-automatic-failover SYSTEM "repmgrd-automatic-failover.sgml">
<!ENTITY repmgrd-configuration SYSTEM "repmgrd-configuration.sgml"> <!ENTITY repmgrd-configuration SYSTEM "repmgrd-configuration.sgml">

1
doc/repmgr.sgml
View File

@@ -74,6 +74,7 @@
&follow-new-primary; &follow-new-primary;
&switchover; &switchover;
&event-notifications; &event-notifications;
&upgrading-repmgr;
</part> </part>
<part id="using-repmgrd"> <part id="using-repmgrd">

7
doc/repmgrd-degraded-monitoring.sgml
View File

@@ -1,9 +1,9 @@
<chapter id="repmgrd-degraded-monitoring"> <chapter id="repmgrd-degraded-monitoring">
<title>"degraded monitoring" mode</title> <title>"degraded monitoring" mode</title>
<para> <para>
In certain circumstances, `repmgrd` is not able to fulfill its primary mission In certain circumstances, <command>repmgrd</command> is not able to fulfill its primary mission
of monitoring the nodes' upstream server. In these cases it enters "degraded of monitoring the nodes' upstream server. In these cases it enters "degraded
monitoring" mode, where `repmgrd` remains active but is waiting for the situation monitoring" mode, where <command>repmgrd</command> remains active but is waiting for the situation
to be resolved. to be resolved.
</para> </para>
<para> <para>
@@ -62,7 +62,8 @@
</para> </para>
<para> <para>
By default, <literal>repmgrd</literal> will continue in degraded monitoring mode indefinitely. By default, <literal>repmgrd</literal> will continue in degraded monitoring mode indefinitely.
However a timeout (in seconds) can be set with <varname>degraded_monitoring_timeout</varname>. However a timeout (in seconds) can be set with <varname>degraded_monitoring_timeout</varname>,
after which <command>repmgrd</command> will terminate.
</para> </para>

22
doc/upgrading-repmgr.sgml Normal file
View File

@@ -0,0 +1,22 @@
<chapter id="upgrading-repmgr" xreflabel="Upgrading repmgr">
<title>Upgrading repmgr</title>
<para>
&repmgr; is updated regularly with point releases (e.g. 4.0.1 to 4.0.2)
containing bugfixes and other minor improvements. Any substantial new
functionality will be included in a feature release (e.g. 4.0.x to 4.1.x).
</para>
<para>
&repmgr; is implemented as a PostgreSQL extension; to upgrade it, first
install the updated package, then in the database where the &repmgr;
extension is installed, execute <command>ALTER EXTENSION repmgr UPDATE</command>.
</para>
<para>
If <command>repmgrd</command> is running, it may be necessary to restart
the PostgreSQL server if the upgrade contains changes to the shared object
file used by <command>repmgrd</command>; check the release notes for details.
</para>
<sect1 id="upgrading-from-repmgr-3">
<title>Upgrading from repmgr 3</title>
</sect1>
</chapter>