June 2011 Archives by thread

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

Starting: Thu Jun 2 13:52:01 PDT 2011
Ending: Thu Jun 30 12:31:18 PDT 2011
Messages: 50

• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 218] New: 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 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 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 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 219] New: truncate triggers in 9.1 don't load   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 219] truncate triggers in 9.1 don't load   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 219] truncate triggers in 9.1 don't load   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 204] Failover to a non-direct subscriber fails   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 220] New: parameters to reshape subscription are passed in the wrong order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 220] parameters to reshape subscription are passed in the wrong order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 220] parameters to reshape subscription are passed in the wrong order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 220] parameters to reshape subscription are passed in the wrong order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 216] monitor threads don't work on Win32   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 214] Slonikconfdump.sh lost   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 215] Add Slony to PGXN   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 221] New: implicit cast (int to text) make ERROR at initialize and cleanup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 221] implicit cast (int to text) make ERROR at initialize and cleanup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 221] implicit cast (int to text) make ERROR at initialize and cleanup   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 217] Changing the primary key of a replicated table leads to trouble   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 222] New: cleanup thread can lock out new application connections   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 222] cleanup thread can lock out new application connections   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 222] cleanup thread can lock out new application connections   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 222] cleanup thread can lock out new application connections   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 222] cleanup thread can lock out new application connections   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 223] New: slonik can wait for a node it just uninstalled   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 216] monitor threads don't work on Win32   bugzilla-daemon at main.slony.info

Last message date: Thu Jun 30 12:31:18 PDT 2011
Archived on: Thu Jun 30 12:31:20 PDT 2011

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

---

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