Re: Bug: RLS policy FOR SELECT is used to check new rows - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Bug: RLS policy FOR SELECT is used to check new rows
Date
Msg-id CA+TgmoZZOf1SwK25U=B9_X8RYE681PYm1Phen1uQ5tiLhCW=kg@mail.gmail.com
Whole thread Raw
In response to Re: Bug: RLS policy FOR SELECT is used to check new rows  (Laurenz Albe <laurenz.albe@cybertec.at>)
Responses Re: Bug: RLS policy FOR SELECT is used to check new rows
List pgsql-hackers
On Fri, Nov 10, 2023 at 7:43 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> So, from my perspective, we should never have let FOR SELECT policies
> mess with an UPDATE.  But I am too late for that; such a change would
> be way too invasive now.  So I'd like to introduce a "back door" by
> creating a FOR SELECT policy with WITH CHECK (TRUE).

In principle I see no problem with some kind of back door here, but
that seems like it might not be the right way to do it. I don't think
we want constant true to behave arbitrarily differently than any other
expression. Maybe that's not what you had in mind and I'm just not
seeing the full picture, though.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Adam Hendel
Date:
Subject: [PATCH] pgbench log file headers
Next
From: Bruce Momjian
Date:
Subject: Re: Question about non-blocking mode in libpq