Fri Jun 1 10:21:58 PDT 2007
- Previous message: [Slony1-general] Does slonik EXECUTE SCRIPT call waits for comands termination?
- Next message: [Slony1-general] Does slonik EXECUTE SCRIPT call waits for comands termination?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6/1/07, Jan Wieck <JanWieck at yahoo.com> wrote: > On 6/1/2007 10:52 AM, Dmitry Koterov wrote: > > I also tried to use > > > > try { > > ... > > } on success { > > WAIT FOR EVENT ( > > ORIGIN = ALL, > > CONFIRMED = ALL, > > WAIT ON = 1 > > ) > > } > > Looking at the code, it seems that EXECUTE SCRIPT doesn't actually > record the events seqno in the admin conninfo. Which means that WAIT FOR > EVENT will wait for an earlier event, or even nothing. Unfortunately the > same is true for SYNC in 1.2.9. Hmmm, I'm looking at slonik.c under slonik_ddl_script() and I see (starting at line 3706) slon_mkquery(&query, "select \"_%s\".ddlScript_prepare(%d, %d); ", stmt->hdr.script->clustername, stmt->ddl_setid, /* dstring_data(&script), */ stmt->only_on_node); if (db_exec_evcommand((SlonikStmt *) stmt, adminfo1, &query) < 0) So, it looks like it's recording the event's seqno in the admin conninfo. What am I missing? Andrew
- Previous message: [Slony1-general] Does slonik EXECUTE SCRIPT call waits for comands termination?
- Next message: [Slony1-general] Does slonik EXECUTE SCRIPT call waits for comands termination?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list