http://www.slony.info/bugzilla/show_bug.cgi?id=218

--- Comment #1 from Steve Singer <ssinger at ca.afilias.info> 2011-06-08 08:46:13 PDT ---
The following is an example from the postgresql query log that shows the issue.


slon.remoteWorkerThread_3 slonyregress1 4def9413.2f41 0LOG:  statement: begin
transaction; set transaction isolation level serializable; 

slon.remoteWorkerThread_3 slonyregress1 4def9413.2f41 0LOG:  statement: select
"_slonyregress".storePath_int(1, 3, 'dbname=slonyregress1 host=localhost
port=9432 user=slony password=test', 10); insert into "_slonyregress".sl_event 
   (ev_origin, ev_seqno, ev_timestamp,      ev_snapshot, ev_type , ev_data1,
ev_data2, ev_data3, ev_data4    ) values ('3', '5000000001', '2011-06-08
11:24:03.10834-04', '43245:43245:', 'STORE_PATH', '1', '3',
'dbname=slonyregress1 host=localhost port=9432 user=slony password=test',
'10'); insert into "_slonyregress".sl_confirm       (con_origin, con_received,
con_seqno, con_timestamp)    values (3, 1, '5000000001', now()); commit
transaction;

slon.remoteWorkerThread_2 slonyregress1 4def9413.2f3e 0LOG:  statement: begin
transaction; set transaction isolation level serializable; 

slon.remoteWorkerThread_2 slonyregress1 4def9413.2f3e 0LOG:  statement: select
"_slonyregress".storePath_int(1, 2, 'dbname=slonyregress1 host=localhost
port=9432 user=slony password=test', 10); insert into "_slonyregress".sl_event 
   (ev_origin, ev_seqno, ev_timestamp,      ev_snapshot, ev_type , ev_data1,
ev_data2, ev_data3, ev_data4    ) values ('2', '5000000001', '2011-06-08
11:24:03.018181-04', '43243:43243:', 'STORE_PATH', '1', '2',
'dbname=slonyregress1 host=localhost port=9432 user=slony password=test',
'10'); insert into "_slonyregress".sl_confirm      (con_origin, con_received,
con_seqno, con_timestamp)    values (2, 1, '5000000001', now()); commit
transaction;


slon.remoteWorkerThread_2 slonyregress1 4def9413.2f3e 43258ERROR:  could not
serialize access due to read/write dependencies among transactions
slon.remoteWorkerThread_2 slonyregress1 4def9413.2f3e 43258DETAIL:  Cancelled
on conflict out to pivot 43254, during read.
slon.remoteWorkerThread_2 slonyregress1 4def9413.2f3e 43258HINT:  The
transaction might succeed if retried.
slon.remoteWorkerThread_2 slonyregress1 4def9413.2f3e 43258CONTEXT:  SQL
statement "delete from "_slonyregress".sl_listen"
slon.remoteWorkerThread_2 slonyregress1 4def9413.2f3e 43258STATEMENT:  select
"_slonyregress".storePath_int(1, 2, 'dbname=slonyregress1 host=localhost
port=9432 user=slony password=test', 10); insert into "_slonyregress".sl_event 
   (ev_origin, ev_seqno, ev_timestamp,      ev_snapshot, ev_type , ev_data1,
ev_data2, ev_data3, ev_data4    ) values ('2', '5000000001', '2011-06-08
11:24:03.018181-04', '43243:43243:', 'STORE_PATH', '1', '2',
'dbname=slonyregress1 host=localhost port=9432 user=slony password=test',
'10'); insert into "_slonyregress".sl_confirm       (con_origin, con_received,
con_seqno, con_timestamp)    values (2, 1, '5000000001', now()); commit
transaction;
slon.remoteWorkerThread_3 slonyregress1 4def9413.2f41 0LOG:  statement: select
li_origin, li_provider from "_slonyregress".sl_listen where li_receiver = 1


I am not sure why the lock table 'sl_config_lock' at the top of storePath_int
isn't stopping this.

-- 
Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.