October 2013 Archives by author
- Messages sorted by: [ thread ] [ subject ] [ date ]
- More info on this list...
Starting: Thu Oct 3 10:33:37 PDT 2013
Ending: Tue Oct 29 13:44:10 PDT 2013
Messages: 50
- [Slony1-bugs] Postgres 9.3 + Slony-I 2.2.0 + PgAdmin 1.18.0 on Windows Server 2003 R2 Enterprise 32 Bit Sven Meirsman
- [Slony1-bugs] Postgres 9.3 + Slony-I 2.2.0 + PgAdmin 1.18.0 on Windows Server 2003 R2 Enterprise 32 Bit Sven Meirsman
- [PATCH] fixing the failover unit test. Steve Singer
- [Slony1-bugs] [Bug 315] Slony 2.1.1 will not build on Debian Wheezy bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 316] New: WAIT FOR EVENT with a non-existing CONFIRMED node is a no-op bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 317] New: When stdout of slonik is not a terminal it is fully buffered bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 318] New: FAILOVER can lead to an endless restart loop of slon bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 319] New: NULL pointer dereferenced on losing connection during SYNC bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 318] FAILOVER can lead to an endless restart loop of slon bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 318] FAILOVER can lead to an endless restart loop of slon bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 319] NULL pointer dereferenced on losing connection during SYNC bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 319] NULL pointer dereferenced on losing connection during SYNC bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 319] NULL pointer dereferenced on losing connection during SYNC bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 318] FAILOVER can lead to an endless restart loop of slon bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 320] New: no_failed column missing in sl_node following upgrade to 2.2.0 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 317] When stdout of slonik is not a terminal it is fully buffered bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 320] no_failed column missing in sl_node following upgrade to 2.2.0 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 320] no_failed column missing in sl_node following upgrade to 2.2.0 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 316] WAIT FOR EVENT with a non-existing CONFIRMED node is a no-op bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] New: constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 315] Slony 2.1.1 will not build on Debian Wheezy bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 313] EXECUTE SCRIPT error with sequences not replicated everywhere bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 312] Missing man pages in slony1-2.1.4-docs.tar.bz2 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 311] tar error when extracting slony1-2.1.4-docs.tar.bz2 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 309] sl_failover_targets view missing after upgrade from 2.1 to 2.2 using UPDATE FUNCTIONS. bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 310] slon loops restarting on a FAILOVER bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 304] Sequences are not SYNC'd as part of EXECUTE SCRIPT bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 299] moveset can cause a subscriber to pull data it has already seen bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 292] sl_log_1 & sl_log_2 table not cleaning bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 322] New: clone prepare can fail to replicate bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 322] clone prepare can fail to replicate bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 322] clone prepare can fail to replicate bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 323] New: Clustertest "Fail Over Test" may unsubscribe node 4 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 323] Clustertest "Fail Over Test" may unsubscribe node 4 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 322] clone prepare can fail to replicate bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 322] clone prepare can fail to replicate bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 323] Clustertest "Fail Over Test" may unsubscribe node 4 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 323] Clustertest "Fail Over Test" may unsubscribe node 4 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 321] constant provider disconnects & reconnects bugzilla-daemon at main.slony.info
Last message date:
Tue Oct 29 13:44:10 PDT 2013
Archived on: Tue Oct 29 13:44:12 PDT 2013
- Messages sorted by: [ thread ] [ subject ] [ date ]
- More info on this list...
This archive was generated by Pipermail 0.09 (Mailman edition).