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

From Peter Eisentraut
Subject Re: Failed assertion due to procedure created with SECURITY DEFINERoption
Date
Msg-id 72ba1903-4c79-653d-432c-8139137b773d@2ndquadrant.com
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  ("Jonathan S. Katz" <jonathan.katz@excoventures.com>)
List pgsql-hackers
On 03.07.18 19:20, Andres Freund wrote:
> 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.

Proposed fix attached.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment

pgsql-hackers by date:

Previous
From: "Ideriha, Takeshi"
Date:
Subject: RE: Global shared meta cache
Next
From: Peter Eisentraut
Date:
Subject: Re: Test-cases for deferred constraints in plpgsql_transaction.sql