Hey,

Recently, unknowingly, we dropped a table on the master db which was a 
part of Slony replication without it going through the Slony script. 
This table is however present on the mirror/replicated db. I read 
somewhere, and want to confirm if the following hack will work.

Dropped table name : foo
tab_id in sl_table : 20

* Create a new table named "foo" with the same schema as the original 
dropped table
* Add trigger on the master table with name "_mirror_logtrigger_20"(as 
created on other replicated tables)
* Update sl_table with the new oid.
* All done, now drop the table via the slop drop script?

Thanks for help in advance


--
Anooj Narvekar