Sun Dec 9 17:31:23 PST 2007
- Previous message: [Slony1-general] Delayed replication: Explicitly creating a slony-I backlog, and then telling the slon daemon to replicate changes all at once.
- Next message: [Slony1-general] postgres version upgrade question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
So I messed up and I was wondering if you could help bail me out... I dropped a bunch of foreign key constraints from tables in the master database without using the EXECUTE SCRIPT command. I didn't realize that that kind of DDL change which didn't change the shape of the tables couldn't be done on each node independently. After reading the documentation more carefully, I see that I made a mistake. At this point, what are my options for recovering the state of the cluster? If I try to delete the foreign keys in the slave db, I get errors like ERROR: "users_pkey" is an index. Any suggestions? Thanks in advance for whatever help you can offer. ---Marc ____________________________________________________________________________________ Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20071209/174b5494/attachment.htm
- Previous message: [Slony1-general] Delayed replication: Explicitly creating a slony-I backlog, and then telling the slon daemon to replicate changes all at once.
- Next message: [Slony1-general] postgres version upgrade question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list