August 2011 Archives by subject

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

Starting: Wed Aug 3 12:07:43 PDT 2011
Ending: Wed Aug 31 12:42:22 PDT 2011
Messages: 66

• [Slony1-bugs] [Bug 173] Slonik ABORT command   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 173] Slonik ABORT command   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 218] slon often has to retry transactions due to concurrent update in 2.1.0.b2   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 218] slon often has to retry transactions due to concurrent update in 2.1.0.b2   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 218] slon often has to retry transactions due to concurrent update in 2.1.0.b2   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 218] slon often has to retry transactions due to concurrent update in 2.1.0.b2   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 218] slon often has to retry transactions due to concurrent update in 2.1.0.b2   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 228] 'drop node' in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 228] 'drop node' in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 228] 'drop node' in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 228] 'drop node' in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 228] 'drop node' in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 228] New: 'drop node' in a try block   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 229] creating a set then adding a table to a different set can deadlock   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 229] creating a set then adding a table to a different set can deadlock   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 229] creating a set then adding a table to a different set can deadlock   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 229] creating a set then adding a table to a different set can deadlock   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 229] creating a set then adding a table to a different set can deadlock   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 229] New: creating a set then adding a table to a different set can deadlock   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 230] New: Timestamps stopped showing up in the slon_log on some platforms   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 230] Timestamps stopped showing up in the slon_log on some platforms   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 230] Timestamps stopped showing up in the slon_log on some platforms   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 230] Timestamps stopped showing up in the slon_log on some platforms   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 230] Timestamps stopped showing up in the slon_log on some platforms   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 230] Timestamps stopped showing up in the slon_log on some platforms   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 230] Timestamps stopped showing up in the slon_log on some platforms   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 231] Bad regex in start_slon.sh   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 231] Bad regex in start_slon.sh   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 231] Bad regex in start_slon.sh   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 231] Bad regex in start_slon.sh   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 231] New: Bad regex in start_slon.sh   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 232] New: slony error handling capabilities   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 232] slony error handling capabilities   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 232] slony error handling capabilities   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 233] New: slonik segfaults on subscribe set, when the set does not exist.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 233] slonik segfaults on subscribe set, when the set does not exist.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 233] slonik segfaults on subscribe set, when the set does not exist.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 233] slonik segfaults on subscribe set, when the set does not exist.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 234] New: pg_dump + restore of a slony node leaves the node corrupt   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 234] pg_dump + restore of a slony node leaves the node corrupt   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 235] New: 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 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 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] New: misformatted log messages   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 237] New: drop set does not remove truncate triggers   bugzilla-daemon at main.slony.info

Last message date: Wed Aug 31 12:42:22 PDT 2011
Archived on: Wed Aug 31 12:42:23 PDT 2011

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

---

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