Re: Wrong security context for deferred triggers? - Mailing list pgsql-hackers

From Laurenz Albe
Subject Re: Wrong security context for deferred triggers?
Date
Msg-id a9c18c43-dbd8-4a5a-b665-29abe6828c70@cybertec.at
Whole thread Raw
In response to Re: Wrong security context for deferred triggers?  (Joseph Koshakow <koshy44@gmail.com>)
Responses Re: Wrong security context for deferred triggers?
List pgsql-hackers
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




pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Improving the latch handling between logical replication launcher and worker processes.
Next
From: Tom Lane
Date:
Subject: Re: Is it expected behavior index only scan shows "OPERATOR(pg_catalog." for EXPLAIN?