From: | "Plugge, Joe R(dot)" <JRPlugge(at)west(dot)com> |
---|---|
To: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Slony-I - Update trigger on a replicated table |
Date: | 2010-05-13 21:11:55 |
Message-ID: | BD69807DAE0CE44CA00A8338D0FDD08302D2B27515@oma00cexmbx03.corp.westworlds.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Nevermind ... I RTFM ...
echo "alter table mytable ENABLE REPLICA TRIGGER check_lockout;" | psql mydb
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Plugge, Joe R.
Sent: Thursday, May 13, 2010 4:02 PM
To: pgsql-admin(at)postgresql(dot)org
Subject: [ADMIN] Slony-I - Update trigger on a replicated table
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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-05-13 21:19:08 | Re: List traffic |
Previous Message | Marc G. Fournier | 2010-05-13 21:07:43 | Re: List traffic |