On 7/23/2007 2:27 AM, Mikko Partio wrote:
> 
> 
> On 7/20/07, *Mikko Partio* <mpartio at gmail.com 
> <mailto:mpartio at gmail.com>> wrote:
> 
>     Hello all,
> 
>     as mentioned in an another thread I have started a log shipping
>     scenario where there's an origin, a slave and a log shipping slave.
>     The setup went smoothly and everything worked when the logs produced
>     by the normal subscriber were applied to the log shipping slave. The
>     problem is that inevitably the replication to the log shipping slave
>     stops. The reason is that the syncs in the logfiles have gaps:
> 
>     To my eye it seems that file 524 is trying to advance the sync
>     number from 521 to 524, while it has already been incremented to 523
>     in the previous file. Why does the 524 file try to advance the sync
>     number in such a way? 
> 
> 
> 
> The problem only surfaces when I modify the replication sets, in normal 
> replication everything works like a charm. The 1.2.10 release notes say that

Modify the replication sets exactly how?


Jan

> 
> Fix archive log ship tracking. Slon now tracks the setsync status in 
> memory and generates a void archive with the correct old,new event seqno 
> for all events.
> 
> but apparently the problem still exists. If I manually change the 
> sequence numbers in the archive files everything goes ok, but I wish 
> that slon would create the correct numbers by itself.
> 
> Regards
> 
> MP
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #