mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-22 22:56:29 +00:00
Update README/TODO about following non-master server
This commit is contained in:
@@ -711,8 +711,9 @@ updated to reflect this:
|
||||
|
||||
|
||||
Note that with cascading replication, `repmgr standby follow` can also be
|
||||
used to detach a standby from its current upstream server and follow another
|
||||
upstream server, including the master.
|
||||
used to detach a standby from its current upstream server and follow the
|
||||
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
|
||||
|
||||
3
TODO
3
TODO
@@ -53,6 +53,9 @@ Planned feature improvements
|
||||
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).
|
||||
|
||||
* repmgr: enable "standby follow" to point a standby at another standby, not
|
||||
just the replication cluster master (see GitHub #130)
|
||||
|
||||
|
||||
Usability improvements
|
||||
======================
|
||||
|
||||
Reference in New Issue
Block a user