Thu Aug 30 08:47:41 PDT 2012
- Previous message: [Slony1-bugs] [Bug 276] local_listen can not restart on PostgreSQL 8.3+.
- 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 --- Comment #2 from Christopher Browne <cbbrowne at ca.afilias.info> 2012-08-30 08:47:41 PDT --- Looking good. I ran slon "without" the patch, getting the "key already exists" [and I haven't any good explanation for this], which is poor behaviour. I then ran it with the patch, and got the more desirable message: DETAIL: Key (nl_nodeid, nl_conncnt)=(2, 0) already exists. FATAL Do you already have a slon running against this node? FATAL Or perhaps a residual idle backend connection from a dead slon? So that looks pretty good, and the patch nicely reduces the dependency on the exact form of error string text. -- 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.
- Previous message: [Slony1-bugs] [Bug 276] local_listen can not restart on PostgreSQL 8.3+.
- 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