b8677a0fa2
docs: link to PostgreSQL roadmap
2020-08-06 10:01:40 +09:00
992d2e0e49
doc: update "repmgr witness register" description
...
Add missing "Options" section.
2020-08-06 10:01:37 +09:00
5c71809261
docs: reformat additonal config file upgrade notes into a new section
...
It's easier to link to the information that way.
2020-08-06 10:01:32 +09:00
22f2ee3050
doc: add two notes on section related to configuration files
...
Add notes to the documention mentioning that after postgres or repmgr
upgrades (postgres major upgrades), there are some changes that need
to be taken care of.
Signed-off-by: Martín Marqués <martin.marques@2ndquadrant.com >
2020-08-06 10:01:29 +09:00
b9874cd751
doc: clarify "node rejoin" usage
...
Emphasize that conninfo must be provided for a running node.
2020-07-06 09:57:48 +09:00
3bfaa8e722
doc: note downstream node (dis)connection monitoring in more places
2020-06-09 16:30:53 +09:00
9ce1c2e640
doc: clarify usage of "-f /etc/repmgr.conf" in examples
2020-05-08 10:24:24 +09:00
2b0218456a
doc: clarify usage of the "passfile" parameter.
2020-04-23 15:04:40 +09:00
cb19311b35
doc: have Makefile clean up generated html files
2020-04-20 15:41:29 +09:00
9ce7cb7012
doc: clarify .pgpass usage with -S/--superuser option
2020-04-20 15:41:26 +09:00
687ed68ce2
doc: remove DEBUG output from example
2020-04-20 12:17:48 +09:00
8472d99277
doc: clarify usage of -F/--force with "standby promote"
...
Per GitHub #632 .
2020-04-20 12:17:45 +09:00
1e90d5e018
doc: update link to Debian package archive
...
See also https://www.df7cb.de/blog/2020/apt-archive.postgresql.org.html
2020-04-14 12:34:06 +09:00
d45e64ca9e
doc: fix typo in 5.1.0 release section ID
2020-04-13 10:40:25 +09:00
ce88f3ec43
doc: finalize release notes
2020-04-10 16:40:23 +09:00
5acdd69add
doc: update release notes
2020-04-10 13:39:03 +09:00
599bab590a
Create temporary pg.auto.conf file with the same permissions as the original
...
Commit 0574279
2020-04-07 13:29:59 +09:00
cd80f265ac
standby clone: warn about missing pg_rewind prerequisites
...
These are not essential for cloning a standby, but useful to warn
as early as possible in case the user is intending to use pg_rewind.
2020-04-06 15:37:37 +09:00
59159dede7
Ensure next release is 5.1, not 5.1.0
2020-04-03 14:57:17 +09:00
447054a630
standby promote: in --dry-run mode, display promote command which will be used
...
For PostgreSQL 12 and later, explicitly note whether repmgr user has
execution permissions on the pg_promote() function.
2020-04-02 12:37:32 +09:00
d998cab3d0
doc: add note about granting permissions on pg_promote()
2020-04-02 11:32:02 +09:00
7f460c88bf
doc: update "node check" examples
...
Also add example output for a standby.
2020-03-31 11:09:00 +09:00
bffb8fa11b
node check: handle --upstream option when node is primary
2020-03-31 10:49:30 +09:00
d9cb38c7f0
node check: add --upstream option
...
We have a --downstream option to check for attached nodes, but it
would be useful to have a corresponding --upstream option too.
A following patch will adapt the behaviour of this option when executed
on the primary node.
2020-03-30 17:54:52 +09:00
e64349e4da
standby switchover: accept -S/--superuser option
2020-03-25 14:00:51 +09:00
2b06f2d1ae
node service: enable provision of the -S/--superuser option
...
This is required to be able to execute a CHECKPOINT if the normal
repmgr user is not a superuser.
2020-03-24 17:25:34 +09:00
b09631b3bc
doc: clarify pg_promote() usage
2020-03-24 15:40:26 +09:00
e561ddc8d3
node check: accept -S/--superuser option
...
This is mainly useful for the --data-directory-config option, which
requires permission to read pg_settings to verify that the data
directory configured in "repmgr.conf" matches the data directory
actually in use.
If pg_settings read permission is not available, repmgr will fall
back to a simple check that the data directory configured in
"repmgr.conf" is a valid PostgreSQL directory. This is not entirely
foolproof, as it's possible PostgreSQL could be using a different
data directory.
2020-03-23 17:14:04 +09:00
b691a1bd10
doc: minor fixes to pg_upgrade notes
2020-03-20 17:24:41 +09:00
dd35c22033
doc: add note about pg_upgrade and standbys
2020-03-20 17:22:15 +09:00
ddde31b14e
doc: update section about passwords when cloning standbys
...
Reference new password management section and remove duplicate
info.
2020-03-18 17:24:39 +09:00
09a78111f6
doc: add note about alternative passfile locations
2020-03-18 17:08:54 +09:00
76cea52755
doc: add section about password management
...
This is briefly covered in the section about cloning, but is hard to
find.
2020-03-18 17:08:49 +09:00
57ba3ef19a
doc: clarify database user permission requirements
2020-03-10 14:26:27 +09:00
0ddc9b8bbf
doc: move database permission configuration to separate file
2020-03-10 14:26:23 +09:00
5722c0a582
doc: fix typo
2020-03-06 17:41:19 +09:00
0bc0a28378
standby promote: enable "service_promote_command" in PostgreSQL 12
...
This enables the promote command generated internally by repmgr to
be overridden if desired, in the same way as for PostgreSQL 11 and
earlier.
2020-03-06 13:21:30 +09:00
fb5ce720f3
standby promote: fall back to "pg_ctl promote" if necessary
...
From PostgreSQL 12, the SQL-level function "pg_promote()" can be used
to promote a PostgreSQL instance, however usage is restricted to
superusers and users to whom explicit execution permission for this
function has been granted.
Therefore, if execution permission is not available, fall back to
"pg_ctl promote".
2020-03-06 12:53:37 +09:00
6559258b53
doc: update release notes
2020-03-05 17:24:24 +09:00
10304a1a3b
doc: update release notes
2020-03-04 17:21:31 +09:00
e02e3dae29
doc: update "repmgr cluster show" output example
2020-02-26 16:02:08 +09:00
51a7c31833
doc: update "repmgr cluster show" examples
2020-02-25 12:22:19 +09:00
2bb89d252b
doc: a witness server is also relevant for primary visibility consensus checks
...
Clarify documentation and example to make it clear that a witness
server, if present, is also used for primary visibility consensus
checks.
2020-02-24 15:25:15 +09:00
089b3ecb8b
doc: note PostgreSQL 9.4 EOL
2020-02-14 11:17:06 +09:00
6f01c54620
repmgr: improve "standby switchover" completion checks
...
There were some corner cases where "repmgr standby switchover"
would erroneously report a successful switchover, even if the
demotion candidate had not reattached to the promotion candidate.
Also improve the logging in various places to make it clearer
what is happening on which node.
2020-02-04 15:38:10 +09:00
e2a362a171
"node rejoin": check for available replication slots on the rejoin target
...
"standby follow" did this already, but "node rejoin" didn't.
2020-02-03 17:03:20 +09:00
ab9c84c655
Report error code on follow/rejoin failure due to non-available slot
...
Previously, if "repmgr standby follow" or "repmgr node rejoin" failed
due to a replication slot not being available, no error code was
returned.
2020-02-03 15:03:31 +09:00
0141bc2be7
standby switchover: display "shutdown_check_timeout" value in --dry-run mode
...
It's useful to be aware of this setting.
2020-01-30 10:30:18 +09:00
3ae6691d34
doc: minor clarifications to Debian package info
2020-01-24 10:36:46 +09:00
bd8eb82fb9
doc: update repository links to https
2020-01-24 10:29:40 +09:00
Ian Barwick