Thanks!

Could I update only the slonik processor to the new version, not touching
all slon processes on other machines (1.2.9)?
Would slonik-1.2.10 conflict with slon-1.2.9 or not in such case?


On 6/5/07, Jan Wieck <JanWieck at yahoo.com> wrote:
>
> On 6/4/2007 7:01 PM, Dmitry Koterov wrote:
> > Hmm, possibly
> >
> > LOCK SET (ID =3D 1, ORIGIN =3D 1);
> > UNLOCK SET (ID =3D 1, ORIGIN =3D 1);
> >
> > would be a better choise? I just want to explicitly wait until all
> > schema changes are finished on all nodes, no more... And I guarantees
> > that there is no reading or writing activity at that moment, I just want
> > to sit and wait...
>
> I just committed the fix for the original problem. Check out the CVS
> branch REL_1_2_STABLE and look at src/ducttape/test_5_... it includes
> tests for SYNC as well as for EXECUTE SCRIPT followed by WAIT FOR EVENT.
> As soon as we have that tested enough we will release 1.2.10 and you
> will have a real solution. Please run your test cases and let us know if
> it fixes your problems. If everything goes well and no more serious bugs
> show up in the next few days, we will have 1.2.10 out this week.
>
>
> Jan
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070605/=
4c75b4a6/attachment-0001.htm