Great, try to keep the messages on the mailing list.
>________________________________
> From: Riya V <[email protected]>
>To: [email protected]
>Sent: Wednesday, 6 June 2012, 18:12
>Subject: RE: [Slony1-general] creating a new trigger for a table on a slave
>host
>
>
>
>Thanks!
>We are on 1.2 now and planning to move to 2.X
>
>
>Riya
>
>
>
>________________________________
>Date: Wed, 6 Jun 2012 12:19:02 +0100
>From: [email protected]
>Subject: Re: [Slony1-general] creating a new trigger for a table on a slave
>host
>To: [email protected]; [email protected]
>
>
>What version of slony?
>
>
>
>For 1.2 and earlier add the trigger via slonik and use store trigger if you
>want to enable it:
>
>
>http://slony.info/documentation/1.2/stmtstoretrigger.html
>
>
>For 2.0 and later use DISABLE/ENABLE [REPLICA|ALWAYS] TRIGGER in postgresql.
>
>
>
>>________________________________
>> From: Riya V <[email protected]>
>>To: [email protected]
>>Sent: Tuesday, 5 June 2012, 19:27
>>Subject: [Slony1-general] creating a new trigger for a table on a slave host
>>
>>
>>
>>I need to modify my database schema and create a new trigger function. I know
>>that triggers are suppressed on the slave once Slony starts up. However since
>>slony is now already running on the slave, if I create a new trigger there,
>>it will not be suppressed. What is the best practice for creating a trigger
>>on the slave? Should you take the table out of replication, create trigger ,
>>then add the table back in? Is there some other way to do it?
>>Thanks!
>>
>>
>>RV
>>_______________________________________________
>>Slony1-general mailing list
>>[email protected]
>>http://lists.slony.info/mailman/listinfo/slony1-general
>>
>>
>>
>
>
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
