Re: Failed assertion due to procedure created with SECURITY DEFINERoption - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Failed assertion due to procedure created with SECURITY DEFINERoption
Date
Msg-id 20180703172011.shxrsovy6pp5evxa@alap3.anarazel.de
Whole thread Raw
In response to Re: Failed assertion due to procedure created with SECURITY DEFINERoption  (Andres Freund <andres@anarazel.de>)
Responses Re: Failed assertion due to procedure created with SECURITY DEFINERoption  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
On 2018-06-29 10:19:17 -0700, Andres Freund wrote:
> Hi,
> 
> On 2018-06-29 13:56:12 +0200, Peter Eisentraut wrote:
> > On 6/29/18 13:07, amul sul wrote:
> > > This happens because of in fmgr_security_definer() function we are
> > > changing  global variable SecurityRestrictionContext and in the
> > > StartTransaction() insisting it should be zero, which is the problem.
> > 
> > Hmm, what is the reason for this insistation?
> 
> Because it's supposed to be reset by AbortTransaction(), after an error.

Does that make sense Peter?

I've added this thread to the open items list.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Nikhil Sontakke
Date:
Subject: Re: [HACKERS] logical decoding of two-phase transactions
Next
From: Alvaro Herrera
Date:
Subject: Re: Non-reserved replication slots and slot advancing