Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario - Mailing list pgsql-general

From David G. Johnston
Subject Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
Date
Msg-id CAKFQuwYb_Z3B=127KOXrn+KmHHxTUUbHiM6OGqmKSgpb2_+zug@mail.gmail.com
Whole thread Raw
In response to Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario  (Bryn Llewellyn <bryn@yugabyte.com>)
List pgsql-general
On Tue, Aug 23, 2022 at 7:32 PM Bryn Llewellyn <bryn@yugabyte.com> wrote:

The account of my GitHub issue includes a preliminary test that shows that there's something to investigate further. I copied it below. Please tell me if it meets your succinctness criteria. If it does, then I'll submit it to the psql-bugs list as you suggest.


Fair point, go ahead and just post to -bugs because I'm not going to be diving that deeply into this right now.

David J.

pgsql-general by date:

Previous
From: Bryn Llewellyn
Date:
Subject: Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: recovery_command has precedence over phisical slots?