Wed Mar 31 07:38:13 PDT 2010
- Previous message: [Slony1-bugs] [Bug 55] Possible buffer overflow in slon, still happens as of 1.2.14
- Next message: [Slony1-bugs] [Bug 81] duplicate key sl_nodelock-pkey and duplicate slon(8) processes not detected
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=81 --- Comment #3 from Steve Singer <ssinger at ca.afilias.info> 2010-03-31 07:38:13 PDT --- (In reply to comment #2) > Is there anything that I can help you to debug this issue? Can you clarify what your seeing. If I start up on the same postgresql cluster 1) 1 slon on my origin database 2) 1 slon on my receiver database 3) A second slon on my receiver database The third slon gives me ---------------------------------------------- 2010-03-31 10:31:44 EDTFATAL localListenThread: "select "_test".cleanupNodelock(); insert into "_test".sl_nodelock values ( 2, 0, "pg_catalog".pg_backend_pid()); " - ERROR: duplicate key value violates unique constraint "sl_nodelock-pkey" 2010-03-31 10:31:44 EDTINFO slon: shutdown requested 2010-03-31 10:31:44 EDTINFO slon: notify worker process to shutdown 2010-03-31 10:32:04 EDTINFO slon: child termination timeout - kill child 2010-03-31 10:32:04 EDTCONFIG slon: child terminated status: 9; pid: 5071, current worker pid: 5071 2010-03-31 10:32:04 EDTINFO slon: done 2010-03-31 10:32:04 EDTINFO slon: exit(0) ----------------------------------------------------------- and exits. Isn't this the behavior one would expect, or are you seeing something else? -- 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.
- Previous message: [Slony1-bugs] [Bug 55] Possible buffer overflow in slon, still happens as of 1.2.14
- Next message: [Slony1-bugs] [Bug 81] duplicate key sl_nodelock-pkey and duplicate slon(8) processes not detected
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list