On Wed, Feb 24, 2010 at 2:00 PM, Joseph S <jks at selectacast.net> wrote:
> If a trigger exists on a table, when slony is installed on a slave it
> removes the original triggers.  However if I want to add a trigger to
> the table (to make sure my master & slave always have the same schema)
> how do I get slony to move it to where it hid the original triggers?
> This trigger firing on INSERT on the slave can actually cause data
> corruption.

ALL change to the db schema are to be run thru slony's EXECUTE SCRIPT
function, which will take care of ensuring that the schema change is
applied properly to all copies, and that slony knows about those
changes so it can properly replicate your data (especially important
when adding/removing columns, adding/removing foreign keys, etc.)