On May 18, 2006 08:36 am, Norman Yamada <nyamada at millburncorp.com> wrote:

> Now we're stuck. I can't drop the table from the slony set, because
> it complains that the table doesn't exist on the master node. I've re-
> created the table on the master node to no avail. Worse, while my
> slony set continues to function even without this table, I can't run
> any other DDL scripts on the set -- it complains about the missing
> table.

This should work ...

Assuming the replacement table you created is still there:

Update sl_table.tab_reloid to the replacement table oid, and manually 
recreate the replication trigger on the table (paying attention to the name 
- see your other tables for examples), then you should be able to drop it 
from the set.

-- 
Alan