Seems WAIT FOR EVENT doesn't help:

echo "
  cluster name =3D my_cluster;
  node 1 admin conninfo=3D'host=3D...'
  node 2 admin conninfo=3D'host=3D...'
  ...
  execute script (
    set id =3D 1,
    filename =3D '/tmp/1kLLzqFEAd',
    event node =3D 1
  );
  WAIT FOR EVENT (
    ORIGIN =3D ALL,
    CONFIRMED =3D ALL,
    WAIT ON =3D 1
  );
" | slonik

This piece of core does not force slonik to wait until all nodes are
updated.
Is there another solution (or any corrections)?

On 6/1/07, Andrew Sullivan <ajs at crankycanuck.ca> wrote:
>
> On Fri, Jun 01, 2007 at 01:41:44PM +0400, Dmitry Koterov wrote:
> > Seems when I use EXECUTE
> > SCRIPT<http://slony.info/documentation/stmtddlscript.html>and slonik
> > reports PGRES_TUPLES_OK updates may NOT be finished yet on all
> > slaves.
>
> Right.  If that weren't the case, we wouldn't have WAIT FOR EVENT.
>
> > 1. THE MAIN question: is it possible to ask slonik to wait untill all
> scheme
> > changes were propogated to all slaves after a slonik call?
>
> See above, and http://slony.info/documentation/stmtwaitevent.html
>
> > 2. If slonik updates slaves not immediately, but via event creation, why
> > does it still need to know an information about ALL database hosts, not
> only
> > about the master database? I have to enumerate all slave hosts in slonik
> > calls:
>
> You need this information for some cases, and unfortunately that just
> means that we require it for all cases.  Slonik is indeed a little
> clunky that way.  It wasn't really intended to be the last word in
> administration interface for Slony-I.
>
> A
>
> --
> Andrew Sullivan  | ajs at crankycanuck.ca
> This work was visionary and imaginative, and goes to show that visionary
> and imaginative work need not end up well.
>                 --Dennis Ritchie
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070601/=
7cb4c061/attachment.htm