On 11/29/2005 3:28 PM, Sven Willenberger wrote:
On Tue, 2005-11-29 at 15:09 -0500, Sven Willenberger wrote:
Slony 1.1.2, FreeBSD 6.0, Postgresql 8.0.4
I currently have a table that I am replicating to a subscriber node
containing customer information. I have added a trigger to the
subscriber version of this table to fire after insert that should create
a new table using information from the newly inserted record; this
trigger does not seem to fire.
Does Slony bypass user triggers on the subscriber node's tables? If so,
is there any way to bypass this behavior? If not, any ideas why this
trigger may not be firing?
Sven
_______________________________________________
Please disregard; there were apparently a batch of records that were
being updated rather than inserted (that had already existed prior to
the replication scheme being enabled); further testing with adding new
records reveals that the after update triggers on subscriber nodes in
fact do work.
I apologize for the noise.
I hope that you did not create the trigger in the subscriber database
via direct DDL after Slony-I was installed. On a Slony-I node all DDL
must be run via the slonik command EXECUTE SCRIPT.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== [EMAIL PROTECTED] #
_______________________________________________
Slony1-general mailing list
[email protected]
http://gborg.postgresql.org/mailman/listinfo/slony1-general
