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

--- Comment #2 from Steve Singer <ssinger at ca.afilias.info> 2013-03-21 11:25:08 PDT ---
(In reply to comment #1)
> That error message seems to come from execute script, which tries to find the
> last non-sync event ID. But loading the new slony_funcs.sql doesn't use the
> execute script stuff, so how did this get called?

script_exec_stmts - which loops over all statements in your slonik script (it
has nothing to do with the slony EXECUTE SCRIPT command) calls 
slonik_get_last_event_id(...) which queries sl_event.

I'm debating how to fix this keeping mind scripts like:

node 1 admin conninfo='....'
node 2 admin conninfo='....'

create set(id=99, origin=1);
update functions(id=2);

or 

node 1 admin conninfo='....'
node 2 admin conninfo='....'
try {
 create set(id=99, origin=1);
 update functions(id=2);
}

-- 
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.