8f031d3c20
Add "includedir_internal" to "PG_CPPFLAGS"
2017-09-19 22:19:04 +09:00
20224d1296
Prevent compiler truncation warnings
2017-09-19 16:24:01 +09:00
e64600d3e3
Prevent compiler truncation warnings
2017-09-19 16:15:47 +09:00
bb311892b5
Remove unused code
2017-09-19 14:47:49 +09:00
ea82d52151
Fix typo in repmgr help output
2017-09-18 14:21:33 +00:00
34fb09cae4
Add placeholder test
2017-09-18 21:55:23 +09:00
28675af630
Update README
2017-09-18 15:58:24 +09:00
e3defc507e
Merge branch 'pg93'
2017-09-18 15:55:32 +09:00
3dad337413
Clarification at top of README
2017-09-18 06:50:32 +01:00
33a3283135
Fix a few typos in descriptive text
2017-09-18 06:07:38 +01:00
994975b8c6
Minor typos in descriptive text
2017-09-18 05:53:52 +01:00
17397334c9
Typo
2017-09-18 05:48:58 +01:00
1197c11c59
"standby clone": skip tablespace mapping in PostgreSQL 9.3
2017-09-18 13:26:35 +09:00
30b11c08e6
Disable any configuration settings not compatible with PostgreSQL 9.3
...
And emit a warning while we're at it.
2017-09-18 13:12:38 +09:00
750a776f1d
Fixes for PostgreSQL 9.3 support
2017-09-18 11:00:39 +09:00
ea2693bc75
Move create_recovery_file() et al to repmgr-action-standby.c
...
As they're only ever called from there.
2017-09-18 09:53:08 +09:00
3600d98856
Remove test configuration files
2017-09-17 07:44:14 +09:00
5a3c26a0b8
Makefile: better fix for SCRIPTS_built and 9.4
2017-09-17 07:42:58 +09:00
31c7cb4e9a
Fixes for 9.3 support
2017-09-15 17:13:17 +09:00
192f968d29
Workaround for 9.3
2017-09-15 11:57:33 +09:00
687c8b4e27
Initial changes for 9.3 support
2017-09-15 10:27:37 +09:00
68f4a37ca4
Update README
2017-09-14 08:57:16 +09:00
f5c9c74a75
Minor log output tweak
2017-09-14 08:57:16 +09:00
e040f95aaa
"standby clone": fix replication slot generation
...
Slot on source node was being deleted even if source node is the intended
upstream node.
2017-09-14 08:47:56 +09:00
55f203a2fc
Add "-o ConnectTimeout=10" as default in "ssh_options"
2017-09-13 13:23:16 +09:00
f194c254b8
Update README
...
Clarify that "standby switchover" can only be executed on a direct downstream
of the current primary.
2017-09-13 11:55:40 +09:00
e583e2eb40
"standby switchover": fix error message
2017-09-13 11:30:29 +09:00
cf58d9460c
Add missing README sections
2017-09-13 08:11:56 +09:00
5da0275cdc
Fix configuration file detection logging
...
The logger won't be initialised at this point, so we'll have to output
directly.
This is mainly useful for diagnosing how repmgr is finding (or not finding)
its configuration file.
2017-09-12 12:14:28 +09:00
621ca352df
Dynamically generate "repmgr_version.h"
2017-09-12 12:02:26 +09:00
b6cd816923
Tidy up some log output
2017-09-12 11:08:41 +09:00
13d55b9bd8
Update configfile location logging output
2017-09-11 22:13:52 +09:00
cf59944a35
Fix "repmhr cluster --help" output
2017-09-11 21:25:30 +09:00
f617c83434
Enable packagers to explicitly provide the configuration file location as a patch
2017-09-11 17:38:12 +09:00
b6b31b15b2
Implement "repmgr cluster cleanup"
2017-09-11 13:48:46 +09:00
a9f4a027a7
pgindent run
2017-09-11 11:14:13 +09:00
0e6699ecb6
Formatting updates before pgindent run
2017-09-11 11:05:43 +09:00
c9f3f971e2
Add further documentation files
2017-09-11 11:05:43 +09:00
36d63f499d
Add further documentation files
2017-09-11 11:00:48 +09:00
64ec85bb10
Clarify _do_node_archive_config() usage
2017-09-11 11:00:13 +09:00
f19d546fa1
Merge pull request #2 from gciolli/master
...
Small clarification on sudo-based configuration (#1 )
2017-09-11 10:23:37 +09:00
9b2a35c5e3
Add/update various documents
2017-09-11 10:21:20 +09:00
3447257ae4
repmgrd: minor fixes and comment updates
2017-09-08 20:59:21 +09:00
e16f68dfce
Use "MODULE_PATHNAME" in function definitions
2017-09-08 20:46:45 +09:00
ba38b99590
repmgrd: fix logging when reloading configuration
2017-09-08 14:52:33 +09:00
e4f7dc8234
Add copyright notices
2017-09-08 13:27:39 +09:00
82db2237ad
Add files as placeholders
2017-09-08 08:16:34 +09:00
ab8cb9d471
"standby register": remove database connection parameter warning
2017-09-07 17:09:29 +09:00
b6a27b975d
"standby clone": improve handling when designated upstream doesn't yet exist
...
This situation can occur in provisioning environments, where a node's
upstream may not exist at the point it's cloned. If replication slots
are in use, we'll need to make sure no attempt is made to create
the replication slot on the designated upstream, as that will end in
tears. We assume the user will be prepared to complete this step manually.
2017-09-07 12:35:27 +09:00
3787dd3795
"standby switchover": better handling of remote execution failure
2017-09-07 11:50:56 +09:00
Ian Barwick