Thu Oct 4 11:52:28 PDT 2012
- Previous message: [Slony1-general] pg_reorg and reorganizing tables in slony cluster
- Next message: [Slony1-general] offline log shipping errors
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 1st 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. Please point me in the right direction. Thanks, Mike -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20121004/7bbe681b/attachment.htm
- Previous message: [Slony1-general] pg_reorg and reorganizing tables in slony cluster
- Next message: [Slony1-general] offline log shipping errors
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list