public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tom Lane <[email protected]>
To: David G. Johnston <[email protected]>
Cc: Noah Misch <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: PG 18 release notes draft committed
Date: Wed, 04 Jun 2025 18:37:57 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKFQuwa6rVaMDp5+hLbAMEefV-qP=8oCbsgiGnh4xPkQ=nu-wQ@mail.gmail.com>
References: <[email protected]>
<[email protected]>
<[email protected]>
<CAKFQuwYhd6-fSM-inS9RnB5WydVpzj471-YNgU7CiVZ7WWi3ow@mail.gmail.com>
<[email protected]>
<[email protected]>
<[email protected]>
<CAKFQuwa6rVaMDp5+hLbAMEefV-qP=8oCbsgiGnh4xPkQ=nu-wQ@mail.gmail.com>
"David G. Johnston" <[email protected]> writes:
> Is this covering the case of executing at the end of an outer SQL command
> (thus not deferred) that contains volatile DML functions that temporarily
> change current_user within the function?
Not quite. I think that a non-deferred AFTER trigger would ordinarily
run as the same user that was active when we queued the event, earlier
in the same statement --- but it's possible that some function that
runs in between would change the active role in a non-temporary way.
Doing that will now have different effects than it did before.
regards, tom lane
view thread (147+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: PG 18 release notes draft committed
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox