November 2011 Archives by subject

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...

Starting: Fri Nov 4 13:02:08 PDT 2011
Ending: Wed Nov 30 13:14:36 PST 2011
Messages: 65

• [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 156] Slon on startup should have "health check"   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 161] EXECUTE SCRIPT fails to execute multi-line commands   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 178] More sophisticated FAILOVER   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 178] More sophisticated FAILOVER   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 178] More sophisticated FAILOVER   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 178] More sophisticated FAILOVER   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 192] Cluster test output not specific enough   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 197] Documentation Images Don't Work   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 229] creating a set then adding a table to a different set can deadlock   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 235] SYNC GROUP size bugs   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 235] SYNC GROUP size bugs   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 235] SYNC GROUP size bugs   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 235] SYNC GROUP size bugs   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 235] SYNC GROUP size bugs   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 236] misformatted log messages   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 236] misformatted log messages   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 236] misformatted log messages   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 236] misformatted log messages   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 236] misformatted log messages   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 237] drop set does not remove truncate triggers   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 244] create set is not well parsed   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 244] create set is not well parsed   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 244] create set is not well parsed   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 244] create set is not well parsed   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 244] create set is not well parsed   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 247] New: Slony log shipper doesn't parse TRUNCATE   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 247] Slony log shipper doesn't parse TRUNCATE   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 247] Slony log shipper doesn't parse TRUNCATE   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 247] Slony log shipper doesn't parse TRUNCATE   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 248] New: Log shipper targets can't add sequences after initial setup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 249] New: TRUNCATE log trigger not working quite right   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 249] TRUNCATE log trigger not working quite right   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 250] Log shipper does not report application name   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 250] Log shipper does not report application name   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 250] Log shipper does not report application name   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 250] Log shipper does not report application name   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 250] Log shipper does not report application name   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 250] New: Log shipper does not report application name   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 251] New: RPM Repository link on page 19 is out of date   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 251] RPM Repository link on page 19 is out of date   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 251] RPM Repository link on page 19 is out of date   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 251] RPM Repository link on page 19 is out of date   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 252] New: cloneNodePrepare() stores invalid conninfo in sl_path   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 253] In the event of OID mismatch, slon confirms replication events without actually actioning them   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 253] In the event of OID mismatch, slon confirms replication events without actually actioning them   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 253] In the event of OID mismatch, slon confirms replication events without actually actioning them   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 253] New: In the event of OID mismatch, slon confirms replication events without actually actioning them   bugzilla-daemon at main.slony.info

Last message date: Wed Nov 30 13:14:36 PST 2011
Archived on: Wed Nov 30 13:14:39 PST 2011

• Messages sorted by: [ thread ] [ author ] [ date ]
• More info on this list...

---

This archive was generated by Pipermail 0.09 (Mailman edition).