August 2010 Archives by thread

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

Starting: Tue Aug 3 10:51:05 PDT 2010
Ending: Tue Aug 31 12:55:36 PDT 2010
Messages: 191

• [Slony1-bugs] [Bug 132] ERROR: duplicate key value violates unique constraint "sl_nodelock-pkey"   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 145] Document Mistake   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 143] definition of sl_status.st_lag_time suspicious   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 144] replicate_partition stored procedure doesn't start replicating changes to the new table   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 122] bad error message: subscribe a set with no paths to a dropped node   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 146] New: Remove logic for using DELETE on sl_log_1/sl_log_2   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 146] Remove logic for using DELETE on sl_log_1/sl_log_2   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 146] Remove logic for using DELETE on sl_log_1/sl_log_2   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 92] Events and Confirmations are not propagating   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 127] sync events are not generated on nodes that are not a set origin   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 142] Minimize security profile   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 142] Minimize security profile   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 141] altertablerestore() is obsolete in 2.0+   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 147] New: TABLE ADD KEY is no longer supported in 2.x and yet slonik creates scripts using it.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 147] TABLE ADD KEY is no longer supported in 2.x and yet slonik creates scripts using it.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 147] TABLE ADD KEY is no longer supported in 2.x and yet slonik creates scripts using it.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 147] TABLE ADD KEY is no longer supported in 2.x and yet slonik creates scripts using it.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 147] TABLE ADD KEY is no longer supported in 2.x and yet slonik creates scripts using it.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 147] TABLE ADD KEY is no longer supported in 2.x and yet slonik creates scripts using it.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 147] TABLE ADD KEY is no longer supported in 2.x and yet slonik creates scripts using it.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 142] Minimize security profile   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 141] altertablerestore() is obsolete in 2.0+   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 141] altertablerestore() is obsolete in 2.0+   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 142] Minimize security profile   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 142] Minimize security profile   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 142] Minimize security profile   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 122] bad error message: subscribe a set with no paths to a dropped node   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 142] Minimize security profile   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 136] listen paths not being rebuilt correctly   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 142] Minimize security profile   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 134] TRUNCATE support   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 148] New: TablesToVacuum tries to vacuum pg_listener which no longer exists in 9.0   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 148] TablesToVacuum tries to vacuum pg_listener which no longer exists in 9.0   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 148] TablesToVacuum tries to vacuum pg_listener which no longer exists in 9.0   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 148] TablesToVacuum tries to vacuum pg_listener which no longer exists in 9.0   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 148] TablesToVacuum tries to vacuum pg_listener which no longer exists in 9.0   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 148] TablesToVacuum tries to vacuum pg_listener which no longer exists in 9.0   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 118] initial copy of an inherited table can leave the table empty   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 134] TRUNCATE support   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 127] sync events are not generated on nodes that are not a set origin   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 78] Vacuum of sl_log_2 with 42M rows is blocking replication   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 78] Vacuum of sl_log_2 with 42M rows is blocking replication   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 78] Vacuum of sl_log_2 with 42M rows is blocking replication   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 78] Vacuum of sl_log_2 with 42M rows is blocking replication   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 120] store path - after slon has started does not take effect   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 134] TRUNCATE support   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 137] excute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 137] excute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 137] excute script does not get applied in the correct order   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 127] sync events are not generated on nodes that are not a set origin   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 92] Events and Confirmations are not propagating   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 120] store path - after slon has started does not take effect   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 92] Events and Confirmations are not propagating   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 130] failover does not seem to update sl_set   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 81] duplicate key sl_nodelock-pkey and duplicate slon(8) processes not detected   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 42] schemadoc formatting bug   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 78] Vacuum of sl_log_2 with 42M rows is blocking replication   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 149] New: localListener thread failures on startup can deadlock slon   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 149] localListener thread failures on startup can deadlock slon   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 149] localListener thread failures on startup can deadlock slon   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 149] localListener thread failures on startup can deadlock slon   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 134] TRUNCATE support   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 115] Slonik should detect + error out on scripts that have a WAIT FOR EVENT in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 115] Slonik should detect + error out on scripts that have a WAIT FOR EVENT in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 17] slony doesn't build with a 'virtual' postgresql installation done with DESTDIR   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 77] Missing confirm records for events in sl_confirm table   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 99] unable to set datestyle   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 99] unable to set datestyle   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 106] Misleading error message "Unable to set datestyle"   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 115] Slonik should detect + error out on scripts that have a WAIT FOR EVENT in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 14] Pull lexer from psql   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 150] New: Documenting Bugzilla Usage for Slony-I   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 150] Documenting Bugzilla Usage for Slony-I   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 150] Documenting Bugzilla Usage for Slony-I   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 150] Documenting Bugzilla Usage for Slony-I   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 10] Create a CANCEL SUBSCRIPTION command   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 11] duplicate_node.sh   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 18] Patch to shorten "attkind" on logtrigger functions   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 53] High memory usage when using high table id   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 57] Missing data and syncs ignored   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 59] slony doesn't escape varchar fields properly, making it impossible to replicate varchar or bytea columns in some cases   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 62] Initial subscription blocks with "sequence ID <xxx> has already been assigned"   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 79] --prefix and --exec-prefix options don't function as expected   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 10] Create a CANCEL SUBSCRIPTION command   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 111] node -1 not found in runtime configuration   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 138] groff detection in configure broken   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 138] groff detection in configure broken   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 138] groff detection in configure broken   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 104] slon core in sched_add_fdset   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 79] --prefix and --exec-prefix options don't function as expected   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 79] --prefix and --exec-prefix options don't function as expected   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 136] listen paths not being rebuilt correctly   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 115] Slonik should detect + error out on scripts that have a WAIT FOR EVENT in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 13] Change Slony-I to use PGXS   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 134] TRUNCATE support   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 134] TRUNCATE support   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 67] Array overrun in logtrigger()   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 41] Links to stored procedures prefixed with 'schemadoc' everywhere   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 124] EXECUTE SCRIPT, ONLY ON != EVENT NODE is wrong   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 17] slony doesn't build with a 'virtual' postgresql installation done with DESTDIR   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 99] unable to set datestyle   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 126] slon sometimes does not recover from a network outage   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 126] slon sometimes does not recover from a network outage   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 17] slony doesn't build with a 'virtual' postgresql installation done with DESTDIR   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 117] syslog=2, messages go both to syslog and the standard output.   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 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.   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 125] New init script   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 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 104] slon core in sched_add_fdset   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 138] groff detection in configure broken   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 138] groff detection in configure broken   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 104] slon core in sched_add_fdset   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 126] slon sometimes does not recover from a network outage   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 117] syslog=2, messages go both to syslog and the standard output.   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 80] slon daemon restarts itself in a loop after failover()   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 81] duplicate key sl_nodelock-pkey and duplicate slon(8) processes not detected   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 121] 'provider node -1 for set' when subscribing from a forwarding node   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 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 115] Slonik should detect + error out on scripts that have a WAIT FOR EVENT in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 75] Bugs: (1) Initialize forgotten cs->plan_active_log. (2) Session_replication_role and "SET datestyle TO 'ISO'" in slonik at connection start.   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 130] failover does not seem to update sl_set   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 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 62] Initial subscription blocks with "sequence ID <xxx> has already been assigned"   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 99] unable to set datestyle   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 115] Slonik should detect + error out on scripts that have a WAIT FOR EVENT in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 117] syslog=2, messages go both to syslog and the standard output.   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 124] EXECUTE SCRIPT, ONLY ON != EVENT NODE is wrong   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 126] slon sometimes does not recover from a network outage   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 132] ERROR: duplicate key value violates unique constraint "sl_nodelock-pkey"   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 136] listen paths not being rebuilt correctly   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 144] replicate_partition stored procedure doesn't start replicating changes to the new table   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 115] Slonik should detect + error out on scripts that have a WAIT FOR EVENT in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 115] Slonik should detect + error out on scripts that have a WAIT FOR EVENT in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 115] Slonik should detect + error out on scripts that have a WAIT FOR EVENT in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 117] syslog=2, messages go both to syslog and the standard output.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 151] New: Let DDL for EXECUTE SCRIPT to be specified inline   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 151] Let DDL for EXECUTE SCRIPT to be specified inline   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 152] New: Command line argument to only echo DDL on failure   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 152] Command line argument to only echo DDL on failure   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 153] New: Include output from an executable.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 153] Include output from an executable.   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 153] Include output from an executable.   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 115] Slonik should detect + error out on scripts that have a WAIT FOR EVENT in a try block   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 132] ERROR: duplicate key value violates unique constraint "sl_nodelock-pkey"   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 136] listen paths not being rebuilt correctly   bugzilla-daemon at main.slony.info
• [Slony1-bugs] [Bug 40] libpq thread test insufficient   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 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 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 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 99] unable to set datestyle   bugzilla-daemon at main.slony.info

Last message date: Tue Aug 31 12:55:36 PDT 2010
Archived on: Tue Aug 31 12:55:38 PDT 2010

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

---

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