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

node rejoin: better document unrecoverable situation

Browse Source 
If two diverged nodes are on the same timeline, currently there's
no way of establishing the divergence point and pg_rewind
is ineffective.

Clarify the log messages to make this clearer.
This commit is contained in:
Ian Barwick
2020-10-08 21:07:16 +09:00
parent 7969dc4800
commit 758c18985c
1 changed files with 15 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
repmgr-client.c
View File

@@ -4208,12 +4208,26 @@ check_node_can_attach(TimeLineID local_tli, XLogRecPtr local_xlogpos, PGconn *fo
}
else
{
log_error(_("this node is ahead of the %s target"), action);
/*
* Unable to follow or join to a node we're ahead of, if we're on the
* same timeline. Also, pg_rewind does not detect this situation,
* as there is no definitive fork point.
*
* Note that Pg will still happily attach to the upstream in state "streaming"
* for a while but then detach with an endless stream of
* "record with incorrect prev-link" errors.
*/
log_error(_("this node ahead of the %s target on the same timeline (%i)"), action, local_tli);
log_detail(_("local node lsn is %X/%X, %s target lsn is %X/%X"),
format_lsn(local_xlogpos),
action,
format_lsn(follow_target_xlogpos));
if (is_rejoin == true)
{
log_hint(_("the --force-rewind option is ineffective in this case"));
}
success = false;
}
}