Postgres Pro
Downloads
Home   >   mailing lists

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 14665d35-0420-dc6c-bbd4-ce07fcd2189b@2ndquadrant.com
Whole thread Raw
In response to Failed assertion due to procedure created with SECURITY DEFINER option  (amul sul <sulamul@gmail.com>)
Responses Re: Failed assertion due to procedure created with SECURITY DEFINERoption
Re: Failed assertion due to procedure created with SECURITY DEFINER option
List pgsql-hackers
Tree view 
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?

We could work around this for now by prohibiting transaction commands in
security definer procedures, similar to what we do in procedures with
GUC settings attached.

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

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: assert in nested SQL procedure call in current HEAD
Next
From: Peter Eisentraut
Date:
Subject: Re: Tips on committing