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
b885337abc
Minor code formatting fix
2019-10-07 10:48:35 +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
1ed8b1067a
Prevent use of backend string functions
...
From PostgreSQL 12, port.h forcibly redefines printf() et al to use
the versions defined by PostgreSQL (pg_printf() et al). As this
causes linking issues in build environments which build pre-Pg12
versions against Pg12's libpq, ensure relevant macros defined
in port.h are undefined.
2019-09-26 12:47:51 +09:00
a502b2cf96
Move function parse_repmgr_version() to a more appropriate location
2019-09-24 13:14:03 +09:00
8e6d111f32
Refactor remote_command() function
...
Use dynamic rather than fixed buffer to generate the command string.
2019-09-24 13:14:03 +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
bce039f336
doc: add clarifications to "Standby disconnection on failover"
2019-09-05 18:00:56 +09:00
19190153a0
doc: clarify prerequisites for executing the "repmgr service" commands
...
Note node accessibility requirements on each command's reference
page.
2019-08-30 12:07:37 +09:00
b1c6418e8d
doc: expand "see also" links for "repmgr (service|daemon)" commands
2019-08-30 11:51:32 +09:00
12491c6aa1
doc: add note about starting/stopping repmgrd on individual nodes
2019-08-30 11:51:11 +09:00
d5b806eeff
Fix pg_control handling for PostgreSQL 12
...
"FullTransactionId" is not present in earlier versions, so we'll
have to #ifdef that out for those.
We should probably add more elegant checks to ensure that repmgr
is being executed against the PostgreSQL version it was built against.
In a normal production environment that will be the case as the
matching package will have been installed, so version mismatches
don't usually occur.
Note that while currently most aspects of the repmgr client are
compatible across PostgreSQL versions, the repmgrd code is very
version specific, so version specificity is a given anyway.
2019-08-29 17:22:01 +09:00
37bfe6ee4f
Have "make clean" remove "repmgr_version.h"
2019-08-29 17:17:33 +09:00
97c21ed907
doc: update package examples
...
Use recent version numbers where appropriate.
2019-08-29 15:57:49 +09:00
3ea47522cd
doc: clarify "repmgr daemon (start|stop)" purpose
2019-08-28 16:28:29 +09:00
935be3d669
doc: update example PostgreSQL version references to Pg12
2019-08-28 15:52:14 +09:00
494444869d
doc: updates for repmgr 5.x and PostgreSQL 12
2019-08-28 15:33:01 +09:00
677a94513e
repmgr: note that --dry-run is not effective with "repmgr service status"
2019-08-28 15:14:35 +09:00
931da14df1
Rename some "repmgr daemon ..." commands to "repmgr service ..."
...
"repmgr daemon" can be interpreted to mean the commands affect the local
daemon process only. Rename the commands which affect the entire cluster
to "repmgr service ...".
The "repmgr daemon ..." form of the affected commands is retained for backwards
compatibility.
2019-08-28 14:58:11 +09:00
3e812f6e91
repmgrd: always emit NOTICE when attempting to follow a new primary
...
Previously, if a standby's repmgrd was looping in degraded monitoring
mode looking for a new primary to follow, once a new primary was
detected the follow command would be executed without any prior
logging at non-DEBUG log levels.
2019-08-26 16:02:41 +09:00
ffc7b7817b
doc: update HISTORY
...
Note PostgreSQL support.
2019-08-22 15:42:29 +09:00
fb6352735a
The next major release will be 5.0.
...
4.5 was a placeholder release number in case a major release was required
prior to the release of Pg12.
2019-08-22 15:15:56 +09:00
f122c44a77
Fix debugging output
2019-08-21 15:52:08 +09:00
b4e6922a26
doc: add further note about configuration file changes
2019-08-20 16:36:58 +09:00
6e200d32a4
doc: add note about max_wal_senders in Pg12 and later
2019-08-20 11:17:36 +09:00
507b27c05d
Mark set_repmgrd_pid() as "RETURNS NULL ON NULL INPUT"
...
When unsetting the PID, we'll want to set the pidfile to NULL rather
than an empty string.
2019-08-19 20:15:30 +09:00
28f4536372
repmgrd: fix pidfile handling at shutdown
2019-08-19 17:55:18 +09:00
2ec761a979
doc: update "repmgr standby clone" reference for PostgreSQL 12
...
Mainly replace "recovery.conf" with the more generic "replication
configuration".
2019-08-19 10:40:42 +09:00
b5225a2662
Support --create-recovery-conf in Pg12
2019-08-19 10:40:38 +09:00
d5ed38f573
Make "standby follow" work in Pg12
2019-08-19 10:40:35 +09:00
2a37e28304
write standby.signal
2019-08-19 10:40:31 +09:00
9eb6ce52b4
Write replication configuration for Pg12 and later
2019-08-19 10:40:27 +09:00
9e072c6773
Update code comment with list of options for "standby clone"
2019-08-15 18:11:47 +09:00
72daa38baa
durable_rename() only available externally from Pg10
2019-08-14 20:28:05 +09:00
f5044465cb
Add function to safely modify postgresql.auto.conf
...
This is required for PostgreSQL 12 and later.
2019-08-14 16:57:42 +09:00
Ian Barwick