From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: alpic@benchmarkconsulting.com
Subject: BUG #18521: RLS should report when non-select operation is refused
Date: Mon, 24 Jun 2024 18:10:29 +0000
Message-ID: <18521-8c6cf61397cdc7ea@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18521
Logged by: Alain Picard
Email address: alpic@benchmarkconsulting.com
PostgreSQL version: 15.1
Operating system: Ubuntu
Description:
When dealing with RLS policies it is possible to have an update operation
for example that is refused and to received a success status.
Even when looking at logs, nothing clearly indicates that the operation was
refused. In the case of debugging, we should also be able to at least be
able to know which policy triggered the refusal.
I would even expect to have a debug mode where it is possible to trace all
of the RLS policies that are invoked, in which order and to easily identify
if and where the operation is denied.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, alpic@benchmarkconsulting.com
Subject: Re: BUG #18521: RLS should report when non-select operation is refused
In-Reply-To: <18521-8c6cf61397cdc7ea@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox