82515a9733
doc: document new parameters for "failover_validation_command"
2020-09-17 15:48:18 +09:00
f1bdb09512
doc: note existing pg_rewind corner-case bug
2020-09-15 14:21:14 +09:00
028e3ab48d
doc: rearrange "repmgr node rejoin" reference for clarity
...
The <important> section looked like an actual subsection, so convert
that and the following example section into <refsect2> sections.
2020-09-15 13:42:18 +09:00
b5b7d635ad
doc: fix "release-current" tag
2020-09-04 15:12:33 +09:00
3945314e65
Remove PostgreSQL 9.3 support
...
PostgreSQL 9.3 community support ended in November 2018.
2020-09-04 11:37:12 +09:00
9a836b3c04
Add option --verify-backup
...
This causes pg_verifybackup to be executed immediately after
pg_basebackup completes.
PostreSQL 13 and later.
2020-09-03 10:40:32 +09:00
1131e3aad2
PostgreSQL 13: support "wal_keep_size"
...
Renamed from "wal_keep_segments" in core commit f5dff459.
2020-08-31 17:18:41 +09:00
c50a2d049c
doc: note use of wildcards in .pgpass file
2020-08-19 10:32:34 +09:00
20100f5aaa
docs: link to PostgreSQL roadmap
2020-08-06 09:50:23 +09:00
2d20c110bf
doc: update "repmgr witness register" description
...
Add missing "Options" section.
2020-08-06 09:50:19 +09:00
aed0045c3a
docs: reformat additonal config file upgrade notes into a new section
...
It's easier to link to the information that way.
2020-08-06 09:50:16 +09:00
cd81046c26
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 09:50:11 +09:00
4d88f177a7
doc: clarify "node rejoin" usage
...
Emphasize that conninfo must be provided for a running node.
2020-07-06 09:55:06 +09:00
547bbb06d8
doc: note downstream node (dis)connection monitoring in more places
2020-06-09 16:21:36 +09:00
f05978e2e1
doc: update example log output to match current code
2020-05-15 10:33:47 +09:00
72dfe28e81
doc: clarify usage of "-f /etc/repmgr.conf" in examples
2020-05-08 10:22:52 +09:00
6507a374f7
doc: update legacy upgrade procedure
...
From PostgreSQL 13, the "CREATE EXTENSION ... FROM" syntax is no longer
available. It's unlikely at this point that someone will find themselves
with a PostgreSQL 13 database and the legacy repmgr schema, but we'll
cover all bases just in case.
2020-05-01 10:27:33 +09:00
3200c8c4e4
doc: clarify usage of the "passfile" parameter.
2020-04-23 15:03:40 +09:00
f8b214f721
doc: have Makefile clean up generated html files
2020-04-20 15:40:13 +09:00
96acd3f915
doc: clarify .pgpass usage with -S/--superuser option
2020-04-20 15:34:29 +09:00
c1584d587c
doc: remove DEBUG output from example
2020-04-20 12:14:47 +09:00
2f26a02b5c
doc: clarify usage of -F/--force with "standby promote"
...
Per GitHub #632 .
2020-04-20 12:11:49 +09:00
e1953742a1
doc: note additional diagnostic options provided by "node check"
2020-04-17 11:53:56 +09:00
9df1731fb8
doc: update release notes
2020-04-15 14:50:51 +09:00
3d85d8f5ff
doc: update link to Debian package archive
...
See also https://www.df7cb.de/blog/2020/apt-archive.postgresql.org.html
2020-04-14 12:32:59 +09:00
4f0e8a503a
doc: fix typo in 5.1.0 release section ID
2020-04-13 17:17:06 +09:00
c39289d570
doc: finalize release notes
2020-04-13 17:17:01 +09:00
662b603770
doc: update release notes
2020-04-13 17:16:55 +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
Ian Barwick