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

From: Bryn Llewellyn <bryn(at)yugabyte(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, 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-12 04:52:43
Message-ID: BC0E0F77-BA43-4897-A1C2-117C4D677C8B@yugabyte.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> david(dot)g(dot)johnston(at)gmail(dot)com wrote:
>

Good. I can see the attachments here too:

https://www.postgresql.org/message-id/CAKFQuwaNcC2NPtwNY%2BNvbbHFQuphfkicvLxcnCbnwTTwKf%3DGdw%40mail.gmail.com

And I can download via the links with no problem. I'll aim to work out what's wrong my end as soon as I can.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Scott Simpson 2022-08-12 10:16:35 Migrating PostgreSQL Stored Procedures to MSSQL 2019 for example
Previous Message David G. Johnston 2022-08-12 03:58:56 Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario