May 2011 Archives by author
- Messages sorted by: [ thread ] [ subject ] [ date ]
- More info on this list...
Starting: Mon May 2 00:39:34 PDT 2011
Ending: Tue May 31 08:18:34 PDT 2011
Messages: 54
- [Slony1-bugs] [Bug 202] remote_worker error creating log cursor bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 90] Error while running "make" for Slony 2.0 on Solaris 2.11 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 179] Implicit WAIT FOR EVENT bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 171] Health Check: Verify node's parentage bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 178] More sophisticated FAILOVER bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 203] New: Use of "name" type conflicts with pg_upgrade bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 137] execute script does not get applied in the correct order bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 204] New: Failover to a non-direct subscriber fails 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 205] New: Upgrade to 2.1.0b1 fails bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 206] New: Upgrade from 2.0.0 to 2.1.0b1 fails bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 207] New: create set in a try block rollsback bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 207] create set in a try block rollsback bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 207] create set in a try block rollsback bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 207] create set in a try block rollsback bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 207] create set in a try block rollsback bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 208] New: default table id doesn't work in 2.1.0.b1 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 209] New: PGRES_FATAL_ERROR ERROR when installing slony in postgresql 7.4.30 DB bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 207] create set in a try block rollsback bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 209] PGRES_FATAL_ERROR ERROR when installing slony in postgresql 7.4.30 DB bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 208] default table id doesn't work in 2.1.0.b1 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 207] create set in a try block rollsback bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 210] New: mergeSet needs to wait for both sets to be subscribed bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 210] mergeSet needs to wait for both sets to be subscribed bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 210] mergeSet needs to wait for both sets to be subscribed bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 211] New: altperl tools broken in 2.1.0b1 (try blocks) bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 212] New: moveSet leaves cluster with no origin bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 210] mergeSet needs to wait for both sets to be subscribed bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 213] New: failover while slon is not running bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 211] altperl tools broken in 2.1.0b1 (try blocks) bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 210] mergeSet needs to wait for both sets to be subscribed bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 206] Upgrade from 2.0.0 to 2.1.0b1 fails bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 205] Upgrade to 2.1.0b1 fails 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 137] execute script does not get applied in the correct order bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 214] New: Slonikconfdump.sh lost bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 214] Slonikconfdump.sh lost bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 215] New: Add Slony to PGXN bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 215] Add Slony to PGXN bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 208] default table id doesn't work in 2.1.0.b1 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 208] default table id doesn't work in 2.1.0.b1 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 208] default table id doesn't work in 2.1.0.b1 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 216] New: monitor threads don't work on Win32 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 216] monitor threads don't work on Win32 bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 217] New: 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 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 217] Changing the primary key of a replicated table leads to trouble bugzilla-daemon at main.slony.info
Last message date:
Tue May 31 08:18:34 PDT 2011
Archived on: Tue May 31 08:18:36 PDT 2011
- Messages sorted by: [ thread ] [ subject ] [ date ]
- More info on this list...
This archive was generated by Pipermail 0.09 (Mailman edition).