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

From Peter Geoghegan
Subject Re: Broken lock management in policy.c.
Date
Msg-id CAM3SWZSZJvWUYkjaKwDTn0c_zQx6PUpnYYnCL=ve6baMAnyMFA@mail.gmail.com
Whole thread Raw
In response to Re: Broken lock management in policy.c.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Jan 3, 2016 at 6:09 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> 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.

I agree that the text was unclear, and that that should be fixed,
because it's too complicated to expect anyone to understand this
without an example (indeed, that's why I used isolationtester to
explain the issue). My confusion was only about whether it was
understood that Stephen had fulfilled my request to document this
behavior.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Broken lock management in policy.c.
Next
From: Tom Lane
Date:
Subject: Re: 9.5 BLOCKER: regrole and regnamespace and quotes