Mon May 22 07:41:18 PDT 2017
- Previous message: [Slony1-general] Wrongly configured trigger when upgrading slony from 2.0.7 to 2.2.5
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, May 20, 2017 at 5:24 AM, Soni M <diptatapa at gmail.com> wrote: > The upgrade went well, except it configure the trigger wrong. > > On master, It has triggers : logtrigger, truncatedeny, and truncatetrigger > disabled trigger : denyaccess > > On slave, It has triggers : denyaccess, truncatedeny, and truncatetrigger > disabled trigger : logtrigger > How were the triggers configured before the upgrade? Why do you think these are wrong? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20170522/f4afa20f/attachment.htm
- Previous message: [Slony1-general] Wrongly configured trigger when upgrading slony from 2.0.7 to 2.2.5
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list