Found the issue, slony cannot be upgraded directly from 2.0.7 to 2.2.5. It needs to be upgraded to 2.1.4 first and then upgraded again to 2.2.5. It configured the trigger correctly.
On Mon, May 22, 2017 at 9:41 PM, Vick Khera <vi...@khera.org> wrote: > > On Sat, May 20, 2017 at 5:24 AM, Soni M <diptat...@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? > > > _______________________________________________ > Slony1-general mailing list > Slony1-general@lists.slony.info > http://lists.slony.info/mailman/listinfo/slony1-general > > -- Regards, Soni Maula Harriz
_______________________________________________ Slony1-general mailing list Slony1-general@lists.slony.info http://lists.slony.info/mailman/listinfo/slony1-general
