Re: Wrong security context for deferred triggers?

Laurenz Albe <laurenz.albe@cybertec.at>

From: Laurenz Albe <laurenz.albe@cybertec.at>

To: Pavel Stehule <pavel.stehule@gmail.com>

Cc: pgsql-hackers@lists.postgresql.org

Date: 2024-10-19T11:02:32Z

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

Attachments

v3-0001-Make-AFTER-triggers-run-with-the-correct-user.patch (text/x-patch) patch v3-0001

On Sat, 2024-10-19 at 06:17 +0200, Pavel Stehule wrote:
> Maybe we should document so the trigger is executed with the identity used by DML command always,
> when the trigger function has no SECURITY DEFINER flag?

Good idea.  Version 3 has documentation.

Yours,
Laurenz Albe