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 9ffba6b7-2cc4-ac33-0a5d-210f6469d8af@2ndquadrant.com
Whole thread Raw
In response to Re: Failed assertion due to procedure created with SECURITY DEFINERoption  ("Jonathan S. Katz" <jonathan.katz@excoventures.com>)
List pgsql-hackers
On 12.07.18 21:52, Jonathan S. Katz wrote:
> So it handles it as expected.

Committed.

> Code and test cases look fine to me from what I can tell. My only suggestion
> would be if we could add some guidance to the documentation on what
> languages
> can support transaction control statements inside procedures with a SECURITY
> DEFINER.

The documentation change is in the CREATE PROCEDURE ref page, since it's
independent of any language.

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


pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: pgbench's expression parsing & negative numbers
Next
From: Peter Eisentraut
Date:
Subject: Re: ALTER TABLE on system catalogs