Thu Oct 2 08:34:32 PDT 2008
- Previous message: [Slony1-general] Replication between different versions of pgsql
- Next message: [Slony1-general] sanity check for all tables in a set
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Sep 30, 2008 at 02:27:08PM -0500, Mark Keisler wrote: > Someone deleted that table at some point and now I can't move the set > and I can't unsubscribe the set. It didn't seem like I could do > anything at this point besides manually strip out the cluster schema and > start over. So my first question is if there are any other options at > this point? I don't think so. Re-educate your users not to drop things out from under you. No DDL! > Secondly, is there some sort of check that I can run periodically to > make sure a set is still intact so something like this doesn't bite me > right when I need to move a set? You can check the _slony.sl_tables and _slony.sl_sequence tables. A -- Andrew Sullivan ajs at commandprompt.com +1 503 667 4564 x104 http://www.commandprompt.com/
- Previous message: [Slony1-general] Replication between different versions of pgsql
- Next message: [Slony1-general] sanity check for all tables in a set
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list