Well, if I had to guess, that's what I would think. The previous sysadmin created some scripts to manage slony, but I'm not sure that they're working effectively.

Mike

-----Original Message-----
From: Steve Singer [mailto:ssinger at ca.afilias.info] 
Sent: Thursday, October 04, 2012 3:02 PM
To: Mike James
Cc: slony1-general at lists.slony.info
Subject: Re: [Slony1-general] offline log shipping errors

On 12-10-04 02:52 PM, Mike James wrote:
> Hi, our DBA stopped log shipping to create a new replication set. When 
> he resumed log shipping, the next sequence number on the offline node 
> is not consistent with the new log sequence numbers coming from the 
> cluster. This is my 1^st experience using Postgres/Slony and I don't 
> know how to resolve this. I have not found a straightforward 
> resolution of this in Google searches - probably I'm using the wrong keywords.
>

What exactly do you mean by 'stopped log shipping' ?

Do you mean that he shutdown the slon then restarted it without the -a option?

If so I think you will need to rebuild the offline node from scratch with slony1_dump.sh because there is no longer a record of the changes that the slon had processed when it was running without the -a option.




> Please point me in the right direction. Thanks, Mike
>
>
>
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
>