On 7/29/07, Jan Wieck <JanWieck at yahoo.com> wrote:
>
> On 7/24/2007 12:29 AM, Mikko Partio wrote:
> >
> >     What I meant is that it'd be good to get enough detail information
> about
> >     the specific actions that lead to this problem in order to create a
> >     standalone test that can reproduce it.
> >
> >
> > Ok here comes:
>
> 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.
>


Great that you got it fixed! Will the patch be included in the 1.2.11releas=
e?

Regards

MP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070801/=
b1cbcf48/attachment-0001.htm