Re: Wrong security context for deferred triggers?

Laurenz Albe <laurenz.albe@cybertec.at>

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

To: Joseph Koshakow <koshy44@gmail.com>

Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>, pgsql-hackers@lists.postgresql.org, isaac.morland@gmail.com

Date: 2024-07-08T12:36:45Z

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 7/8/24 04:14, Joseph Koshakow wrote:
> Given the above and the fact that the patch is a breaking change, my
> vote would still be to keep the current behavior and update the
> documentation. Though I'd be happy to be overruled by someone with more
> knowledge of triggers.

Thanks for that feedback.
Based on that, the patch should be rejected.

Since there were a couple of other opinions early in the thread, I'll let
it sit like that for now, and judgement can be passed at the end of the
commitfest.  Perhaps somebody else wants to chime in.

Yours,
Laurenz Albe