Re: Bug: RLS policy FOR SELECT is used to check new rows

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: Bug: RLS policy FOR SELECT is used to check new rows
Дата
Msg-id CA+TgmoZZOf1SwK25U=B9_X8RYE681PYm1Phen1uQ5tiLhCW=kg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Bug: RLS policy FOR SELECT is used to check new rows  (Laurenz Albe <laurenz.albe@cybertec.at>)
Ответы Re: Bug: RLS policy FOR SELECT is used to check new rows  (Laurenz Albe <laurenz.albe@cybertec.at>)
Список 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 по дате отправления:

Предыдущее
От: Adam Hendel
Дата:
Сообщение: [PATCH] pgbench log file headers
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Question about non-blocking mode in libpq