On 8/6/07, Mikko Partio <mpartio at gmail.com> wrote:
>
>
> On 7/29/07, Jan Wieck <JanWieck at yahoo.com> wrote:
> >
> >
> >
> >
> > This one played quite a bit hide and seek with me. But I think I found
> > and fixed the bug.
> >
> > The problem occurred when some action (like STORE_SET) caused the
> > subscriber slon to perform an internal restart. During that, the current
> >
> > setsync tracking in the pset structure is reinitialized. However, since
> > the sl_setsync table is not updated on events other than SYNC, this
> > would lead to the wrong (too low) old sync expected if the last event(s)
> >
> > processed from that node where no SYNC events.
> >
> > Thanks for the detailed example.
>
>
>
> My experiments show me that the problem persists. The test-case is the
> same as in the previous example (started from scratch):
>



Any ideas?

Regards

MP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070810/=
86aced27/attachment.htm