September 2010 Archives by thread

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

Starting: Thu Sep 2 11:54:04 PDT 2010
Ending: Mon Sep 13 13:42:56 PDT 2010
Messages: 31

• [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 80] slon daemon restarts itself in a loop after failover()   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state   bugzilla-daemon at main.slony.info
• No subject  
• No subject  
• [Slony1-bugs] [Bug 139] sighandler is calling non async safe functions   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 139] sighandler is calling non async safe functions   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 121] 'provider node -1 for set' when subscribing from a forwarding node   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 154] New: moving tables to another schema does not update sl_table on the subscriber   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 154] moving tables to another schema does not update sl_table on the subscriber   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 154] moving tables to another schema does not update sl_table on the subscriber   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 154] moving tables to another schema does not update sl_table on the subscriber   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 155] New: slon can segfault when the postgres backend abnormally terminates   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 156] New: Slon on startup should have "health check"   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 156] Slon on startup should have "health check"   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 128] DROP TABLE replicatedTable leaves the cluster in a bad state   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 124] EXECUTE SCRIPT, ONLY ON != EVENT NODE is wrong   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 139] sighandler is calling non async safe functions   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info

Last message date: Mon Sep 13 13:42:56 PDT 2010
Archived on: Wed Nov 3 08:53:16 PDT 2010

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

---

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