May 2010 Archives by thread

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

Starting: Mon May 3 18:12:37 PDT 2010
Ending: Mon May 31 13:29:33 PDT 2010
Messages: 53

• [Slony1-bugs] UTF-8 encoding error...problems with 2.0.3   Andrew Eross
• [Slony1-bugs] UTF-8 encoding error...problems with 2.0.3   Steve Singer
• [Slony1-bugs] An old event not confirmed: A possible bug?   Gurjeet Singh
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Jan Wieck
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Gurjeet Singh
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Cyril Scetbon
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Jan Wieck
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Cyril Scetbon
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Jan Wieck
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Cyril Scetbon
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Jan Wieck
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Cyril Scetbon
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Jan Wieck
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Cyril Scetbon
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Jan Wieck
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Steve Singer
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Gurjeet Singh
• [Slony1-bugs] [Slony1-general] An old event not confirmed: A possible bug?   Cyril Scetbon
• [Slony1-bugs] [Bug 119] New: cloneNodeFinish() fails updating sequences   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 119] cloneNodeFinish() fails updating sequences   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 120] New: store path - after slon has started does not take effect   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 121] New: 'provider node -1 for set' when subscribing from a forwarding node   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 122] New: bad error message: subscribe a set with no paths to a dropped node   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 122] bad error message: subscribe a set with no paths to a dropped node   bugzilla-daemon at main.slony.info
• [Slony1-bugs] Slony triggers included in pg_dump   Gurjeet Singh
• [Slony1-bugs] [Slony1-general] Slony triggers included in pg_dump   Steve Singer
• [Slony1-bugs] [Slony1-general] Slony triggers included in pg_dump   Gurjeet Singh
• [Slony1-bugs] [Slony1-general] Slony triggers included in pg_dump   Steve Singer
• [Slony1-bugs] [Slony1-general] Slony triggers included in pg_dump   David Fetter
• [Slony1-bugs] Slony triggers included in pg_dump   Jan Wieck
• [Slony1-bugs] Slony triggers included in pg_dump   Gurjeet Singh
• [Slony1-bugs] [Slony1-general] Slony triggers included in pg_dump   Steve Singer
• [Slony1-bugs] [Slony1-general] Slony triggers included in pg_dump   Gurjeet Singh
• [Slony1-bugs] [Bug 123] New: Adding a node shortly after deleting it causes 'node -1 not found'   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 123] New: Adding a node shortly after deleting it causes 'node -1 not found'   Jan Wieck
• [Slony1-bugs] [Bug 123] New: Adding a node shortly after deleting it causes 'node -1 not found'   Steve Singer
• [Slony1-bugs] [Bug 124] New: EXECUTE SCRIPT, ONLY ON != EVENT NODE is wrong   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 125] New: New init script   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 125] New init script   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 125] New init script   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 125] New init script   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 125] New init script   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 125] New init script   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 125] New init script   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 125] New init script   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 126] New: slon sometimes does not recover from a network outage   bugzilla-daemon at main.slony.info
• [Slony1-bugs] Events confirmed not removed   Cyril Scetbon
• [Slony1-bugs] [Bug 127] New: sync events are not generated on nodes that are not a set origin   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Slony1-general] Slony triggers included in pg_dump   Jan Wieck
• [Slony1-bugs] [Bug 128] New: DROP TABLE replicatedTable leaves the cluster in a bad state   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 129] New: FAILOVER command does not update sl_subscriber   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 130] New: failover does not seem to update sl_set   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 131] New: two concurrent subscribe sets can deadlock each other   bugzilla-daemon at main.slony.info

Last message date: Mon May 31 13:29:33 PDT 2010
Archived on: Thu Jun 24 04:29:40 PDT 2010

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

---

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