Thu Sep 17 23:46:51 PDT 2009
- Previous message: [Slony1-bugs] [Bug 55] Possible buffer overflow in slon, still happens as of 1.2.14
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=95 Summary: Calls to subscribeSet_int are incorrect in Slonik src Product: Slony-I Version: devel Platform: PC OS/Version: Linux Status: NEW Severity: critical Priority: high Component: slonik AssignedTo: slony1-bugs at lists.slony.info ReportedBy: matthew.figg at accenture.com CC: slony1-bugs at lists.slony.info Estimated Hours: 0.0 We are using slony1-2.0.3-rc2 with the following node setup: Node 1: Provider of Set 1 Node 2: Subscriber to Set 1 Node 3: A new node about to be added to the cluster with STORE NODE There are two calls to the postgres function subscribeSet_int(integer, integer, integer, boolean, boolean) in slony1-engine/src/slonik/slonik.c Both calls do not pass in the last boolean input (the new OMIT COPY parameter) and hence you get errors. We have only seen it when using slonik_store_node but looking at the code it could also happen in slonik_failed_node. We are running the following slonik script: cluster name = test_cluster; node 1 admin conninfo = '<db connect string omitted>'; node 2 admin conninfo = '<db connect string omitted>'; node 3 admin conninfo = '<db connect string omitted>'; store node ( id = 3, comment = 'Node 3', event node = 1 ); Output from slonik is: init_slave.ik:5: PGRES_FATAL_ERROR select "_test_cluster".subscribeSet_int(1, 1, 2, 't'); select "_test_cluster".enableSubscription_int(1, 1, 2); - ERROR: function _test_cluster.subscribeset_int(integer, integer, integer, unknown) does not exist LINE 1: select "_test_cluster".subscribeSet_int(1, 1, 2, 't'); selec... ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts. -- 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
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list