Sat Aug 11 12:40:31 PDT 2007
- Previous message: [Slony1-general] cannot drop tables from schema after dropping tables from replication
- Next message: [Slony1-general] cannot drop tables from schema after dropping tables from replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 8/10/07, Richard Yen <dba at richyen.com> wrote: > > Not sure if this is enough detail, or if anyone would have any idea > why this happens. Again, I can successfully DROP TABLE from the > origin, but I cannot do so from the subscribers. Therefore, I > suspect that Slony has put my subscriber nodes in a strange state. You have to remove the table from replication first (see slonik and "set drop table") before you can physically drop it. This is because Slony alters the pgsql system catalog at the subscriber node. Regards MP -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20070811/= d8b7635a/attachment.htm
- Previous message: [Slony1-general] cannot drop tables from schema after dropping tables from replication
- Next message: [Slony1-general] cannot drop tables from schema after dropping tables from replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list