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

From Tom Lane
Subject Re: Broken lock management in policy.c.
Date
Msg-id 23043.1451873343@sss.pgh.pa.us
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 Geoghegan <pg@heroku.com> writes:
> On Sun, Jan 3, 2016 at 6:00 PM, Stephen Frost <sfrost@snowman.net> wrote:
>> 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

If that's what we're talking about, let's say it in precisely that many
words.  With an example.  The current text is 100% useless.
        regards, tom lane



pgsql-hackers by date:

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