Mon Jun 28 12:09:35 PDT 2010
- Previous message: [Slony1-bugs] [Bug 138] New: groff detection in configure broken
- Next message: [Slony1-bugs] [Bug 120] store path - after slon has started does not take effect
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=127 Devin Ben-Hur <dbenhur at whitepages.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dbenhur at whitepages.com --- Comment #1 from Devin Ben-Hur <dbenhur at whitepages.com> 2010-06-28 12:09:35 PDT --- We noticed this behavior change when moving from 1.2x to 2.0x as it made some health monitors conducting sl_status lag-time polling uninformative on non-origin nodes. In the archives, I notice at least one other person encountering the problem too http://permalink.gmane.org/gmane.comp.db.postgresql.slony1.general/9029 This bug is marked as applying to v1.2, but the behavior effects v2.0 as well and gives non-origin nodes the appearance of accumulating tremendous replication lag. -- 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 138] New: groff detection in configure broken
- Next message: [Slony1-bugs] [Bug 120] store path - after slon has started does not take effect
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list