b6264b77c4
repmgr: mandate explicit configuration for "daemon (start|stop)"
...
The initial implementation was designed to fall back to "manual"
start/stop of repmgrd if the "repmgrd_service_..._command" parameters
were not set.
However on reflection, this is too much of a potential footgun, so
we will mandate provision of these parameters.
2019-01-30 10:57:06 +09:00
9e7cb6d01c
doc: make it easier to find info about installation of old packages
2019-01-30 09:45:08 +09:00
0435bda115
Fix string comparison
2019-01-29 20:42:33 +09:00
a5aa47c1dd
daemon start/stop: add warning about missing configuration
...
repmgr will attempt to construct appropriate commands to start
and stop repmgrd, but usually it's preferable for them to be explicitly
defined, particularly if repmgr is installed from packages.
2019-01-29 14:08:00 +09:00
7654dd615b
Finalize "daemon (start|stop)" commands
...
Implements GitHub #528 .
2019-01-29 13:16:11 +09:00
c83e9870fe
doc: update "repmgr daemon (start|stop)" documentation
2019-01-29 13:01:36 +09:00
8b13d14294
"daemon stop": initial implementation
2019-01-29 13:01:23 +09:00
ba13172b3a
Add initial "repmgr daemon (start|stop)" documentation
2019-01-29 13:01:19 +09:00
32b81e7d49
"daemon start": initial implementation
2019-01-29 13:01:14 +09:00
cbfef17a1d
Fix check of --no-wait option
2019-01-29 12:29:05 +09:00
a48d408e4e
Consistently log strerror output as DETAIL
2019-01-29 12:10:55 +09:00
e5f50e7b99
doc: add additional index entries for repmgrd
2019-01-28 09:52:51 +09:00
aeea02b598
doc: update "standby follow" error codes
2019-01-24 10:43:38 +09:00
59eca2be30
node rejoin: improve error code handling
...
- return ERR_REJOIN_FAIL in all cases where the rejoin operation fails
- ensure ERR_FOLLOW_FAIL is not returned
- document error codes
2019-01-24 10:31:45 +09:00
dfe57d2406
"node rejoin": log pg_rewind command as DETAIL rather than DEBUG
2019-01-23 17:15:07 +09:00
061932d023
"node rejoin": verify status of rejoin target
...
This adapts the code previously added to "standby follow" to verify
whether the rejoin target can actually be rejoined.
2019-01-23 17:08:55 +09:00
3f5762e03a
Refactor upstream attachment check code
...
Move it from the "standby follow" code to an independent function so it can
be used in other contexts, e.g. "node rejoin".
2019-01-23 15:11:42 +09:00
42fa9a2a88
Log node rejoin failure as ERROR
2019-01-23 13:55:40 +09:00
f23065e041
Fix typo in log message
2019-01-23 13:53:29 +09:00
efe4a9c344
repmgrd: log receipt of SIGINT/SIGTERM
2019-01-23 13:44:59 +09:00
0970789b1d
doc: improve package install instructions
...
Including:
- additional clarification for Pg 9.x RPM package names
- consistent usage of sudo
2019-01-23 12:55:06 +09:00
07b79286b5
doc: clarify use-cases for pausing repmgrd
2019-01-23 12:33:57 +09:00
c3d284e097
doc: better document relevant PostgreSQL settings
...
There is a brief section in the Quickstart Guide, but it is hard to find
unless you know it is there.
2019-01-23 12:25:02 +09:00
a9e09d436a
doc: use "/current/" in URL path
...
From the next major release, the current documentation will be located in the
"/docs/current/" subdirectory. This makes it easier to provide canonical
links to the latest version of the documentation (similar to how the
main PostgreSQL documentation is organised).
Once the following major release is available, the documentation will be moved
to a subdirectory with the version number, e.g. "/docs/4.3/".
2019-01-23 10:28:48 +09:00
965984a510
doc: update internal documentation links
2019-01-23 10:18:31 +09:00
1980deb480
repmgrd: check for a change to the upstream node
...
If the upstream node has changed, for example after "repmgr standby follow"
was manually executed, restart monitoring to ensure repmgrd is monitoring the
correct node.
2019-01-22 13:33:13 +09:00
b6fe91ebcd
repmgrd: track status of local (standby) node
...
If the local node is not available, note the degraded monitoring status.
2019-01-22 10:36:22 +09:00
44cbb44500
repmgrd: improve logging output for standby monitoring
2019-01-22 10:36:14 +09:00
99161c38d2
Fix typo
2019-01-21 17:37:01 +05:30
57d3ee768c
doc: clarify data directory requirement in quickstart guide
2019-01-21 15:12:33 +09:00
7dce3ed234
Update copyright notices to 2019
2019-01-21 14:54:35 +09:00
58efb0f158
repmgrd: on a cascaded standby, don't fail over if "failover=manual"
...
Addresses GitHub #531 .
2019-01-21 14:16:49 +09:00
d261768541
Standardize on --host option
2019-01-17 10:52:41 +09:00
aa8547a219
Improve "witness register" documentation, help and logging
...
Make it clearer that a) the primary server's hostname is required,
and b) how to provide it.
Based on feedback provided in GitHub #529 .
2019-01-17 10:42:53 +09:00
9f04a846ec
doc: command to unpause should be 'unpause'
...
GitHub #530 .
2019-01-17 10:13:22 +09:00
ff0e480fdd
Ensure functions in dirutil.c do not directly modify the provided path
2019-01-16 17:24:31 +09:00
8881b69c06
"standby switchover": check remote data directory configuration
...
The switchover will fail if the data_directory parameter in repmgr.conf
on the remote node (demotion candidate) is incorrectly configured.
We use the previously added "repmgr node check --data-directory-config
to verify this, and abort early if an issue is discovered.
Implements GitHub #523 .
2019-01-16 16:03:49 +09:00
0b3a310802
Add --data-directory-config option to "repmgr node check"
...
Implements part of GitHub #523 .
2019-01-16 16:03:44 +09:00
4523137bfc
doc: note "pg_read_all_settings" in FAQ
...
Relevant for PostgreSQL 10 and later where the repmgr user is not a superuser.
2019-01-16 11:27:35 +09:00
666f5cf851
doc: add FAQ entry clarifying why "data_directory" is required in repmgr.conf
2019-01-16 09:50:29 +09:00
e89938e132
doc: add missing space after varname
...
GitHub #526
2019-01-16 09:37:58 +09:00
d97905f6fd
doc: fix typos and update version example
2019-01-15 12:56:18 +09:00
bed66edfd9
doc: clarify Debian source install instructions
2019-01-15 12:52:30 +09:00
ba7ef9e643
doc: update PostgreSQL documentation links
...
"/static/" path element no longer required.
2019-01-15 12:45:33 +09:00
10be941298
Fix typo
...
"node join" should be "node rejoin"
2019-01-14 15:39:13 +09:00
75379eab2e
doc: update "repmgr standby follow" documentation
...
Note corner case where repmgr will not be able to check for timeline
divergence.
2019-01-14 13:53:52 +09:00
d4e993a240
Improve handling of connection URIs when executing remote commands
...
Previously, if connection URIs were in use and "repmgr standby switchover"
was executed, repmgr would pass the connection URI as-is to the demotion
candidate to execute "repmgr node rejoin". However the presence of
unescaped ampersands in the connection URI was causing the rejoin command
to be incorrectly executed.
Addresses GitHub #525 .
2019-01-14 11:11:51 +09:00
695a45f9ed
Fix regression test
...
get_new_primary() output has changed.
2019-01-14 10:04:20 +09:00
028c874f81
"standby follow": simplify check when follow target has higher timeline
...
No need for a CHECKPOINT here, which simplifies things considerably.
2019-01-11 16:34:04 +09:00
b3c2831bd3
repmgr: add --dry-run option to "standby promote"
...
Implements GitHub #522 .
2019-01-10 12:36:58 +09:00
Ian Barwick