Re: Wrong security context for deferred triggers?

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Noah Misch <noah@leadboat.com>

Cc: Laurenz Albe <laurenz.albe@cybertec.at>, Tom Lane <tgl@sss.pgh.pa.us>, Pavel Stehule <pavel.stehule@gmail.com>, pgsql-hackers@lists.postgresql.org

Date: 2025-06-05T05:07:44Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Doc: improve description of which role runs a trigger.
- c37be39a74b2 18.0 landed
Change role names used in trigger test.
- 4b05ebf0957b 18.0 landed
Ensure that AFTER triggers run as the instigating user.
- 01463e1cccd3 18.0 landed
Reverse the search order in afterTriggerAddEvent().
- 7921927bbb9d 18.0 landed

On Tue, Apr 15, 2025 at 08:58:50AM -0700, Noah Misch wrote:
> commit 01463e1 wrote:
>> +NOTICE:  I am regress_groot

Ahah.  Excellent.

> Let's not incur trivially-avoidable trademark risks
> (https://google.com/search?q=%22i+am+groot%22) in the source tree.

But you may be right that it could be a problem, and that's just a
matter of applying a s/regress_groot/regress_dt_user/ or something
equivalent, so let's do the change.
--
Michael