Fri Dec 18 11:32:25 PST 2009
- Previous message: [Slony1-general] logtrigger/denyaccess triggers removed from master/slave
- Next message: [Slony1-general] logtrigger/denyaccess triggers removed from master/slave
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Dec 18, 2009 at 2:02 PM, tamanna madaan <tamanna.madan at globallogic.com> wrote: > I want to know what could be the root cause of logtriggers/denyaccess > triggers getting removed from the tables. > Do you do any schema changes to your database? If you do not tell slony about them, it will break in strange ways like this. General rule: always do your DDL changes via EXECUTE SCRIPT slonik command.
- Previous message: [Slony1-general] logtrigger/denyaccess triggers removed from master/slave
- Next message: [Slony1-general] logtrigger/denyaccess triggers removed from master/slave
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list