Thu Oct 4 12:02:09 PDT 2012
- Previous message: [Slony1-general] offline log shipping errors
- Next message: [Slony1-general] offline log shipping errors
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 >
- Previous message: [Slony1-general] offline log shipping errors
- Next message: [Slony1-general] offline log shipping errors
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list