Wed Nov 17 05:38:55 PST 2010
- Previous message: [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order
- Next message: [Slony1-bugs] [Bug 166] Provide a way of counting the number of outstanding operations in a sync
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=166 Summary: Provide a way of counting the number of outstanding operations in a sync Product: Slony-I Version: devel Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: low Component: core scripts AssignedTo: slony1-bugs at lists.slony.info ReportedBy: ssinger at ca.afilias.info CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 This is a feature request. It would be very useful from a 'what the heck is my system doing' point of view to know how many operations make up each outstanding SYNC request. A system that is behind by 1000 SYNC's with no row edits in any of them is in a very different state than a system that is 1000 SYNC's behind each with 10,000 UPDATE statements. Similarly if the next/current SYNC to be processed consists of a million rows that might explain why replication 'seems' to have stopped from an sl_status point of view. The test_slony_state.pl script seems like the most logical place to add this though other ideas are welcome. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug. You are the assignee for the bug.
- Previous message: [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order
- Next message: [Slony1-bugs] [Bug 166] Provide a way of counting the number of outstanding operations in a sync
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list