Re: Broken lock management in policy.c.

Поиск
Список
Период
Сортировка
От Peter Geoghegan
Тема Re: Broken lock management in policy.c.
Дата
Msg-id CAM3SWZSXc0e3AYyyPZ7f_-weMe07kGpAMdw-2mK5WHqZGFBYAw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Broken lock management in policy.c.  (Stephen Frost <sfrost@snowman.net>)
Ответы Re: Broken lock management in policy.c.  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Sun, Jan 3, 2016 at 6:00 PM, Stephen Frost <sfrost@snowman.net> wrote:
>> I'm not sure what you mean. The CREATE POLICY changes in commit
>> 43cd468cf01007f3 specifically call out the issue illustrated in my
>> example test case. There are some other changes made in that commit,
>> but they don't seem to be attempting to address this specific problem.
>> They also seem fine.
>
>
> I believe Tom's complaint was that the overall page is about CREATE POLICY,
> technically, and that the text in attempting to address the concern might be
> taken under the context of being a CREATE POLICY issue rather than a general
> RLS issue with row locking.

Really? But the problem happens as a consequence of having a
subqueries within CREATE POLICY's USING quals (as well as a
misunderstanding made by the admin about just what is possible).

-- 
Peter Geoghegan



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Broken lock management in policy.c.
Следующее
От: Ian Barwick
Дата:
Сообщение: Description tweak for vacuumdb