June 2010 Archives by subject
- Messages sorted by: [ thread ] [ author ] [ date ]
- More info on this list...
Starting: Tue Jun 1 05:58:38 PDT 2010
Ending: Wed Jun 30 07:05:33 PDT 2010
Messages: 78
- [Slony1-bugs] [Bug 104] slon core in sched_add_fdset 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 104] slon core in sched_add_fdset Jan Wieck
- [Slony1-bugs] [Bug 104] slon core in sched_add_fdset 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 105] too much columns in INSERT 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 111] node -1 not found in runtime configuration 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 118] initial copy of an inherited table can leave the table empty 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 120] store path - after slon has started does not take effect 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 123] Adding a node shortly after deleting it causes 'node -1 not found' 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 127] sync events are not generated on nodes that are not a set origin 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 128] DROP TABLE replicatedTable leaves the cluster in a bad state bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 129] FAILOVER command does not update sl_subscriber bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 12] Add tests to test_slony_state scripts 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 130] failover does not seem to update sl_set 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 130] failover does not seem to update sl_set bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 130] New: failover does not seem to update sl_set Jan Wieck
- [Slony1-bugs] [Bug 132] ERROR: duplicate key value violates unique constraint "sl_nodelock-pkey" bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 132] New: ERROR: duplicate key value violates unique constraint "sl_nodelock-pkey" bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 133] DROP set in the middle of a subscribe to the same set confuses slon bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 133] New: DROP set in the middle of a subscribe to the same set confuses slon bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 134] New: TRUNCATE support bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 134] TRUNCATE support bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 134] TRUNCATE support bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 134] TRUNCATE support bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 135] New: slon can get stuck waiting for a sl_config_lock it already has 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 136] listen paths not being rebuilt correctly 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 136] New: listen paths not being rebuilt correctly bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 137] New: excute script does not get applied in the correct order bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 138] New: groff detection in configure broken bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 14] Pull lexer from psql 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 18] Patch to shorten "attkind" on logtrigger functions bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 32] Once every two to three months Slony fails to commit confirms 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 41] Links to stored procedures prefixed with 'schemadoc' everywhere bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 43] get_set() is used inconsistently in altperl tools bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 43] get_set() is used inconsistently in altperl tools bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 47] EXECUTE SCRIPT runs on ALL nodes bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 52] Slon periodically leaks memory bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 56] store trigger runs against all nodes upon subscription bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 58] launch_clusters.sh in 1.2.15 reports an error in bash 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 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 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 67] Array overrun in logtrigger() bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 69] Upgrade from 1.2 to 2.0 didn't work... bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 69] Upgrade from 1.2 to 2.0 didn't work... 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 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 79] --prefix and --exec-prefix options don't function as expected 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 92] Events and Confirmations are not propagating bugzilla-daemon at main.slony.info
- [Slony1-bugs] [Bug 99] unable to set datestyle bugzilla-daemon at main.slony.info
- [Slony1-bugs] delete "logswitch_weekly()" from Slony-I 2.0.x document TAKATSUKA Haruka
Last message date:
Wed Jun 30 07:05:33 PDT 2010
Archived on: Wed Jun 30 07:05:33 PDT 2010
- Messages sorted by: [ thread ] [ author ] [ date ]
- More info on this list...
This archive was generated by Pipermail 0.09 (Mailman edition).