Follow-up question...

Base on this comment:

" The Right Way to handle such triggers is normally to use STORE
TRIGGER, which tells Slony-I that a trigger should not get deactivated."

Does this mean that I can't put a 'create trigger' statement in an sql
file passed to slonik and expect it to work properly? (on the master
node)

I now have a subscriber node that I need to add 5 triggers to (tied to 5
different tables)....they already exist in the master node.  How should
I do this?



-----Original Message-----
From: Jeff Amiel 
Sent: Wednesday, October 01, 2008 1:08 PM
To: slony1-general at lists.slony.info
Subject: subscriber question

I'm about to attempt to do some DR testing...and my goal was to take one
of my subscriber nodes, dump it, load it in another instance and point
my DR app server at it and watch the magic happen.

However...I got a little scared after reading this:

http://www.slony.info/documentation/faq.html#AEN6553

(specifically related to my own table triggers)

Let's assume my origin is 'gone' (destroyed in a nuclear burst)....I
have no way to 'dump' the subscriber node?  

In my case I 'may' have hand-added triggers to the subscriber node (as
well as origin) at one point without using slonik execute_script.....

That makes this harder, I assume...

Any advice?

Jeff