Fri Dec 18 12:00:52 PST 2009
- Previous message: [Slony1-general] logtrigger/denyaccess triggers removed from master/slave
- Next message: [Slony1-general] slony is scanning every table...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
--- On Fri, 12/18/09, tamanna madaan <tamanna.madan at globallogic.com> wrote: >From: tamanna madaan <tamanna.madan at globallogic.com> >Subject: [Slony1-general] logtrigger/denyaccess triggers removed from master/slave >To: slony1-general at lists.slony.info >Cc: "Gaurav Katiyar" <gaurav.katiyar at globallogic.com> >Date: Friday, December 18, 2009, 1:02 PM > >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 The version of slony you are using --> slony-1.1.5 is most probably the cause. It is a very old version. I highly recommend you upgrade to the latest version of 1.2. Melvin Davidson -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20091218/746d5c06/attachment.htm
- Previous message: [Slony1-general] logtrigger/denyaccess triggers removed from master/slave
- Next message: [Slony1-general] slony is scanning every table...
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list