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
1fb2801639
repmgr: add option --replication-user
2016-12-14 15:58:11 +09:00
e3031f0204
repmgr: fix log message
2016-12-14 12:39:47 +09:00
79748f28f1
repmgr: improve STANDBY REGISTER sanity checks and log messages
2016-12-14 12:38:42 +09:00
46740b64a9
repmgr: enable forced registration of a node with a downstream cascaded standby
2016-12-14 12:22:41 +09:00
6557099832
repmgr: initial support for standby register --force
...
This functionality is intended for those cases where a cascading replication
cluster is being automatically provisioned and it might be necessary to
clone multiple levels in parallel.
As always, use of `--force` implies you know what you are doing.
2016-12-12 15:51:19 +09:00
083e288ac3
repmgr: add usage warnings for --no-conninfo-password
2016-12-08 23:01:46 +09:00
f5e3d7c041
Merge branch 'no-passwords'
...
GitHub pull request #255
2016-12-08 22:56:04 +09:00
402e02f4b7
Add an option to suppress passwords in recovery.conf/primary_conninfo
2016-12-08 22:36:18 +09:00
a21b16f960
Update HISTORY
2016-12-07 17:12:21 +09:00
be58af701b
repmgr: add option --upstream-conninfo
...
When executing `repmgr standby clone`, this enables the primary_conninfo
string set in recovery.conf to be explictly defined (rather than generated
from the upstream node's conninfo string and connection parameters).
This is primarily intended for those cases when an L2 cascaded standby
is being cloned from the cluster primary, and its intended upstream
might not yet be available.
2016-12-07 17:05:57 +09:00
eb2cdf8a98
repmgr: improve handling of command line parameter errors
...
Previously providing a parameter which requires a value (e.g. -f/--config-file)
would result in a misleading error like "Unknown option -f".
Rather than suppress getopt's error messages, we'll rely on these to inform
about missing required values or unknown options (as other PostgreSQL tools
do), though we will still provide our own list of command line errors and
warnings countered above and beyond getopt's sanity checks.
2016-12-05 14:40:32 +09:00
7cc0400c03
repmgr: add option --log-to-file; remove timestamp from log output by default
...
Log lines will still be prefixed with timestamp if `-log-to-file` used.
2016-12-05 14:09:41 +09:00
9788b2bd29
repmgr: don't display timestamp in log output
...
Differentiate between repmgr and repmgrd output
2016-12-05 10:44:30 +09:00
227f0190f7
repmgr: initial support for PostgreSQL 10
...
Handle directory name change from pg_xlog to pg_wal.
Note that some functions with "xlog" in their name may also change.
2016-12-02 12:06:08 +09:00
d6dbc70916
Update HISTORY
2016-11-25 08:17:01 +09:00
d2f4eda224
Note use of phbouncer %include directive
2016-11-23 09:33:30 +09:00
Ian Barwick