| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Broken lock management in policy.c. |
| Date: | 2016-01-04 02:09:03 |
| Message-ID: | 23043.1451873343@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Geoghegan <pg(at)heroku(dot)com> writes:
> On Sun, Jan 3, 2016 at 6:00 PM, Stephen Frost <sfrost(at)snowman(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2016-01-04 02:12:02 | Re: Broken lock management in policy.c. |
| Previous Message | Peter Geoghegan | 2016-01-04 02:09:02 | Re: Broken lock management in policy.c. |