Hello,

I have a novel requirement; I'd like to fire AFTER triggers on
replicated tables, that don't modify the database, on slaves only.
These triggers just send notifications to client apps that connect to
the slave, which cause them to refresh their view to the table, so the
user doesn't have to refresh it themselves - that is all.

I've noticed that Slony-I disables my AFTER triggers on the slaves
(they actually don't even exist on the master).  While I understand
the rationale in having Slony do this, this is clearly something I can
safely override.

Does what I want seem reasonable? I see that I can ALTER TABLE
my_table ENABLE REPLICA TRIGGER my_trig and get the desired behaviour.
Should I just make a point of doing this after replication has been
setup on all slaves?

I'm using Slony 2.0.2, with Postgres 8.3.5 on the slave and 8.4.1 on the master.

Regards,
Peter Geoghegan