634 Commits

Author	SHA1	Message	Date
Ian Barwick	7969dc4800	Enable "node rejoin" to join a target with a lower timeline ... This has been possible since PostgreSQL 9.6, but the node rejoin/follow check did not consider this possibility.	2020-10-08 16:51:16 +09:00
Ian Barwick	4b524c52b6	standby clone: honour --waldir setting when cloning from Barman ... By setting --waldir in "pg_basebackup_options", standbys cloned using pg_basebackup would have their WAL directory set to the specified location and symlinked from the data directory. This commit causes repmgr to honour that setting even when cloning from Barman.	2020-10-07 15:13:52 +09:00
Ian Barwick	679cfe0852	doc: update release notes ... Note PostgreSQL 13 support as a general feature.	2020-10-06 14:17:16 +09:00
Ian Barwick	e86c035242	standby promote: in Pg13 and later, promotion overrides paused WAL replay ... Aborting in this case no longer makes sense, so we apply the checks to PostgreSQL 12 and earlier only.	2020-09-30 15:15:07 +09:00
Ian Barwick	73d2088a85	standby follow: don't restart server (PostgreSQL 13 and later) ... As of PostgreSQL 13, changes to the fundamental replication configuration can be applied with a simple SIGHUP, no restart required. In case the old behaviour is desired, i.e. a full restart to apply the configuration changes, the new configuration parameter "standby_follow_restart" can be set. This parameter has no effect in PostgreSQL 12 and earlier.	2020-09-29 17:53:51 +09:00
Ian Barwick	ce229beff8	repmgrd: add configuration option "always_promote" ... In certain corner cases, it's possible repmgrd may end up monitoring a standby which was a former primary, but the node record has not yet been updated. Previously repmgrd would abort the promotion with a cryptic message about being unable to find a node record for node_id -1 (the default value for an unknown node id). This commit addes a new configuration option "always_promote", which determines whether repmgrd should promote the node in this case. The default is "false", to effectively maintain the existing behaviour. Logging output has also been improved to make it clearer what has happened when this situation occurs.	2020-09-29 14:18:00 +09:00
Ian Barwick	70061c51aa	Further improve handling of possible pg_control read errors ... Builds on changes in commit 147f454, and ensures appropriate action is taken if a value cannot be read from pg_control.	2020-09-28 13:59:34 +09:00
Ian Barwick	26b5664741	repmgr: enable "primary unregister --force" to unregister an active primary ... The primary must have no registered standby nodes. Also document usage when unregistering a primary node which is actually running as a standby.	2020-09-23 15:12:19 +09:00
Ian Barwick	cb86180f4f	doc: document include directives	2020-09-18 16:27:52 +09:00
Ian Barwick	bccc2673b6	doc: update compatibility matrix	2020-09-18 11:40:47 +09:00
Ian Barwick	158008c5c5	doc: update release notes	2020-09-18 11:29:07 +09:00
Ian Barwick	5f3d1cdeb6	doc: note removal of PostgreSQL 9.3 support	2020-09-17 16:05:16 +09:00
Ian Barwick	82515a9733	doc: document new parameters for "failover_validation_command"	2020-09-17 15:48:18 +09:00
Ian Barwick	f1bdb09512	doc: note existing pg_rewind corner-case bug	2020-09-15 14:21:14 +09:00
Ian Barwick	028e3ab48d	doc: rearrange "repmgr node rejoin" reference for clarity ... The <important> section looked like an actual subsection, so convert that and the following example section into <refsect2> sections.	2020-09-15 13:42:18 +09:00
Ian Barwick	b5b7d635ad	doc: fix "release-current" tag	2020-09-04 15:12:33 +09:00
Ian Barwick	3945314e65	Remove PostgreSQL 9.3 support ... PostgreSQL 9.3 community support ended in November 2018.	2020-09-04 11:37:12 +09:00
Ian Barwick	9a836b3c04	Add option --verify-backup ... This causes pg_verifybackup to be executed immediately after pg_basebackup completes. PostreSQL 13 and later.	2020-09-03 10:40:32 +09:00
Ian Barwick	1131e3aad2	PostgreSQL 13: support "wal_keep_size" ... Renamed from "wal_keep_segments" in core commit f5dff459.	2020-08-31 17:18:41 +09:00
Ian Barwick	c50a2d049c	doc: note use of wildcards in .pgpass file	2020-08-19 10:32:34 +09:00
Ian Barwick	20100f5aaa	docs: link to PostgreSQL roadmap	2020-08-06 09:50:23 +09:00
Ian Barwick	2d20c110bf	doc: update "repmgr witness register" description ... Add missing "Options" section.	2020-08-06 09:50:19 +09:00
Ian Barwick	aed0045c3a	docs: reformat additonal config file upgrade notes into a new section ... It's easier to link to the information that way.	2020-08-06 09:50:16 +09:00
Martín Marqués	cd81046c26	doc: add two notes on section related to configuration files ... 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>	2020-08-06 09:50:11 +09:00
Ian Barwick	4d88f177a7	doc: clarify "node rejoin" usage ... Emphasize that conninfo must be provided for a running node.	2020-07-06 09:55:06 +09:00
Ian Barwick	547bbb06d8	doc: note downstream node (dis)connection monitoring in more places	2020-06-09 16:21:36 +09:00
Ian Barwick	f05978e2e1	doc: update example log output to match current code	2020-05-15 10:33:47 +09:00
Ian Barwick	72dfe28e81	doc: clarify usage of "-f /etc/repmgr.conf" in examples	2020-05-08 10:22:52 +09:00
Ian Barwick	6507a374f7	doc: update legacy upgrade procedure ... From PostgreSQL 13, the "CREATE EXTENSION ... FROM" syntax is no longer available. It's unlikely at this point that someone will find themselves with a PostgreSQL 13 database and the legacy repmgr schema, but we'll cover all bases just in case.	2020-05-01 10:27:33 +09:00
Ian Barwick	3200c8c4e4	doc: clarify usage of the "passfile" parameter.	2020-04-23 15:03:40 +09:00
Ian Barwick	f8b214f721	doc: have Makefile clean up generated html files	2020-04-20 15:40:13 +09:00
Ian Barwick	96acd3f915	doc: clarify .pgpass usage with -S/--superuser option	2020-04-20 15:34:29 +09:00
Ian Barwick	c1584d587c	doc: remove DEBUG output from example	2020-04-20 12:14:47 +09:00
Ian Barwick	2f26a02b5c	doc: clarify usage of -F/--force with "standby promote" ... Per GitHub #632.	2020-04-20 12:11:49 +09:00
Ian Barwick	e1953742a1	doc: note additional diagnostic options provided by "node check"	2020-04-17 11:53:56 +09:00
Ian Barwick	9df1731fb8	doc: update release notes	2020-04-15 14:50:51 +09:00
Ian Barwick	3d85d8f5ff	doc: update link to Debian package archive ... See also https://www.df7cb.de/blog/2020/apt-archive.postgresql.org.html	2020-04-14 12:32:59 +09:00
Ian Barwick	4f0e8a503a	doc: fix typo in 5.1.0 release section ID	2020-04-13 17:17:06 +09:00
Ian Barwick	c39289d570	doc: finalize release notes	2020-04-13 17:17:01 +09:00
Ian Barwick	662b603770	doc: update release notes	2020-04-13 17:16:55 +09:00
Ian Barwick	599bab590a	Create temporary pg.auto.conf file with the same permissions as the original ... Commit 0574279 set the file permissions to 0600 rather than the user's umask, but if initdb was executed with -g/--allow-group-access, the file is maintained with 0640, so we'll just maintain the existing permssions.	2020-04-07 13:29:59 +09:00
Ian Barwick	cd80f265ac	standby clone: warn about missing pg_rewind prerequisites ... These are not essential for cloning a standby, but useful to warn as early as possible in case the user is intending to use pg_rewind.	2020-04-06 15:37:37 +09:00
Ian Barwick	59159dede7	Ensure next release is 5.1, not 5.1.0	2020-04-03 14:57:17 +09:00
Ian Barwick	447054a630	standby promote: in --dry-run mode, display promote command which will be used ... For PostgreSQL 12 and later, explicitly note whether repmgr user has execution permissions on the pg_promote() function.	2020-04-02 12:37:32 +09:00
Ian Barwick	d998cab3d0	doc: add note about granting permissions on pg_promote()	2020-04-02 11:32:02 +09:00
Ian Barwick	7f460c88bf	doc: update "node check" examples ... Also add example output for a standby.	2020-03-31 11:09:00 +09:00
Ian Barwick	bffb8fa11b	node check: handle --upstream option when node is primary	2020-03-31 10:49:30 +09:00
Ian Barwick	d9cb38c7f0	node check: add --upstream option ... We have a --downstream option to check for attached nodes, but it would be useful to have a corresponding --upstream option too. A following patch will adapt the behaviour of this option when executed on the primary node.	2020-03-30 17:54:52 +09:00
Ian Barwick	e64349e4da	standby switchover: accept -S/--superuser option	2020-03-25 14:00:51 +09:00
Ian Barwick	2b06f2d1ae	node service: enable provision of the -S/--superuser option ... This is required to be able to execute a CHECKPOINT if the normal repmgr user is not a superuser.	2020-03-24 17:25:34 +09:00