On Sun, Jan 3, 2016 at 6:00 PM, Stephen Frost <sfr...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
