On Wed, Feb 12, 2014 at 07:17:51AM -0500, Steve Singer wrote: > On Tue, 11 Feb 2014, David Fetter wrote: > > >On Tue, Feb 11, 2014 at 08:46:26PM -0500, Vick Khera wrote: > >>On Sat, Feb 8, 2014 at 12:23 PM, Steve Singer <[email protected]> > >>wrote: > >> > >>>Just add the triggers to your tables as you normally would on all > >>>nodes. > >> > >>Which is to say using slonik to run the SQL script that will add > >>them. > > > >Thanks for clarifying that. It's kinda important :) > > You can add the triggers via slonik EXECUTE SCRIPT, but in most > cases you can also add the triggers to all nodes directly with psql.
In what cases can't I do this? Given our volume, I'm not a huge fan of the size of the lock EXECUTE SCRIPT might take. > With the psql method the triggers get added to all nodes immedately, > even if the node is behind in replication. With a origin only > trigger this shouldn't make a difference. If the trigger does stuff > on replicas then this is more of an issue. The trigger only does stuff on a replica if that replica takes over as origin. Cheers, David. -- David Fetter <[email protected]> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: [email protected] iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate _______________________________________________ Slony1-general mailing list [email protected] http://lists.slony.info/mailman/listinfo/slony1-general
