logtrigger/denyaccess triggers removed from master/slave

From: "tamanna madaan" <tamanna(dot)madan(at)globallogic(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Cc: "Gaurav Katiyar" <gaurav(dot)katiyar(at)globallogic(dot)com>
Subject: logtrigger/denyaccess triggers removed from master/slave
Date: 2009-12-18 18:59:05
Message-ID: 68666423656E1444A011106C4E085F4D96F090@ex3-del1.synapse.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


Hi All

I am using postgres-8.1.2 and slony-1.1.5 for replication.
I have 1 master and 1 slave in my cluster.
Sometimes I see problem of missing logtriggers and denyaccess triggers
on master table and slave tables respectively. Replication don't take place in that
state though systems are properly shown as master and slave.
This problem is resolved by dropping the schema used by slony on both the systems an
then recreating the schema.

I want to know what could be the root cause of logtriggers/denyaccess
triggers getting removed from the tables.

Thanks in advance

Regards
Tamanna

Responses

Browse pgsql-general by date

  From Date Subject
Next Message sabrina miller 2009-12-18 19:00:33 Triggers made with plpythonu performance issue
Previous Message Little, Douglas 2009-12-18 17:27:26 column level encryption & select rules