Horton

Re: Wrong security context for deferred triggers?

Pavel Stehule <pavel.stehule@gmail.com>

View thread
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: pgsql-hackers@lists.postgresql.org
Date: 2024-10-19T17:13:18Z
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 →

  1. Doc: improve description of which role runs a trigger.

  2. Change role names used in trigger test.

  3. Ensure that AFTER triggers run as the instigating user.

  4. Reverse the search order in afterTriggerAddEvent().

so 19. 10. 2024 v 13:02 odesílatel Laurenz Albe <laurenz.albe@cybertec.at>
napsal:

> 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.
>

perfect

all tests passed

I'll mark this patch as ready for committer

Regards

Pavel


>
> Yours,
> Laurenz Albe
>