edf3aa6687
doc: restore original stylesheet for now
2019-05-09 16:24:41 +09:00
255623004c
doc: update link to PostgreSQL documentation
2019-05-09 16:24:37 +09:00
04a6bf86f2
doc: update documentation build instructions
2019-05-09 16:24:30 +09:00
3804c95019
doc: (re)add single page HTML generation
2019-05-09 16:24:26 +09:00
409eb47e2a
doc: convert documentation to DocBook XML
...
This brings the repmgr documentation build system in line with that
used by the main PostgreSQL project, and removed the restriction
that documentation must be built against PostgreSQL 9.6 or earlier.
Main formatting changes are:
- convert empty-element tags (mainly <xref/>)
- put <indexterm> sections in the correct location
- correct usage of various entities.
2019-05-09 16:24:21 +09:00
1a6f7e979d
doc: update release notes
2019-05-07 17:23:03 +09:00
6f8fa45604
doc: update release notes
2019-05-07 15:49:54 +09:00
5e03627e6c
doc: update release notes
2019-05-07 15:29:56 +09:00
1c13e57c8b
doc: update release notes
2019-05-07 15:27:13 +09:00
02245a0014
repmgrd: add missing PQfinish() calls
2019-05-02 18:50:21 +09:00
4b37562444
Make it clearer that a witness node counts as a "sibling node"
...
It's not attached to the primary per-se, but needs to know what
the current primary is in order to correctly synchronise its
copy of the metadata.
Per GitHub #560 .
2019-05-02 14:22:53 +09:00
8da355eb3f
doc: update release notes
2019-05-02 14:00:07 +09:00
b8fa71257a
doc: update "repmgr standby promote" documentation
...
Document new "--siblings-follow" option.
2019-05-02 12:06:08 +09:00
fed09ecaae
standby promote: have former siblings follow new primary
2019-05-02 12:04:49 +09:00
98d09f83b5
standby (promote|switchover): improve --dry-run functionality
...
Continue checks as far as possible.
2019-05-02 12:04:43 +09:00
7bbe938e19
Separate promotion candidate walsender/slot checks into discrete functions
...
For use by "standby promote" as well as "standby follow"
2019-05-02 12:04:40 +09:00
63c7f758c3
Remove unneeded server version number variables
...
No need to pass these around.
2019-05-02 12:04:33 +09:00
b9f07f6a91
standby promote: use variable name "local_conn" for the local connection handle
...
This is consistent with usage in other functions, and makes it easier to
differentiate between the local node connection and the primary connection.
2019-05-02 12:04:26 +09:00
e4615b4666
Refactor code for executing --siblings-follow
...
This will enable provision of "--siblings-follow" to "repmgr standby promote"
2019-05-02 12:04:15 +09:00
dbeffbf29a
doc: define entity for repmgrd
2019-05-01 10:36:54 +09:00
4d1e11533e
doc: add missing space in example output
2019-05-01 10:14:18 +09:00
52905f1eb3
Standardize on "ID: %i" when logging node IDs
...
Previously there was a mix of "id:", "node id:", "node ID:" and "node_id:".
2019-04-30 17:07:33 +09:00
6c3b4c0db8
Remove unused line
2019-04-30 15:53:24 +09:00
89a7261483
Always quote node names in log messages
2019-04-30 15:52:56 +09:00
d7de0a64e0
doc: bit too many e.g.'s
...
PR #565 .
2019-04-30 10:47:45 +09:00
531c4d9853
doc: promote -> follow
...
PR #565
2019-04-30 10:43:15 +09:00
356fe2e640
Fix "repmgr daemon status --csv" output
2019-04-29 20:52:27 +09:00
e32acda8c0
standby switchover: ignore nodes which are unreachable and marked as inactive
...
Previously "repmgr standby switchover" would abort if any node was unreachable,
as that means it was unable to check if repmgrd is running.
However if the node has been marked as inactive in the repmgr metadata, it's
reasonable to assume the node is no longer part of the replication cluster
and does not need to be checked.
2019-04-29 14:35:49 +09:00
5f10e68f31
emit warning if "--siblings-follow" provided out-of-context
2019-04-29 14:12:22 +09:00
87910a5448
repmgrd: improve logging of sibling node's upstream info
...
If the sibling node has already been promoted (for whatever
reason, e.g. "repmgr standby promote" was executed manually)
and has exited recovery, the upstream node ID will normally
be reported as "-1", which is correct, but looks confusing in
the logs.
We now only report the upstream node ID if the sibling node
is still in recovery, *or* if it has exited recovery but is
still reporting an extant node ID.
2019-04-29 13:51:17 +09:00
ec6266e375
doc: list caveats when monitoring child node disconnection
2019-04-25 17:52:14 +09:00
2082a8d3f3
Consolidate some code
2019-04-25 16:04:40 +09:00
c8d52bab6d
cluster show: fix thinko introduced in commit 9fe2fa2
2019-04-25 15:46:07 +09:00
dbbf35ded1
Update HISTORY
2019-04-25 14:59:33 +09:00
9fe2fa2daf
daemon status: make output more like that of "cluster show"
...
In particular make any issues with unexpected server state more
obvious.
2019-04-25 14:45:41 +09:00
da24896fd5
doc: add child node monitoring example
2019-04-24 16:04:47 +09:00
c092ce60a7
doc: document "child_node..." configuration parameters
2019-04-24 14:48:38 +09:00
090493ebc9
doc: document "child_node" events
2019-04-24 13:19:00 +09:00
8d80267ab1
doc: update "repmgr primary register" output
2019-04-24 13:18:31 +09:00
3231b5034d
Remove temporary debugging log output
2019-04-24 13:17:52 +09:00
5a9175c740
Clarify hints about updating the repmgr extension
2019-04-24 11:37:31 +09:00
58b33fb411
Clarify a couple of code comments
2019-04-24 10:55:53 +09:00
3129da221e
"primary register": ensure --force works if another primary is registered but not running
2019-04-23 16:54:07 +09:00
6cbf436bf8
Don't execute "child_nodes_disconnect_command" when repmgrd paused
2019-04-23 14:08:13 +09:00
5a90513878
repmgrd: monitor standbys attached to primary
...
This functionality enables repmgrd (when running on the primary) to
monitor connected child nodes. It will log connections and disconnections
and generate events.
Additionally, repmgrd can execute a custom script if the number of connected
child nodes falls below a configurable threshold. This script can be used
e.g. to "fence" the primary following a failover situation where a new primary
has been promoted and all standbys are now child nodes of that primary.
2019-04-22 16:18:52 +09:00
64c4cb81d5
Update pg_control processing for PostgreSQL 12
2019-04-18 09:31:33 +09:00
3115face28
doc: add note about when a PostgreSQL restart is required
...
Per query in GitHub #564 .
2019-04-17 09:43:35 +09:00
80f66e87c9
Improve string handling during configuration file reload
2019-04-16 11:20:41 +09:00
ad28cf95bd
standby register: add upstream node ID in event details
2019-04-16 11:01:22 +09:00
a0c6cb602f
repmgrd: remove duplicate function definition
2019-04-16 10:53:05 +09:00
Ian Barwick