From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | "Jonathan S(dot) Katz" <jonathan(dot)katz(at)excoventures(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, amul sul <sulamul(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Failed assertion due to procedure created with SECURITY DEFINER option |
Date: | 2018-07-13 08:46:27 |
Message-ID: | 9ffba6b7-2cc4-ac33-0a5d-210f6469d8af@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2018-07-13 09:05:10 | Re: ALTER TABLE on system catalogs |
Previous Message | Fabien COELHO | 2018-07-13 08:46:23 | Re: pgbench's expression parsing & negative numbers |