Summary: | Slonik ABORT command | ||
---|---|---|---|
Product: | Slony-I | Reporter: | Christopher Browne <cbbrowne> |
Component: | slonik | Assignee: | Christopher Browne <cbbrowne> |
Status: | ASSIGNED --- | ||
Severity: | enhancement | CC: | slony1-bugs |
Priority: | low | ||
Version: | devel | ||
Hardware: | All | ||
OS: | All |
Description
Christopher Browne
2010-12-03 13:33:17 UTC
Discussion on list began...http://lists.slony.info/pipermail/slony1-general/2011-January/011459.html http://lists.slony.info/pipermail/slony1-general/2011-January/011459.html Additional suggestion: Are there any non-SYNC events outstanding? Scripts that modify the cluster configuration may not care about how far a node is behind in data, but definitely need to assume that the current configuration is stable and not altered underneath by older events, that haven't propagated through the cluster. - Jan Perhaps this should be extended to a fuller "conditional" to mostly replace the present TRY block concept. Have to think about that some more... |