Hello.

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.
I ran a long ALTER TABLE statement (about 3 minutes), master updated
immediately after I had seen PGRES_TUPLES_OK, but slave - 10 or more minutes
later.

So, the questions are:

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?

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:

cluster name =3D my_cluster;
 node 1 admin conninfo=3D'host=3Dhost1 dbname=3Dm user=3Dslony port=3D5432
password=3D**';
 node 2 admin conninfo=3D'host=3Dhost2 dbname=3Dm user=3Dslony port=3D5432
password=3D**';
 node 3 admin conninfo=3D'host=3Dhost3 dbname=3Dm user=3Dslony port=3D5432
password=3D**';
 ...
  execute script (
    set id =3D 1,
    filename =3D '/tmp/e0H7Aa03Fh',
    event node =3D 1
  );

But if a schema changes are propogated via events, theoretically we have to
know only master's address...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070601/=
e9b1a676/attachment.htm