SLONY DDL errors

Slony version 1.1.2

If executing a slony DDL script that contains a  "DROP TABLE" statement 
fails with errors, and the exact cause is
not immediately known, try executing the DDL commands through a SQL window.

If the DROP commands succeed on the MASTER, but fail on the SLAVE with 
an error similar to
ERROR: "xxxx_pk" is an index

Then the problem is caused by the table being deleted having a 
constraint that refers to the primary key of another
table that is being replicated.

To resolve the problem:
1: Drop any tables from the slony replication set that are referred to 
by the table being DROP'ed.
    ie: SET DROP TABLE ( ORIGIN=nn, ID=xxx); (where nn is the set # and 
xxx is the id of the table):
         
2. After completing the DDL statements, re-add the tables to the 
replication set(s) with MERGE SET.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mdavidson.vcf
Type: text/x-vcard
Size: 300 bytes
Desc: not available
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20060413/8e50beb9/mdavidson.vcf