173 2010-12-03 13:33:00 -0800 Slonik ABORT command 2011-08-08 12:40:40 -0700 1 1 1 Unclassified Slony-I slonik devel All All ASSIGNED low enhancement --- 1 cbbrowne cbbrowne slony1-bugs cbbrowne 2010-12-03 13:33:17 -0800 http://wiki.postgresql.org/wiki/SlonyBrainstorming#ABORT Initially mentioned by Vivek Khera General point: Fail if replication is behind Reasonable criteria: - event count - "within 3 events is OK" - time interval "behind by no more than 15 seconds is OK" Other Health Criteria - Is node there? - Is replication set there? - Is subscription active? - Run SQL, fail if ERROR cbbrowne 2011-01-13 13:38:40 -0800 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 cbbrowne 2011-01-27 09:21:03 -0800 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 cbbrowne 2011-08-03 12:07:43 -0700 Perhaps this should be extended to a fuller "conditional" to mostly replace the present TRY block concept. Have to think about that some more... cbbrowne 2011-08-08 12:40:40 -0700 As observed in bug #228, there would be some use in having conditionals used to pick between blocks of Slonik code. We're not necessarily going to want to abort.