We ran across a problem where we wanted to delete a column in a table  
and didn't recognize that that column was used as a unique key index  
(nonprimary) by slony.

We did the "best practice" of testing it inside a BEGIN-ROLLBACK to  
make sure that it would go and then pushed it through  
slonik_execute_script and the effect was that all the slony triggers  
got dropped on the master.

We won't make that mistake again.

I guess this is impossible to easily detect and refuse to perform as  
you can't put triggers on "alter table" but could it maybe be made to  
still restore the triggers?

Just a thought...

Karl