Tue Feb 19 12:25:56 PST 2008
- Previous message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Next message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
cbbrowne at ca.afilias.info wrote: > The more you describe this, the more this is sounding like a case where > the databases may have (somehow?) gotten corrupted. > > It is not self-evident whether it is the origin or subscribers or both > that have gotten corrupted. > > If that is the case, then it is not evident that there is any problem with > Slony-I in this. This isn't something Slony-I should have caused, and, > alas, it is not something it can necessarily protect you from. Notably, > if both DBs have been corrupted, all bets are off altogether. > > I think you need to look into your backups :-(. And fortunately we have those. I'm assuming that triggers on my replication database would be disabled by slony. Is this correct? -- Until later, Geoffrey Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. - Benjamin Franklin
- Previous message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Next message: [Slony1-general] proper procedure for re-starting slony after replication slave reboots
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list