192f8ff3c2
doc: add section about password management
...
This is briefly covered in the section about cloning, but is hard to
find.
2020-03-18 17:38:52 +09:00
cc233c90e8
doc: clarify database user permission requirements
2020-03-10 14:27:16 +09:00
d021810ce6
doc: move database permission configuration to separate file
2020-03-10 14:27:11 +09:00
0c8a636293
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:38:12 +09:00
d475ccdec2
doc: note PostgreSQL 9.4 EOL
2020-02-14 17:17:55 +09:00
3145ccbe95
doc: add single quotes to "barman_config" example.
...
Mandatory from repmgr 5.x.
2020-02-14 17:17:32 +09:00
d19ccf74e8
standby switchover: display "shutdown_check_timeout" value in --dry-run mode
...
It's useful to be aware of this setting.
2020-01-30 10:31:20 +09:00
f5bfba4a5a
doc: minor clarifications to Debian package info
2020-01-24 10:46:56 +09:00
e60d00543c
doc: update repository links to https
2020-01-24 10:46:52 +09:00
be79f1e2c9
doc: note availability of RHEL 8 packages
2020-01-07 09:45:24 +09:00
9d2d3296fb
doc: update release notes
2019-12-10 16:48:36 +09:00
656030b851
doc: add reference to "ssh_options"
...
This is listed in "repmgr.conf.sample" but not the main documentation.
2019-11-25 10:17:45 +09:00
b535daed89
doc: link PgBouncer fencing document from main docs
2019-11-21 09:58:01 +09:00
cd0ea1688c
doc: document "tablespace_mapping" parameter.
...
This was previously only mentioned in "repmgr.conf.sample".
2019-11-20 16:54:49 +09:00
98021f1167
doc: fix minor punctuation typo
2019-11-11 15:54:59 +09:00
d963558baf
doc: ensure various repmgr.conf values are quoted appropriately
2019-11-08 11:50:29 +09:00
017387dfd0
doc: clarify Barman configuation
...
Per confusion noted in GitHub #602 .
2019-11-07 14:29:14 +09:00
ff48789ea3
doc: note superuser requirement for "repmgr primary register"
2019-10-25 12:44:49 +09:00
0112843f1b
doc: note permission requirements for "repmgr standby (promote|switchover)
...
Per issues noted in GitHub #595 .
2019-10-25 11:54:50 +09:00
446d7426ba
doc: note which repmgr versions are supported in the compatibility matrix
2019-10-24 09:49:28 +09:00
b4da7caa30
doc: update README
...
Link to compatibility matrix, support section.
2019-10-24 09:49:24 +09:00
6c3b0dff4f
doc: expand section about requesting support
2019-10-18 12:00:47 +09:00
676475dc1f
doc: add link to blog entry about Pg12 replication configuration changes
2019-10-18 12:00:43 +09:00
c27f134e50
doc: split notes about PostgreSQL 9.3 and 9.4 support into a new subsection
2019-10-15 10:46:14 +09:00
5a619244ee
doc: add note about 4.x development policy
2019-10-15 10:42:52 +09:00
b5448def7e
doc: add repmgr 5.0 release date
2019-10-15 10:30:34 +09:00
2304584679
Fix handling of upstream node change check
...
repmgrd has a check to see if the upstream node has unexpectedly
changed, e.g. if the repmgrd service is paused and the PostgreSQL
instance has been pointed to another node.
However this check was relying on the node record on the local node
being up-to-date, which may not be the case immediately after a
failover, when the node is still replaying records updated prior
to the node's own record being updated. In this case it will
mistakenly assume the node is following the original primary
and attempt to restart monitoring, which will fail as the original
primary is no longer available.
To prevent this, we check against the node's record on the upstream
node.
Addresses issue noted in GitHub #587 and #588 .
2019-10-14 12:28:04 +09:00
4aaa24a5f8
Update configuration file conversion script
...
Ensure output is quoted.
2019-10-08 10:59:20 +09:00
7053ed5b51
doc: update links to Barman documentation
2019-10-08 10:30:41 +09:00
a845d7126d
doc: minor updates to "repmgr standby clone" reference
...
- remove references to repmgr 4.0.4 (present because feature
was added in a minor release, but that's a long time ago)
- note configuration is appended to postgresql.auto.conf
2019-10-08 10:21:26 +09:00
1c317059cd
doc: clarify use of --recovery-conf-only
2019-10-08 10:03:44 +09:00
dcf5bfb649
doc: fix minor formatting error
2019-10-08 09:48:04 +09:00
f3c3320a9c
doc: update examples in quickstart guide
2019-10-07 18:27:38 +09:00
cfc5bde219
doc: update repmgr.conf samples in Barman section
...
From repmgr 5.x we really need to quote all the things.
2019-10-07 12:05:26 +09:00
ea57269569
doc: improve instructions for cloning from Barman
2019-10-07 11:56:40 +09:00
e8b5b92893
doc: improve Barman standby clone example
2019-10-03 15:52:32 +09:00
02bdcf657f
doc: add link to FAQ section about 3rd party package compatibilty
2019-10-03 15:23:57 +09:00
405f70f769
doc: clarify barman-cli package usage
...
As of Barman 2.8, the barman-cli package has been merged with the core
Barman code, so is only requires an explicit mention for Barman 2.0 ~ 2.7.
2019-10-03 14:35:45 +09:00
577ca35de5
doc: remove reference to Barman 1.x.
...
Barman 1.x is very outdated and should no longer be used anyway.
2019-10-03 14:25:17 +09:00
a557f2d69e
Typo in the documentation of the repmgrd configuration
...
Signed-off-by: Martín Marqués <martin.marques@2ndquadrant.com >
2019-10-01 09:44:30 -03:00
1196821457
doc: update FAQ
...
Note pg_monitor default role as well, and link to relevant section
in the PostgreSQL documentation.
2019-10-01 10:29:44 +09:00
c1d464f3da
doc: add FAQ entry about 3rd-party PostgreSQL packages
2019-10-01 10:07:25 +09:00
4646bbc289
doc: standardize doc formatting
...
Indent with two spaces instead of one.
2019-10-01 09:44:04 +09:00
bb9a0c2297
doc: update FAQ
...
Add note about repmgr 5 in the "What's the difference between the repmgr
versions?" item.
2019-10-01 09:41:49 +09:00
50d4cee877
doc: link to GitHub release page
2019-09-24 11:37:25 +09:00
db99e98236
doc: note flex required for source builds
...
From 5.0 onwards.
2019-09-24 11:34:24 +09:00
10f00b8822
repmgr: pass explicitly provided log level when executing repmgr remotely
...
This makes it possible to return log output when executing repmgr
remotely at a different level to the one defined in the remote
repmgr's repmgr.conf.
This is particularly useful when DEBUG output is required.
2019-09-17 15:38:43 +09:00
98e96f4375
doc: clarify configuration file changes
2019-09-17 13:01:03 +09:00
8489fd061f
doc: update release notes
2019-09-17 11:19:05 +09:00
56aae22b6c
doc: update release notes
2019-09-17 11:00:04 +09:00
Ian Barwick