Thu Aug 30 00:38:32 PDT 2012
- Previous message: [Slony1-bugs] [Bug 81] duplicate key sl_nodelock-pkey and duplicate slon(8) processes not detected
- Next message: [Slony1-bugs] [Bug 276] local_listen can not restart on PostgreSQL 8.3+.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=276 Summary: local_listen can not restart on PostgreSQL 8.3+. Product: Slony-I Version: 2.0 Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: low Component: slon AssignedTo: slony1-bugs at lists.slony.info ReportedBy: saitoh_hidenori_b1 at lab.ntt.co.jp CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 local_listen checks return message to detect duplicated slon starts. and if both messages are same, slon_restart indefinitely. in local_listen.c, bellow message is defined. ERROR: duplicate key violates unique constraint \"sl_nodelock-pkey\" but, after PostgreSQL 8.3 returns another message(added "value"). ERROR: duplicate key value violates unique constraint "sl_nodelock-pkey" because of this change, local_listen can not restart(aborted). manual says Slony-I 2.0 supports only PostgreSQL 8.3+. I think it's degrade problem. to fix it, I think it's reasonable to use "PostgreSQL Error Codes". http://www.postgresql.org/docs/9.1/static/errcodes-appendix.html Error Code : 23505 Condition Name : unique_violation -- 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 81] duplicate key sl_nodelock-pkey and duplicate slon(8) processes not detected
- Next message: [Slony1-bugs] [Bug 276] local_listen can not restart on PostgreSQL 8.3+.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list