Thu Sep 2 11:56:24 PDT 2010
- Previous message: [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state
- Next message: [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
http://www.slony.info/bugzilla/show_bug.cgi?id=128 --- Comment #6 from Jan Wieck <janwieck at yahoo.com> 2010-09-02 11:56:24 PDT --- Here is a different attempt. It simply downgrades the RAISE in alterTableDropTriggers() and alterTableConfigureTriggers() from EXCEPTION to NOTICE, if the underlying table isn't found. There is however more outstanding in this case. If a replicated table is dropped on a subscriber, then incoming replication data for updates to that table will probably cause the SYNC to fail. I still need to test that case. -- Configure bugmail: http://www.slony.info/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
- Previous message: [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state
- Next message: [Slony1-bugs] [Bug 128] DROP TABLE replicatedTable leaves the cluster in a bad state
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-bugs mailing list