Anyone know if it is possible to create an update trigger on the destination 
side of a replicated table in Slony-I and have the replication itself cause the 
trigger to fire? I was able to add the trigger but when run the test 
transaction through, it does not seem to be firing.  It works on the 
non-replicated version of the solution.

Running postgres 8.4.1 and Slony-I 2.0.3


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin

Reply via email to