Commit Graph

1546 Commits

Author SHA1 Message Date
Ian Barwick d19ccf74e8 standby switchover: display "shutdown_check_timeout" value in --dry-run mode
It's useful to be aware of this setting.
2020-01-30 10:31:20 +09:00
Ian Barwick 7bcf736a06 doc: link to latest blog article 2020-01-30 10:23:48 +09:00
Ian Barwick fc678f97e3 Add missing values to action_name() 2020-01-29 15:35:20 +09:00
Ian Barwick 8b96b14397 standby switchover: fix repmgr execution confirmation in --dry-run mode
Inexplicably, "localhost" was hard-coded, rather than the remote host
name.
2020-01-29 14:07:35 +09:00
Ian Barwick 9319f212a9 standby switchover: improve wording of pending archive file messages 2020-01-29 14:07:30 +09:00
Ian Barwick f5bfba4a5a doc: minor clarifications to Debian package info 2020-01-24 10:46:56 +09:00
Ian Barwick e60d00543c doc: update repository links to https 2020-01-24 10:46:52 +09:00
Ian Barwick be79f1e2c9 doc: note availability of RHEL 8 packages 2020-01-07 09:45:24 +09:00
Renaud Fortier 84d83a383a Update repmgr.conf.sample
Add empty single quotes to promote_command and follow_command
2019-12-16 12:28:12 +09:00
Ian Barwick f288e7c6b5 repmgrd: fix configuration file reload handling
Usually repmgrd requires the parameters "promote_command" and
"follow_command" to be present in the configuration file. These are
not required if "failover=manual", but the configuration sanity check
following receipt of SIGHUP was not checking that.

Addresses issue reported in GitHub #614.
2019-12-16 11:35:41 +09:00
Ian Barwick 9d2d3296fb doc: update release notes 2019-12-10 16:48:36 +09:00
Ian Barwick 309f2a7000 standby follow: don't attempt to delete slot if new upstream is same as current
An attempt will be made to delete an existing replication slot on the
old upstream node (this is important during e.g. a switchover operation
or when attaching a cascaded standby to a new upstream). However if the
standby is currently attached to the follow target node anyway, the
replication slot should never be deleted.
2019-12-10 15:58:26 +09:00
Ian Barwick 656030b851 doc: add reference to "ssh_options"
This is listed in "repmgr.conf.sample" but not the main documentation.
2019-11-25 10:17:45 +09:00
Ian Barwick b535daed89 doc: link PgBouncer fencing document from main docs 2019-11-21 09:58:01 +09:00
Ian Barwick cd0ea1688c doc: document "tablespace_mapping" parameter.
This was previously only mentioned in "repmgr.conf.sample".
2019-11-20 16:54:49 +09:00
Ian Barwick 98021f1167 doc: fix minor punctuation typo 2019-11-11 15:54:59 +09:00
Ian Barwick d963558baf doc: ensure various repmgr.conf values are quoted appropriately 2019-11-08 11:50:29 +09:00
Ian Barwick b0bfed0495 doc: update repmgr.conf sample
Convert recovery.conf references to generic configuration descriptions,
and fix spacing.
2019-11-08 11:48:44 +09:00
Ian Barwick 017387dfd0 doc: clarify Barman configuation
Per confusion noted in GitHub #602.
2019-11-07 14:29:14 +09:00
Ian Barwick 0bde2fc00c standby clone: fix typo in log message 2019-10-28 14:09:31 +09:00
Ian Barwick ff48789ea3 doc: note superuser requirement for "repmgr primary register" 2019-10-25 12:44:49 +09:00
Ian Barwick 87fe68032a primary register: improve debug log output 2019-10-25 12:44:05 +09:00
Ian Barwick 0112843f1b doc: note permission requirements for "repmgr standby (promote|switchover)
Per issues noted in GitHub #595.
2019-10-25 11:54:50 +09:00
Ian Barwick 8065a443dd Clarify usage of log_db_error() function 2019-10-24 10:05:12 +09:00
Ian Barwick 446d7426ba doc: note which repmgr versions are supported in the compatibility matrix 2019-10-24 09:49:28 +09:00
Ian Barwick b4da7caa30 doc: update README
Link to compatibility matrix, support section.
2019-10-24 09:49:24 +09:00
Ian Barwick 2067c164fc doc: update README 2019-10-24 09:49:20 +09:00
Ian Barwick 4f0613cba2 Ensure postgresql.auto.conf is created with correct permissions 2019-10-18 16:47:42 +09:00
Ian Barwick 5bf05f7b2d Tweak "repmgr standby --help" output not to mention recovery.conf
Use the more generic "replication configuration" to cover Pg12
and later.
2019-10-18 14:11:39 +09:00
Ian Barwick 6c3b0dff4f doc: expand section about requesting support 2019-10-18 12:00:47 +09:00
Ian Barwick 676475dc1f doc: add link to blog entry about Pg12 replication configuration changes 2019-10-18 12:00:43 +09:00
Ian Barwick 39003be5a3 Change version number from 5.0 to 5.0.0
Previous initial "major" releases were two-element only (e.g. 4.4);
beginning from repmgr 5 we want to ensure all version numbers have
three elements, for general consistency, including the generation
of package names.
v5.0.0
2019-10-15 11:01:03 +09:00
Ian Barwick c27f134e50 doc: split notes about PostgreSQL 9.3 and 9.4 support into a new subsection 2019-10-15 10:46:14 +09:00
Ian Barwick 5a619244ee doc: add note about 4.x development policy 2019-10-15 10:42:52 +09:00
Ian Barwick b5448def7e doc: add repmgr 5.0 release date 2019-10-15 10:30:34 +09:00
Ian Barwick af1c889bc3 Bump version to 5.0 2019-10-14 15:10:40 +09:00
Ian Barwick 2304584679 Fix handling of upstream node change check
repmgrd has a check to see if the upstream node has unexpectedly
changed, e.g. if the repmgrd service is paused and the PostgreSQL
instance has been pointed to another node.

However this check was relying on the node record on the local node
being up-to-date, which may not be the case immediately after a
failover, when the node is still replaying records updated prior
to the node's own record being updated. In this case it will
mistakenly assume the node is following the original primary
and attempt to restart monitoring, which will fail as the original
primary is no longer available.

To prevent this, we check against the node's record on the upstream
node.

Addresses issue noted in GitHub #587 and #588.
2019-10-14 12:28:04 +09:00
Ian Barwick 4aaa24a5f8 Update configuration file conversion script
Ensure output is quoted.
2019-10-08 10:59:20 +09:00
Ian Barwick ea29af2e68 Remove mistakenly added file 2019-10-08 10:33:27 +09:00
Ian Barwick 7053ed5b51 doc: update links to Barman documentation 2019-10-08 10:30:41 +09:00
Ian Barwick a845d7126d doc: minor updates to "repmgr standby clone" reference
- remove references to repmgr 4.0.4 (present because feature
  was added in a minor release, but that's a long time ago)
- note configuration is appended to postgresql.auto.conf
2019-10-08 10:21:26 +09:00
Ian Barwick 1c317059cd doc: clarify use of --recovery-conf-only 2019-10-08 10:03:44 +09:00
Ian Barwick dcf5bfb649 doc: fix minor formatting error 2019-10-08 09:48:04 +09:00
Ian Barwick dbd3d34c89 doc; update repmgr.conf.sample
Note new PostgreSQL-style parsing and add link to documentation.
2019-10-07 18:28:16 +09:00
Ian Barwick f3c3320a9c doc: update examples in quickstart guide 2019-10-07 18:27:38 +09:00
Ian Barwick cfc5bde219 doc: update repmgr.conf samples in Barman section
From repmgr 5.x we really need to quote all the things.
2019-10-07 12:05:26 +09:00
Ian Barwick ea57269569 doc: improve instructions for cloning from Barman 2019-10-07 11:56:40 +09:00
Ian Barwick b885337abc Minor code formatting fix 2019-10-07 10:48:35 +09:00
Ian Barwick e8b5b92893 doc: improve Barman standby clone example 2019-10-03 15:52:32 +09:00
Ian Barwick 02bdcf657f doc: add link to FAQ section about 3rd party package compatibilty 2019-10-03 15:23:57 +09:00