Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Bryn Llewellyn <bryn(at)yugabyte(dot)com>
Cc: Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, pgsql-general list <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
Date: 2022-08-24 02:50:50
Message-ID: CAKFQuwYb_Z3B=127KOXrn+KmHHxTUUbHiM6OGqmKSgpb2_+zug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Aug 23, 2022 at 7:32 PM Bryn Llewellyn <bryn(at)yugabyte(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Kyotaro Horiguchi 2022-08-24 05:18:11 Re: recovery_command has precedence over phisical slots?
Previous Message Bryn Llewellyn 2022-08-24 02:32:25 Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario