README: clarify that the repmgr metadatabase must be part of the replication cluster

Update HISTORY
Merge branch 'master' of github.com:2ndQuadrant/repmgr into REL3_2_STABLE
2026-03-23 15:16:29 +00:00 · 2016-10-26 20:28:22 +09:00 · 2016-10-24 09:03:46 +09:00 · 2016-10-24 08:14:04 +09:00 · 2016-10-11 13:06:09 +09:00 · 2016-10-11 13:06:04 +09:00
3 changed files with 15 additions and 4 deletions
--- a/9
+++ b/9
@@ -1,3 +1,12 @@
+3.2.1   2016-10-24
+        repmgr: require a valid repmgr cluster name unless -F/--force
+          supplied (Ian)
+        repmgr: check master server is registered with repmgr before
+          cloning (Ian)
+        repmgr: ensure data directory defaults to that of the source node (Ian)
+        repmgr: various fixes to Barman cloning mode (Gianni, Ian)
+        repmgr: fix `repmgr cluster crosscheck` output (Ian)
+
 3.2     2016-10-05
        repmgr: add support for cloning from a Barman backup (Gianni)
        repmgr: add commands `standby matrix` and `standby crosscheck` (Gianni)
--- a/README.md
+++ b/README.md
@@ -121,7 +121,8 @@ views:
    status for each node

 The `repmgr` metadata schema can be stored in an existing database or in its own
-dedicated database.
+dedicated database. Note that the `repmgr` metadata schema cannot reside on a database
+server which is not part of the replication cluster managed by `repmgr`.

 A dedicated database superuser is required to own the meta-database as well as carry
 out administrative actions.
@@ -1072,8 +1073,9 @@ This will remove the standby record from `repmgr`'s internal metadata
 table (`repl_nodes`). A `standby_unregister` event notification will be
 recorded in the `repl_events` table.

-Note that this command will not stop the server itself or remove
-it from the replication cluster.
+Note that this command will not stop the server itself or remove it from
+the replication cluster. Note that if the standby was using a replication
+slot, this will not be removed.

 If the standby is not running, the command can be executed on another
 node by providing the id of the node to be unregistered using
--- a/version.h
+++ b/version.h
@@ -1,6 +1,6 @@
 #ifndef _VERSION_H_
 #define _VERSION_H_

-#define REPMGR_VERSION "3.3dev"
+#define REPMGR_VERSION "3.2.1"

 #endif
Author	SHA1	Message	Date
Ian Barwick	54a4d1e444	README: clarify that the repmgr metadatabase must be part of the replication cluster	2016-10-26 20:28:22 +09:00
Ian Barwick	d4b8c034e9	Update HISTORY	2016-10-24 09:03:46 +09:00
Ian Barwick	b8f4c35810	Merge branch 'master' of github.com:2ndQuadrant/repmgr into REL3_2_STABLE Bump version to 3.2.1	2016-10-24 08:14:04 +09:00
Ian Barwick	d2c09a1f71	repmgr: clean up runtime options structure Place elements in a sensible order and split the associated initializer macro over multiple lines for easier editing. Also move a few related global variables into to the structure to keep everything in the same place.	2016-10-11 13:06:09 +09:00
Ian Barwick	2389101ae9	"pg_logical/snapshot" -> "pg_logical/snapshots"	2016-10-11 13:06:04 +09:00
Gianni Ciolli	cbc2841433	When restoring from Barman, create pg_logical subdirectories Nodes cloned from Barman backups were missing these subdirectories, and so they were unable to start when promoted.	2016-10-11 13:05:48 +09:00
Ian Barwick	2bc877114c	repmgr: simplify LSN parsing Also silences a compiler warning.	2016-10-10 22:57:24 +09:00
Ian Barwick	30c5cc86f3	Update README Also reorder HISTORY entries.	2016-10-10 15:12:48 +09:00
Ian Barwick	b977b48aee	repmgr: standardize SSH-related error messages	2016-10-07 07:48:52 +09:00
Ian Barwick	108bdeb269	Add 'cluster crosscheck' to help output detail Per GitHub #243.	2016-10-06 07:39:29 +09:00
Ian Barwick	fefa43e3a6	Minor README fix	2016-10-05 16:49:01 +09:00
Ian Barwick	c1a1fe6f82	Update README `--ignore-external-config-files` deprecated	2016-10-05 16:48:40 +09:00
Ian Barwick	4dc3a05e8d	Update history	2016-10-05 13:58:05 +09:00
Ian Barwick	5945accd84	Add documentation for repmgrd failover process and failed node fencing Addresses GitHub #200.	2016-10-05 13:58:01 +09:00
Ian Barwick	15cbda9ec3	repmgr: consistent error message style	2016-10-05 13:57:57 +09:00
Ian Barwick	358559acc4	Update `barman-wal-restore` documentation Barman 2.0 provides this in a separate, more convenient `barman-cli` package; document this and add note about previous `barman-wal-restore.py` script.	2016-10-03 16:04:02 +09:00
Ian Barwick	0a9f8e160a	Tweak repmgr.conf.sample Put `monitor_interval_secs` at the start of the `repmgrd` section, as it's a very fundamental configuration item.	2016-10-03 16:03:59 +09:00
Ian Barwick	a2d67e85de	Bump version 3.2	2016-09-30 15:13:56 +09:00