> > Finally, we will need to set the slony triggers to 'fire always' on
> > our master as we have a process in our production environment which
> > turns off all triggers on a regular basis.
> 
> You need to fix that process.  If you go around and thump them, things
> will break.  There's no setting that allows you to say, "Even if someone
> turns you off, fire anyway."

Andrew is right that you need to fix this, but all hope is not lost, as
you may be able to make (careful) use of the new session_replication_role
variable in 8.3 of Postgres and a future version of Slony:

http://www.postgresql.org/docs/8.3/interactive/sql-altertable.html

However, "turning off all triggers on a regular basis" is probably the
wrong solution to your particular problem, and at best will cause serious
locking issues, and may cause database corruption. You might want to post
what you are trying to do on pgsql-general and see if a better solution
can be found.

-- 
Greg Sabino Mullane greg at endpoint.com
End Point Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
Url : http://lists.slony.info/pipermail/slony1-general/attachments/20080530/9d2d9c49/signature-0001.pgp