39b3b32814
repmgr: improve detection of pg_rewind on remote server
...
If `pg_bindir` is not explicitly provided, the remote `ls` command
will be `ls pg_rewind`, which will very likely not find pg_rewind.
In this case execute `which pg_rewind` to confirm it's in the default
path.
Addresses GitHub #267 .
2017-05-05 09:22:03 +09:00
846e0f73b2
repmgr: avoid spurious cluster name errors during 'standby switchover'
...
'standby restore-config' doesn't require a configuration file, but
pass it anyway.
Addresses GitHub #269
2017-05-05 09:21:56 +09:00
7467525c8d
Add log_detail() method
2017-05-05 09:21:51 +09:00
b27a94ccbe
Typo in failover docs, reported by VaoTsun
2017-05-05 09:21:47 +09:00
2e69d155da
Typo in README.md reported by dhx
2017-05-05 09:21:43 +09:00
870a367d3b
repmgr: prevent spurious error message when running 'standby switchover'
...
When 'repmgr standby follow' is run on a dormant server, with connection
parameters for the upstream node provided (which is done during the
switchover process to reintegrate the stopped former master into the
replication cluster), a spurious error message is generated about
a slot which cannot be deleted as it's active. During the switchover
process the current master's (former standby's) slot on the former master
is deleted at a later point so can be skipped here.
The error message is annoying but harmless and has no effect on the
switchover process.
Addresses GitHub #285 .
2017-04-10 23:00:10 +09:00
9c28d3626b
Update HISTORY
2017-03-20 14:20:52 +09:00
0916d8f2ad
repmgr: disallow node ids which are not positive signed 32 bit integers
...
Fixes GitHub #280
2017-03-20 11:26:34 +09:00
1964f890be
repmgr: enable master register --force with node foreign key dependency
...
Fixes GitHub #273
2017-03-20 10:03:38 +09:00
976a61005e
Only attempt to set synchronous transaction mode with valid connection
2017-03-17 20:33:29 +09:00
0c82278fd4
repmgr: fix command line parsing with hostname as an additional argument
...
Check explicitly whether -h/--hostname provided, otherwise PGHOST,
if set, will be misinterpreted.
2017-03-17 20:21:13 +09:00
0abfde3773
repmgr: ensure that data dir permissions set correctly when cloning in barman mode
2017-03-17 16:37:49 +09:00
1746831486
repmgr: fix standby clone with barman
...
As of Barman commit 5ff62d3255
2017-03-17 16:32:35 +09:00
8c8e368a69
repmgr: set "synchronous_commit" to "local" by default
...
Rather than set this for individual connections, we'll change the setting
each time a connection is made (except replication connections), which will
obviate the need to take this into consideration when making connections
in the application code.
Resolves GitHub #276 .
2017-03-17 11:32:25 +09:00
0ef532dcff
repmgr: improve standby clone when synchronous replication in use
...
Fixes GitHub #277
2017-03-16 16:46:08 +09:00
478407fd86
repmgr: fix standby clone with barman
...
As of Barman commit 5ff62d3255
2017-03-16 10:29:50 +09:00
05bfdfab2c
repmgr: fix command line parsing with hostname as an additional argument
...
Check explicitly whether -h/--hostname provided, otherwise PGHOST,
if set, will be misinterpreted.
2017-03-14 22:55:27 +09:00
29740dc41b
Bump version
...
3.3.1
2017-03-13 16:00:44 +09:00
ad6ecef2ab
repmgr: clean up standby follow code
2017-03-13 13:27:02 +09:00
5318d37462
README: fix typos
2017-03-13 13:20:56 +09:00
7244dda20f
repmgr: fix typo
2017-03-13 13:20:35 +09:00
e651284927
Update documentation/sample configuration with references to --wal-method
2017-03-13 13:20:20 +09:00
72a2ac284a
repmgr: improve logging of rsync actions
...
In particular, copy_remote_files() would report any kind of non-zero
exit status from rsync as an error, even though when cloning data
directories and tablespaces we explicitly ignore the "vanished
files" status (code 24) as it's expected behaviour for files in these
locations to disappear during the rsync copy process.
Conflicts:
HISTORY
2017-03-13 13:16:44 +09:00
cec01c6620
repmgr: improve standby follow log output
...
In particular suppress any error messages encountered when trying to
connect to the old upstream node, as these are not critical and
will lead to confusion.
2017-03-13 13:14:19 +09:00
989f683bc6
repmgr: have "standby follow" delete old replication slot, if possible
...
Addresses GitHub #272
2017-03-13 13:14:05 +09:00
fa30382f2c
When retrieving a node record, set upstream_node_id correctly.
...
-1 (NO_UPSTREAM_NODE) should be returned if the record's column is NULL.
2017-03-13 12:16:22 +09:00
defc2653e0
There where 2 barman configuration parameters missing in the repmgr.conf
...
sample file.
Added with some comments
2017-02-15 17:17:39 -03:00
67e8ca73b5
repmgrd: fix XLogRecPtr conversion function
2017-01-11 15:03:13 +09:00
a1a1d64e1f
repmgrd: fix usage description
...
Matches the one provided by repmgr.
2017-01-11 15:03:07 +09:00
76509038cc
repmgrd: prevent invalid apply lag value being written to the monitoring table
2017-01-11 15:03:02 +09:00
7f8e50c882
Update copyright notice to 2017
...
Also standardize case to "(c)"
2017-01-11 15:02:55 +09:00
5deb6c8ce4
rempgr: don't link to backend functions
...
The intent was to avoid maintaining duplicate code, but this approach
makes it difficult to build Debian packages (see GitHub #261 ).
As the functions in question are quite compact and unlikely to change,
we'll just use the adapted versions provided for 9.5 and earlier.
2017-01-04 16:55:09 +09:00
175ee8acfc
README: update version information
2017-01-04 10:59:13 +09:00
d1491f51a3
Remove erroneously added configuration item from repmgr.conf.sample
...
Per GitHub #262
2017-01-04 09:35:39 +09:00
bc9febdc48
repmgr: fix error message string
...
Per GitHub #263 .
2017-01-04 09:25:50 +09:00
b6cf22ac90
Update HISTORY
2016-12-27 14:49:50 +09:00
d89a73cbf4
repmgrd: fix log messages and code comments to reflect what is actually happening
...
Sometimes we're setting node status to active.
2016-12-27 14:48:34 +09:00
1f09e92e3f
Typo fix
2016-12-26 15:23:04 +09:00
1bdc72a07b
Updates to README and --help output
2016-12-26 15:23:00 +09:00
a6f1c6e483
repmgr: use provided --replication-user in pg_basebackup mode
2016-12-26 15:22:56 +09:00
6e14f0bc5d
repmgr: in rsync mode don't delete backup_history file
...
Make behaviour consistent with pg_basebackup.
2016-12-26 10:39:05 +09:00
a336d22bd9
repmgr: miscelleanous code cleanup
2016-12-26 10:39:00 +09:00
e88a8a9708
repmgr: standby register --wait-sync=0 can loop infinitely
2016-12-23 11:29:19 +09:00
8f3f4eb4a3
Update version number for 3.3 branch
2016-12-22 16:53:39 +09:00
dc18e5b791
repmgr: escape conninfo parameters when cloning from Barman
2016-12-22 12:21:44 +09:00
9da0914976
Consolidate various backported functions
2016-12-22 12:11:54 +09:00
666e71a589
repmgr: escape parameter values in primary_conninfo, if required
...
Addresses GitHub #253 .
2016-12-22 11:40:46 +09:00
062af91d36
Update HISTORY
2016-12-21 17:06:58 +09:00
571ad698db
Add documentation for standby register --force and --upstream-conninfo
2016-12-21 17:06:07 +09:00
742f7e167f
repmgr: support option --replication-user in STANDBY CLONE too
2016-12-14 17:00:03 +09:00
Ian Barwick