Re: Broken lock management in policy.c. - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Broken lock management in policy.c.
Date
Msg-id CAOuzzgqBjNOYHu4RJ9phG4CFcPzV2LycA0GiwL0=84w=1ZZjzw@mail.gmail.com
Whole thread Raw
In response to Re: Broken lock management in policy.c.  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Broken lock management in policy.c.  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
Peter,

On Sunday, January 3, 2016, Peter Geoghegan <pg@heroku.com> wrote:
On Sun, Jan 3, 2016 at 5:18 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> In any case, the text in create_policy.sgml seems to be a misleading
> description of the problem, as it's talking about DDL modifications
> which are *not* what's happening here.

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. 

Thanks!

Stephen 

pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Broken lock management in policy.c.
Next
From: Tom Lane
Date:
Subject: Re: Broken lock management in policy.c.