Wed Jun 6 04:19:02 PDT 2012
- Previous message: [Slony1-general] creating a new trigger for a table on a slave host
- Next message: [Slony1-general] slony.info website outage
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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 <riyav at hotmail.com> >To: slony1-general at lists.slony.info >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 >Slony1-general at lists.slony.info >http://lists.slony.info/mailman/listinfo/slony1-general > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20120606/15772264/attachment.html
- Previous message: [Slony1-general] creating a new trigger for a table on a slave host
- Next message: [Slony1-general] slony.info website outage
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list