github/repmgr
1
0
Fork 0
mirror of https://github.com/EnterpriseDB/repmgr.git synced 2026-03-27 08:56:29 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

Update README/TODO about following non-master server

Browse Source
This commit is contained in:
Ian Barwick
2016-07-01 12:09:35 +09:00
parent c5a721a3cf
commit 013b4b4b8a
2 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
README.md
View File

@@ -711,8 +711,9 @@ updated to reflect this:
Note that with cascading replication, `repmgr standby follow` can also be Note that with cascading replication, `repmgr standby follow` can also be
used to detach a standby from its current upstream server and follow another used to detach a standby from its current upstream server and follow the
upstream server, including the master. master. However it's currently not possible to have it follow another standby;
we hope to improve this in a future release.
Performing a switchover with repmgr Performing a switchover with repmgr

3
TODO
View File

@@ -53,6 +53,9 @@ Planned feature improvements
requested, activate the replication slot using pg_receivexlog to negate the requested, activate the replication slot using pg_receivexlog to negate the
need to set `wal_keep_segments` just for the initial clone (9.4 and 9.5). need to set `wal_keep_segments` just for the initial clone (9.4 and 9.5).
* repmgr: enable "standby follow" to point a standby at another standby, not
just the replication cluster master (see GitHub #130)
Usability improvements Usability improvements
====================== ======================