Ian Barwick
599bab590a
Create temporary pg.auto.conf file with the same permissions as the original
...
Commit 0574279 set the file permissions to 0600 rather than the user's
umask, but if initdb was executed with -g/--allow-group-access, the
file is maintained with 0640, so we'll just maintain the existing
permssions.
2020-04-07 13:29:59 +09:00
Ian Barwick
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
Ian Barwick
59159dede7
Ensure next release is 5.1, not 5.1.0
2020-04-03 14:57:17 +09:00
Ian Barwick
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
Ian Barwick
d998cab3d0
doc: add note about granting permissions on pg_promote()
2020-04-02 11:32:02 +09:00
Ian Barwick
7f460c88bf
doc: update "node check" examples
...
Also add example output for a standby.
2020-03-31 11:09:00 +09:00
Ian Barwick
bffb8fa11b
node check: handle --upstream option when node is primary
2020-03-31 10:49:30 +09:00
Ian Barwick
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
Ian Barwick
e64349e4da
standby switchover: accept -S/--superuser option
2020-03-25 14:00:51 +09:00
Ian Barwick
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
Ian Barwick
b09631b3bc
doc: clarify pg_promote() usage
2020-03-24 15:40:26 +09:00
Ian Barwick
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
Ian Barwick
b691a1bd10
doc: minor fixes to pg_upgrade notes
2020-03-20 17:24:41 +09:00
Ian Barwick
dd35c22033
doc: add note about pg_upgrade and standbys
2020-03-20 17:22:15 +09:00
Ian Barwick
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
Ian Barwick
09a78111f6
doc: add note about alternative passfile locations
2020-03-18 17:08:54 +09:00
Ian Barwick
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
Ian Barwick
57ba3ef19a
doc: clarify database user permission requirements
2020-03-10 14:26:27 +09:00
Ian Barwick
0ddc9b8bbf
doc: move database permission configuration to separate file
2020-03-10 14:26:23 +09:00
Ian Barwick
5722c0a582
doc: fix typo
2020-03-06 17:41:19 +09:00
Ian Barwick
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
Ian Barwick
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
Ian Barwick
6559258b53
doc: update release notes
2020-03-05 17:24:24 +09:00
Ian Barwick
10304a1a3b
doc: update release notes
2020-03-04 17:21:31 +09:00
Ian Barwick
e02e3dae29
doc: update "repmgr cluster show" output example
2020-02-26 16:02:08 +09:00
Ian Barwick
51a7c31833
doc: update "repmgr cluster show" examples
2020-02-25 12:22:19 +09:00
Ian Barwick
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
Ian Barwick
089b3ecb8b
doc: note PostgreSQL 9.4 EOL
2020-02-14 11:17:06 +09:00
Ian Barwick
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
Ian Barwick
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
Ian Barwick
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
Ian Barwick
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
Ian Barwick
3ae6691d34
doc: minor clarifications to Debian package info
2020-01-24 10:36:46 +09:00
Ian Barwick
bd8eb82fb9
doc: update repository links to https
2020-01-24 10:29:40 +09:00
Ian Barwick
4d4ed3bcd6
Remove BDR 2.x support
...
The BDR 2.x support was conceptual only and was never used in
production. As BDR 2.x will be EOL'd shortly, there is no risk it will
be needed.
2020-01-16 09:52:42 +09:00
Ian Barwick
7fdf2f1778
Update copyright notices to 2020
2020-01-13 14:06:20 +09:00
Ian Barwick
46222cc0ae
doc: note availability of RHEL 8 packages
2020-01-07 09:44:47 +09:00
Ian Barwick
ab6e5ceab3
doc: add reference to "ssh_options"
...
This is listed in "repmgr.conf.sample" but not the main documentation.
2019-11-25 10:17:31 +09:00
Ian Barwick
eb1d5c4e93
doc: link PgBouncer fencing document from main docs
2019-11-21 09:53:53 +09:00
Ian Barwick
b3c09c48bf
doc: document "tablespace_mapping" parameter.
...
This was previously only mentioned in "repmgr.conf.sample".
2019-11-20 16:52:35 +09:00
Ian Barwick
21475b9c70
doc: update pgbouncer fencing example
...
Add "--log-to-file" to "repmgr standby promote", per recommended practice.
2019-11-19 21:57:17 +09:00
Ian Barwick
95ee576052
doc: fix minor punctuation typo
2019-11-11 15:52:15 +09:00
Ian Barwick
ac753c2ba1
doc: ensure various repmgr.conf values are quoted appropriately
2019-11-08 11:54:31 +09:00
Ian Barwick
c3aba173ea
doc: clarify Barman configuation
...
Per confusion noted in GitHub #602 .
2019-11-07 14:26:57 +09:00
Ian Barwick
93acdcfda2
doc: add single quotes to "barman_config" example.
...
Mandatory from repmgr 5.x.
2019-11-07 14:23:04 +09:00
Ian Barwick
c23162e787
doc: note superuser requirement for "repmgr primary register"
2019-10-25 12:43:39 +09:00
Ian Barwick
63217e436a
doc: note permission requirements for "repmgr standby (promote|switchover)
...
Per issues noted in GitHub #595 .
2019-10-25 12:43:39 +09:00
Ian Barwick
5405ae7100
doc: note which repmgr versions are supported in the compatibility matrix
2019-10-24 09:46:28 +09:00
Ian Barwick
b007d5ed4b
doc: update README
...
Link to compatibility matrix, support section.
2019-10-24 09:42:23 +09:00
Ian Barwick
b74f965f54
standby clone: rename --recovery-conf-only to --replication-conf-only
...
A more generic option name to cover pre- and post-Pg12 replication
configuration methods.
--recovery-conf-only is retained as an alias for backwards
compatibility.
2019-10-18 14:44:57 +09:00