On Wed, Aug 30, 2017 at 5:11 PM, Robert Haas <robertmh...@gmail.com> wrote: > On Wed, Aug 30, 2017 at 6:58 AM, Pavan Deolasee > <pavan.deola...@gmail.com> wrote: >> It's quite possible that I don't understand the differences in "role" and >> "session authorization", but it still looks like a bug to me. May be >> SerializeGUCState() should check if SetRoleIsActive is true and only then >> save the role information? > > Ugh. Well, this is definitely a bug, but I'm not sure if that's the right > fix. >
Yeah. > Mutually interdependent GUCs are bad news. > I am able to reproduce this without involving session authorization guc as well. One needs to drop the newly created role from another session, then also we can see the same error. -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
