From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
cc: Noah Misch <noah@leadboat.com>, Bruce Momjian <bruce@momjian.us>,
        PostgreSQL-development <pgsql-hackers@lists.postgresql.org>
Subject: Re: PG 18 release notes draft committed
In-reply-to: 
 <CAKFQuwa6rVaMDp5+hLbAMEefV-qP=8oCbsgiGnh4xPkQ=nu-wQ@mail.gmail.com>
References: <aBQxop9YxQDad8-W@momjian.us>
 <20250603172123.5f.nmisch@google.com> <aECwXlB15awOXivC@momjian.us>
 <CAKFQuwYhd6-fSM-inS9RnB5WydVpzj471-YNgU7CiVZ7WWi3ow@mail.gmail.com>
 <aEDAE0590fqvU0Ud@momjian.us> <1071973.1749075038@sss.pgh.pa.us>
 <20250604221710.2c.nmisch@google.com>
 <CAKFQuwa6rVaMDp5+hLbAMEefV-qP=8oCbsgiGnh4xPkQ=nu-wQ@mail.gmail.com>
Comments: In-reply-to "David G. Johnston" <david.g.johnston@gmail.com>
	message dated "Wed, 04 Jun 2025 15:25:54 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1075843.1749076677.1@sss.pgh.pa.us>
Date: Wed, 04 Jun 2025 18:37:57 -0400
Message-ID: <1075844.1749076677@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1075844.1749076677%40sss.pgh.pa.us>
Precedence: bulk

"David G. Johnston" <david.g.johnston@gmail.com> 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