Replace 9.4 with 10, as that's the minimal version we support now with 5.4.1

Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>
Adding Postgres version 16 support in 5.4.1
2026-03-23 15:16:29 +00:00 · 2023-11-16 11:09:25 +00:00 · 2023-11-16 10:23:15 +00:00 · 2023-07-04 10:25:29 -03:00 · 2023-07-04 14:56:54 +02:00 · 2023-07-04 14:56:52 +02:00
9 changed files with 66 additions and 13 deletions
--- a/6
+++ b/6
@@ -1,3 +1,9 @@
+5.4.1   2023-07-04
+        repmgrd: ensure witness node metadata is updated (Ian)
+
+5.4.0   2023-03-16
+        Support cloning replicas using pg-backup-api
+
 5.3.3   2022-10-17
        Support for PostgreSQL added
        repmgrd: ensure event notification script is called for event
--- a/README.md
+++ b/README.md
@@ -8,7 +8,7 @@ replication, and perform administrative tasks such as failover or switchover
 operations.

 The most recent `repmgr` version (5.3.2) supports all PostgreSQL versions from
-9.5 to 14. PostgreSQL 9.4 is also supported, with some restrictions.
+9.5 to 15. PostgreSQL 9.4 is also supported, with some restrictions.

 `repmgr` is distributed under the GNU GPL 3 and maintained by EnterpriseDB.

--- a/configure.in
+++ b/configure.in
@@ -1,8 +1,8 @@
-AC_INIT([repmgr], [5.4.0], [repmgr@googlegroups.com], [repmgr], [https://repmgr.org/])
+AC_INIT([repmgr],[5.4.1],[repmgr@googlegroups.com],[repmgr],[https://www.repmgr.org/])

 AC_COPYRIGHT([Copyright (c) 2010-2021, EnterpriseDB Corporation])

-AC_CONFIG_HEADER(config.h)
+AC_CONFIG_HEADERS([config.h])

 AC_ARG_VAR([PG_CONFIG], [Location to find pg_config for target PostgreSQL (default PATH)])

--- a/doc/appendix-release-notes.xml
+++ b/doc/appendix-release-notes.xml
@@ -16,8 +16,44 @@
  </para>

  <!-- remember to update the release date in ../repmgr_version.h.in -->
+  <sect1 id="release-5.4.1">
+    <title id="release-current">Release 5.4.1</title>
+    <para><emphasis>Tue 04 July, 2023</emphasis></para>
+    <para>
+      &repmgr; 5.4.1 is a minor release providing a fix for witness metadata update
+    </para>
+    <sect2>
+      <title>Bug fixes</title>
+      <para>
+        <itemizedlist>
+          <listitem>
+            <para>
+              &repmgrd;: ensure witness node metadata is updated if the primary
+              node changed while the witness &repmgrd; was not running.
+            </para>
+          </listitem>
+        </itemizedlist>
+      </para>
+    </sect2>
+  </sect1>
+
+  <sect1 id="release-5.4.0">
+    <title>Release 5.4.0</title>
+    <para><emphasis>Thu 15 March, 2023</emphasis></para>
+    <para>
+      &repmgr; 5.4.0 is a major release.
+    </para>
+    <para>
+      This release provides support for cloning standbys using backups taken with <ulink url="http://www.pgbarman.org">barman</ulink>
+      with the use of <ulink url="https://github.com/EnterpriseDB/pg-backup-api">pg-backup-api</ulink>.
+    </para>
+    <para>
+      Minor fixes to the documentation.
+    </para>
+  </sect1>
+
  <sect1 id="release-5.3.3">
-    <title id="release-current">Release 5.3.3</title>
+    <title>Release 5.3.3</title>
    <para><emphasis>Mon 17 October, 2022</emphasis></para>
    <para>
      &repmgr; 5.3.3 is a minor release providing support for
--- a/doc/configuration-file-optional-settings.xml
+++ b/doc/configuration-file-optional-settings.xml
@@ -10,8 +10,8 @@
  <note>
    <simpara>
      This section documents a subset of optional configuration settings; for a full
-      for a full and annotated view of all configuration options see the
-      see the <ulink url="https://raw.githubusercontent.com/EnterpriseDB/repmgr/master/repmgr.conf.sample">sample repmgr.conf file</ulink>
+      and annotated view of all configuration options see the
+      <ulink url="https://raw.githubusercontent.com/EnterpriseDB/repmgr/master/repmgr.conf.sample">sample repmgr.conf file</ulink>
    </simpara>
  </note>

--- a/doc/install-requirements.xml
+++ b/doc/install-requirements.xml
@@ -14,7 +14,7 @@
  </para>

  <para>
-   &repmgr; &repmgrversion; is compatible with all PostgreSQL versions from 9.4. See
+   &repmgr; &repmgrversion; is compatible with all PostgreSQL versions from 10. See
   section <link linkend="install-compatibility-matrix">&repmgr; compatibility matrix</link>
   for an overview of version compatibility.
  </para>
@@ -120,13 +120,13 @@
              &repmgr; 5.4
            </entry>
            <entry>
-              (dev)
+              YES
            </entry>
            <entry>
              <link linkend="release-current">&repmgrversion;</link> (&releasedate;)
            </entry>
            <entry>
-              9.4, 9.5, 9.6, 10, 11, 12, 13, 15
+              10, 11, 12, 13, 14, 15, 16
            </entry>
            <entry>
              &nbsp;
--- a/doc/repmgr.xml
+++ b/doc/repmgr.xml
@@ -26,7 +26,7 @@
  <abstract>
   <para>
   This is the official documentation of &repmgr; &repmgrversion; for
-   use with PostgreSQL 9.4 - PostgreSQL 15.
+   use with PostgreSQL 10 - PostgreSQL 16.
   </para>
   <para>
     &repmgr; is being continually developed and we strongly recommend using the
--- a/repmgr_version.h.in
+++ b/repmgr_version.h.in
@@ -1,7 +1,7 @@
 #define REPMGR_VERSION_DATE ""
-#define REPMGR_VERSION "5.4dev"
-#define REPMGR_VERSION_NUM 50400
+#define REPMGR_VERSION "5.4.1"
+#define REPMGR_VERSION_NUM 50401
 #define REPMGR_EXTENSION_VERSION "5.4"
 #define REPMGR_EXTENSION_NUM 50400
-#define REPMGR_RELEASE_DATE "2022-XX-XX"
+#define REPMGR_RELEASE_DATE "2023-07-04"
 #define PG_ACTUAL_VERSION_NUM 
--- a/repmgrd-physical.c
+++ b/repmgrd-physical.c
@@ -2394,6 +2394,17 @@ monitor_streaming_witness(void)
 			terminate(ERR_BAD_CONFIG);
 		}

+		/*
+		 * It's possible that the primary changed while the witness repmgrd was not
+		 * running. This does not affect the functionality of the witness repmgrd, but
+		 * does mean outdated node metadata will be displayed, so update that.
+		 */
+		if (local_node_info.upstream_node_id != primary_node_id)
+		{
+			update_node_record_set_upstream(primary_conn, local_node_info.node_id, primary_node_id);
+			local_node_info.upstream_node_id = primary_node_id;
+		}
+
 		initPQExpBuffer(&event_details);

 		appendPQExpBuffer(&event_details,
Author	SHA1	Message	Date
Martín Marqués	bd60929910	Replace 9.4 with 10, as that's the minimal version we support now with 5.4.1 Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>	2023-11-16 11:09:25 +00:00
Martín Marqués	82ff0d6873	Adding Postgres version 16 support in 5.4.1 We've done extensive testing of the current version of repmgr against the new version 16 of Postgres. The tests have passed which gives us the green light to add the version as supported in repmgr 5.4.1. The commit only addresses documentation amendments Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>	2023-11-16 10:23:15 +00:00
Martín Marqués	26f9cb3f95	Merge pull request #817 from EnterpriseDB/generate-5.4.1-release Generate 5.4.1 release	2023-07-04 10:25:29 -03:00
Sidorov Pavel	890cbd9fca	Update README.md upd upper version according to https://repmgr.org	2023-07-04 14:56:54 +02:00
Mario Gonzalez	440ba5fbb4	configure.in: bumping to 5.4.1 release. This release contains all changes related to the new pg-backupapi mode along with the related documentation. In the previous release, we didn't include any documentation at all, just the required C code.	2023-07-04 14:56:52 +02:00
Martín Marqués	20f39e2fbe	Add release notes for repmgr release 5.4.0 This release added support for pg-backup-api. Here we add the release notes which expose the new feature. Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>	2023-07-04 14:55:32 +02:00
Martín Marqués	afdeb5d7b2	Various improvements and fixes to the pg-backup-api restore section on the docs I added a paragraph at the beginning of the section on where to look for instructions on how to install the pg-backup-api rest API. Fixed typos and some gramatical changes. Also reworded the first paragraph (which is now the second one). Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>	2023-07-04 14:52:15 +02:00
Martín Marqués	7d45ab04b3	New sect1 block has to be inside the sect1. The closing tag has to go at the end. Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>	2023-07-04 14:52:05 +02:00
Mario Gonzalez	7af74c4fda	Adding new mode to clone standbys. repmgr v5.4.0 supports this new mode called `pg_backupapi` which is enabled by defining `pg_backupapi_host` in repmgr.conf.	2023-07-04 14:48:24 +02:00
Martín Marqués	1010aeb3dd	Merge pull request #816 from EnterpriseDB/dev/fix-documentation-typos Fix documentation typos	2023-07-04 09:11:44 -03:00
Martín Marqués	c58c95c9f1	Typo in the documentation Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>	2023-07-04 14:08:53 +02:00
Dee Dee Rothery	3887637f1e	Update configuration-file-optional-settings.xml	2023-07-04 14:08:44 +02:00
Israel Barth Rubio	7a84e34630	Bump version number 5.4.1 Signed-off-by: Israel Barth Rubio <israel.barth@enterprisedb.com>	2023-07-04 08:41:22 -03:00
Ian Barwick	9ab4acea78	repmgrd: ensure witness node metadata is updated If the primary changed while the witness repmgrd was not running, ensure the witness's upstream node ID is updated when the witness repmgrd is restarted.	2023-06-08 16:39:52 +09:00
Martín Marqués	ef962436f7	Add release notes for repmgr release 5.4.0 This release added support for pg-backup-api. Here we add the release notes which expose the new feature. Signed-off-by: Martín Marqués <martin.marques@enterprisedb.com>	2023-03-24 18:34:53 +00:00