Ian Barwick
ba13172b3a
Add initial "repmgr daemon (start|stop)" documentation
2019-01-29 13:01:19 +09:00
Ian Barwick
ba7ef9e643
doc: update PostgreSQL documentation links
...
"/static/" path element no longer required.
2019-01-15 12:45:33 +09:00
Ian Barwick
a2d38c6084
doc: clarify "repmgr standby clone --recovery-conf-only" option
...
Make it clearer that the standby needs to have been cloned by whatever
method before running the command.
2018-11-20 10:19:53 +09:00
Ian Barwick
b5f640d04d
doc: improve event notification documentation
...
- add undocumented events (per report from Daymel Bonne)
- split up list into sections for better overview
- where feasible, add cross-links
2018-08-30 12:39:58 +09:00
Ian Barwick
c3949b2aea
"standby clone" - don't copy external config files in dry run mode
...
Avoid copying files during a --dry-run as it may introduce unexpected changes
on the target node. During an actual clone operation, any problems with
copying files will be detected early and the operation aborted before
the actual database cloning commences.
GitHub #491 .
2018-08-20 15:23:37 +09:00
Martín Marqués
81de200561
Add information to the --help and docs of standby clone regarding the need
...
to provide a conninfo line to the upstream from which we will be cloning
from.
2018-07-16 18:56:41 -03:00
Ian Barwick
a50ac039da
doc: fix typo
2018-06-07 15:04:06 +09:00
Ian Barwick
7613b1769c
standby clone: --recovery-conf-only expects the standby to be registered
...
Note this in the documentation, and add a HINT about registering it
if the standby record is not available.
Related to GitHub #438 .
2018-05-31 09:42:53 +09:00
Ian Barwick
99ad57f88a
doc: mention --recovery-conf-only introduced in repmgr 4.0.4
...
Per GitHub #419 .
2018-04-12 16:11:12 +09:00
Ian Barwick
ad0671ead2
doc: various updates related to "standby clone" operations.
2018-04-12 16:11:07 +09:00
Ian Barwick
dfdebd6c08
Enable provision of "archive_cleanup_command" in recovery.conf
...
If "archive_cleanup_command" is defined in "repmgr.conf", a corresponding
entry will be made in the node's "recovery.conf" file after cloning a
standby.
Note that we recommend using PgBarman to manage WAL archives, but are
providing this facility to help repmgr to be integrated in existing environments.
Implements GitHub #416 .
2018-04-03 14:10:21 +09:00
Ian Barwick
9981ede1af
"standby clone": fix --superuser handling
...
get_superuser_connection() was erroneously using the local node record
to connect to as a superuser, which works when registering the primary
but obviously not when cloning a standby.
Addresses GitHub #380 .
2018-03-02 16:43:19 +09:00
Ian Barwick
383a17fba1
doc: add <options> section for various commands
2018-02-26 16:54:27 +09:00
Ian Barwick
15625183c1
"standby clone": document --recovery-conf-only option
2018-02-23 11:19:21 +09:00
Ian Barwick
625d032435
doc: link event notification page from relevate command reference pages
2018-01-04 14:56:15 +09:00
Ian Barwick
f78c169c3d
docs: improve event notification documentation
2017-11-29 14:43:28 +09:00
Ian Barwick
2341da7a06
docs: convert command reference sections to <refentry> format
...
Note that most entries still need a bit more tidying up, consistent structuring,
provision of more examples etc.
2017-10-31 11:27:13 +09:00
Ian Barwick
71430a9f65
Various documentation fixes
2017-10-17 11:00:37 +09:00
Ian Barwick
d156de533d
Split up command reference
2017-10-05 11:48:21 +09:00
