On Wed, Jun 4, 2025 at 02:29:46PM -0700, Noah Misch wrote:
> I agree with David G. Johnston's feedback on this. My draft didn't mention
> SECURITY DEFINER, because I consider it redundant from a user's perspective.
> If a function is SECURITY DEFINER, that always overrides other sources of user
> identity. No need to mention it each time.
Well, if it is a SECURITY DEFINER function, it is not going to be run as
the user who is active at commit/execution time, so I think we have to
specify that.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
