Skip site navigation (1) Skip section navigation (2)

Re: Slony-I - Update trigger on a replicated table

From: chirag(dot)dave(at)gmail(dot)com
To: "Plugge, Joe R(dot)" <JRPlugge(at)west(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Slony-I - Update trigger on a replicated table
Date: 2010-05-13 21:47:21
Message-ID: AANLkTiknzbyo3f1WO2yMRmeuxNGY5rY5nFnIzIvYtDEM@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-admin
On Thu, May 13, 2010 at 5:11 PM, Plugge, Joe R. <JRPlugge(at)west(dot)com> wrote:

> Nevermind ... I RTFM ...
>
> echo "alter table mytable ENABLE REPLICA TRIGGER check_lockout;" | psql
> mydb
>

This is not good idea. Always run DDL script using Slony execute script.

http://www.slony.info/documentation/ddlchanges.html



>
> -----Original Message-----
> From: pgsql-admin-owner(at)postgresql(dot)org [mailto:
> pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Plugge, Joe R.
> Sent: Thursday, May 13, 2010 4:02 PM
> To: pgsql-admin(at)postgresql(dot)org
> Subject: [ADMIN] Slony-I - Update trigger on a replicated table
>
> Anyone know if it is possible to create an update trigger on the
> destination side of a replicated table in Slony-I and have the replication
> itself cause the trigger to fire? I was able to add the trigger but when run
> the test transaction through, it does not seem to be firing.  It works on
> the non-replicated version of the solution.
>
> Running postgres 8.4.1 and Slony-I 2.0.3
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>

In response to

pgsql-admin by date

Next:From: Marc G. FournierDate: 2010-05-13 22:13:30
Subject: Re: List traffic
Previous:From: Dimitri FontaineDate: 2010-05-13 21:29:10
Subject: Re: List traffic

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group