Ian Barwick
34dbf64f50
Ensure an inactive PostgreSQL data directory can be deleted.
...
Addresses GitHub #366 .
2018-02-02 17:12:25 +09:00
Ian Barwick
ea653a8dbc
"standby follow": finalize implementation of --dry-run option
2018-02-02 15:42:08 +09:00
Ian Barwick
50894b6124
"standby follow": check for replication slot availability on target node
2018-02-02 15:01:23 +09:00
Ian Barwick
94e187c476
Improve "repmgr primary unregister" documentation and --help output
...
Per observations in GitHub #373
2018-02-02 14:12:15 +09:00
Ian Barwick
de6284ae79
doc: note password SSH requirements for "standby switchover"
2018-02-02 14:01:58 +09:00
Ian Barwick
c54045bcd8
"standby follow": initial implementation of --dry-run option
...
GitHub #363 .
2018-02-01 14:18:40 +09:00
Ian Barwick
c0a53471e1
"standby switchover": improve log messages and add new exit code
...
Previously, if an issue was encountered with the old primary, but user
provided -F/--force to have repmgr promote the standby anyway, repmgr
would exit with the log message "STANDBY SWITCHOVER is complete"
and exit code 0 (SUCCESS).
To better report this partial completion, repmgr will now emit the message
"STANDBY SWITCHOVER has completed with issues" (and a HINT to check preceding
log messages) and new exit code 22 (ERR_SWITCHOVER_INCOMPLETE).
2018-01-31 10:25:15 +09:00
Ian Barwick
2eec8b5d79
Have do_standby_follow_internal() not abort on error
...
Pass the error code back to the caller instead, mainly so
"repmgr node rejoin" can better report errors.
2018-01-30 16:53:04 +09:00
Ian Barwick
c11e92cf2a
repmgr: improve switchover handling when "pg_ctl" used
...
If logging output not explicitly rediretced with "-l" in the pg_ctl
options, repmgr would hang waiting for pg_ctl output.
Note that we recommend using the OS-level service commands where
available.
2018-01-30 13:43:37 +09:00
Ian Barwick
f294d09034
"repmgr standby register": improve error output when standby not running
...
Add explicit HINT
2018-01-26 22:13:11 +09:00
Ian Barwick
26c597ef5a
doc: expand upgrade documentation
...
Include section about using pg_upgrade
2018-01-23 10:57:19 +09:00
Vlad
b8efbb7a15
doc: add missing word in overview
...
GitHub pull request #362
2018-01-19 09:11:54 +09:00
Ian Barwick
3044696c05
doc: update 4.0.2 release notes
...
Add details about upgrading.
2018-01-19 09:09:59 +09:00
Ian Barwick
6dc1969ad5
Remove --bdr-only configuration option
...
This was required for a specific use case during pre-release
development and is no longer needed now the physical streaming
replication handling is implemented.
2018-01-18 13:30:47 +09:00
Ian Barwick
cb41ef1733
doc: update list of event notifications
2018-01-18 11:48:10 +09:00
Ian Barwick
d10f1f289e
Bump version in configure.in
...
4.0.2
v4.0.2
2018-01-16 13:55:58 +09:00
Ian Barwick
5731ba6043
Update version and release date
2018-01-16 12:58:11 +09:00
Ian Barwick
3d6437c8f8
repmgr: assume node is actually shutting down if pingable and that's the reported status
2018-01-16 11:17:06 +09:00
Ian Barwick
54b5c8ad94
repmgrd: log execution error in "repmgrd_get_local_node_id()"
...
That shouldn't happen, but if it does it will make it easier to
identify the issue.
2018-01-16 11:14:04 +09:00
Ian Barwick
0eca08ffaf
doc: improve switchover documentation
...
Emphasize need to set the "service_*_command" options when repmgr is
installed from a package.
2018-01-16 11:06:39 +09:00
Ian Barwick
05c1dc2b92
doc: add 4.0.2 release notes
2018-01-11 16:39:58 +09:00
Ian Barwick
2bd300073d
doc: minor readbility fix
2018-01-11 15:49:56 +09:00
Ian Barwick
01e020df8e
doc: note change of shared library name from "repmgr_funcs" to "repmgr"
2018-01-11 15:47:35 +09:00
Ian Barwick
ae7963dc64
repmgr: automatically create slot name if missing
...
It's possible that a node was registered with "use_replication_slots=false"
but that was later changed to "use_replication_slots=true". If the node
was not subsequently re-registered, the node record will contain an empty
slot name, which will cause any slot creation operation during
"standby follow" or "node rejoin" to fail.
To prevent this happening, check for an empty slot name and automatically
set before proceeding.
Addresses GitHub #343 .
2018-01-11 11:13:41 +09:00
Ian Barwick
faffb2a6e7
repmgr: catch possible corner case when checking node shutdown status
...
It's conceivable that PQping is returning "no response" but the
shutdown hasn't quite completed.
2018-01-10 14:56:00 +09:00
Ian Barwick
5d57044118
repmgr: during switchover, correctly detect unclean shutdown status
2018-01-10 12:21:04 +09:00
Ian Barwick
07a88c78a5
repmgr standby switchover: add "%p" event notification parameter
...
This will contain the node ID of the former primary.
2018-01-10 11:01:00 +09:00
Ian Barwick
f7df8b9c80
doc: document command line options for "standby switchover"
2018-01-10 10:19:36 +09:00
Ian Barwick
20920b3da1
repmgr standby switchover: add event details
2018-01-10 09:55:24 +09:00
Ian Barwick
683f4de182
Bump version
...
4.0.2
2018-01-09 13:43:58 +09:00
Ian Barwick
0c62821ffb
Consolidate parsing of output from executing repmgr on a remote server
...
This should also fix the issue reported in GitHub #349 .
2018-01-09 13:33:38 +09:00
Ian Barwick
6b70e8bbe6
doc: list repmgr.conf parameters relevant during switchover
2018-01-08 11:13:39 +09:00
Ian Barwick
6b223698c9
Fix call to is_active_bdr_node() in BDR repmgrd
...
Following the fix to "is_active_bdr_node()" in 841f03ae , it turns out
the call in repmgrd-bdr.c was only accidentally working; explicitly
test for a false return value.
2018-01-04 21:06:45 +09:00
Ian Barwick
aee12dc2c7
"repmgr bdr register": create missing connection replication set if needed
...
Previously the assumption was that the "repmgr" replication set would be
set up when the nodes are created, however no checks were implemented
and this was not well-documented.
Addresses GitHub #347 .
2018-01-04 17:12:52 +09:00
Ian Barwick
c5c86e1ada
"repmgr bdr register": improve node name check
...
We'll use "bdr.bdr_get_local_node_name()" to check the local BDR node
name and the repmgr one match.
2018-01-04 16:07:06 +09:00
Ian Barwick
7476dc84f2
doc: link event notification page from relevate command reference pages
2018-01-04 14:54:14 +09:00
Ian Barwick
f6d63f5216
doc: update package documentation
2018-01-04 13:11:44 +09:00
Ian Barwick
a608b0bc18
"repmgr standby register": add --wait-start option
...
Implements GitHub #356 .
2018-01-04 12:48:12 +09:00
Ian Barwick
469ebba656
doc: fix typos in "repmgr primary unregister" command reference
2018-01-04 12:31:29 +09:00
Ian Barwick
647c21ad0e
doc: add link to event notifications page from "repmgr cluster event"
2018-01-04 10:57:54 +09:00
Ian Barwick
3d2530d6f9
Fix query in is_active_bdr_node()
...
Boolean column was not being checked correctly.
Also add detail output in "repmgr node role --check", where the function
is called.
2018-01-04 10:48:31 +09:00
Ian Barwick
b26e400199
"repmgr cluster event": move query to dbutils.c
2018-01-04 10:06:54 +09:00
Ian Barwick
152e9545a4
docs: document "repmgr cluster event --terse"
2018-01-04 09:53:54 +09:00
Ian Barwick
83b8f05221
"repmgr cluster events": optionally omit "Details" column with --terse
...
Implements GitHub #360 .
2018-01-04 09:48:00 +09:00
Ian Barwick
486f8e5a2c
repmgrd: document standby_[failure|recovery] event notifications
...
Also clean up the relevant code section.
Addresses GitHub #359 .
2018-01-04 09:34:49 +09:00
Ian Barwick
e517cc74d1
repmgr node rejoin: handle missing node record correctly
...
If a connection was provided for a database other than the "repmgr"
database, error was logged but execution continued, resulting in
the connection being finished twice.
Addresses GitHub #358 .
2018-01-03 15:20:10 +09:00
Ian Barwick
26285b470f
doc: add appendix with details about packages
...
work-in-progress
2018-01-02 17:24:51 +09:00
Ian Barwick
1521657965
Update copyright notices to 2018
2018-01-02 10:20:09 +09:00
Ian Barwick
041604e303
doc: Fix event notification placeholder typo
...
Per report from Carlos.
2018-01-01 10:29:34 +09:00
Ian Barwick
0be0100a7c
docs: update HISTORY
2017-12-27 10:24:56 +09:00