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: update release notes and upgrade instructions

Browse Source
This commit is contained in:
Ian Barwick
2018-07-24 09:54:06 +09:00
parent 937cffd54c
commit 527a5f7fee
2 changed files with 36 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

28
doc/appendix-release-notes.sgml
View File

@@ -23,14 +23,34 @@
behaviour and some additional configuration parameters. behaviour and some additional configuration parameters.
</para> </para>
<para> <para>
&repmgr; 4.1.0 introduces changes to the &repmgr; extension schema, meaning This release can be installed as a simple package upgrade from repmgr 4.0 ~ 4.0.6.
<command>ALTER EXTENSION repmgr UPGRADE</command> must be executed after The following post-upgrade steps must be carried out:
installing the new version.
<itemizedlist>
<listitem>
<para>
<application>repmgrd</application> (if running) must be restarted.
</para> </para>
</listitem>
<listitem>
<para>
Execute <command>ALTER EXTENSION repmgr UPGRADE</command>
on the primary server in the database where &repmgr; is installed.
</para>
</listitem>
</itemizedlist>
A restart of the PostgreSQL server is <emphasis>not</emphasis> required
for this release.
</para>
<para>
See <xref linkend="upgrading-repmgr-extension"> for more details.
</para>
<para> <para>
Configuration changes are backwards-compatible and no changes to Configuration changes are backwards-compatible and no changes to
<filename>repmgr.conf</filename> are required. However users should <filename>repmgr.conf</filename> are required. However users should
review changes listed below. review the changes listed below.
</para> </para>
<sect2> <sect2>

18
doc/upgrading-repmgr.sgml
View File

@@ -29,8 +29,18 @@
</listitem> </listitem>
<listitem> <listitem>
<simpara> <simpara>
In the database where the &repmgr; extension is installed, execute <application>repmgrd</application> (if running) must be restarted.
<command>ALTER EXTENSION repmgr UPDATE</command>. </simpara>
</listitem>
<listitem>
<simpara>
For major releases, e.g. from <literal>4.0.x</literal> to <literal>4.1</literal>,
execute <command>ALTER EXTENSION repmgr UPDATE</command>
on the primary node in the database where the &repmgr; extension is installed.
</simpara>
<simpara>
This will update the extension metadata and, if necessary, apply
changes to the &repmgr; extension objects.
</simpara> </simpara>
</listitem> </listitem>
</orderedlist> </orderedlist>
@@ -41,10 +51,6 @@
release as they may contain upgrade instructions particular to individual versions. release as they may contain upgrade instructions particular to individual versions.
</para> </para>
<para>
If the <application>repmgrd</application> daemon is in use, we recommend stopping it
before upgrading &repmgr;.
</para>
<para> <para>
Note that it may be necessary to restart the PostgreSQL server if the upgrade contains Note that it may be necessary to restart the PostgreSQL server if the upgrade contains
changes to the shared object file used by <application>repmgrd</application>; check the changes to the shared object file used by <application>repmgrd</application>; check the