Thu Aug 17 01:18:55 PDT 2006
- Previous message: [Slony1-general] relation "PartInd_T1_sl_log_2-node-1" already exists
- Next message: [Slony1-general] relation 'PartInd_T1_sl_log_2-node-1' already exists
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> 2006-08-17 07:53:38 UTC ERROR remoteWorkerThread_1: "begin transaction; > set transaction isolation level serializable; lock table > "_T1".sl_config_lock; > select "_T1".storeSet_int(2001, 1, 'aeronautical_extra'); notify > "_T1_Event"; notify "_T1_Confirm"; insert into "_T1".sl_event > (ev_origin, ev_seqno, ev_timestamp, ev_minxid, ev_maxxid, ev_xip, > ev_type , ev_data1, ev_data2, ev_data3 ) values ('1', '16', '2006-08-17 > 07:50:53.779952', '36975500', '36975501', '', 'STORE_SET', '2001', '1', > 'aeronautical_extra'); insert into "_T1".sl_confirm (con_origin, > con_received, con_seqno, con_timestamp) values (1, 2, '16', now()); > commit transaction;" PGRES_FATAL_ERROR ERROR: relation > "PartInd_T1_sl_log_2-node-1" already exists This is a bug in the new partial indexes code. Chris has already fixed that problem in cvs last monday. Can you please test if that fixes the problem for you? - Niels
- Previous message: [Slony1-general] relation "PartInd_T1_sl_log_2-node-1" already exists
- Next message: [Slony1-general] relation 'PartInd_T1_sl_log_2-node-1' already exists
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list