| From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: missing locking in at least INSERT INTO view WITH CHECK |
| Date: | 2015-08-27 18:19:35 |
| Message-ID: | CAEZATCVdQYrwrDfV4s4Tz5d-KKReuJddD2Y_8_qRdc2YODw8kg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 27 August 2015 at 18:44, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2015-08-27 18:37:10 +0100, Dean Rasheed wrote:
>> I have a feeling that RLS might suffer from the same issue, but I
>> haven't looked yet.
>
> There's a similar issue there, yes:
> http://archives.postgresql.org/message-id/20150827124931.GD15922%40awork2.anarazel.de
>
> Are you thinking of that angle, or yet another one?
>
Yeah, that's what I was thinking of - I just hadn't caught up on all my mail.
It also seems to me that this warning has proved its worth, although I
don't think it's something a production build should be producing.
Perhaps it could be an Assert?
Regards,
Dean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-08-27 18:29:15 | Re: missing locking in at least INSERT INTO view WITH CHECK |
| Previous Message | Dean Rasheed | 2015-08-27 18:00:18 | Re: AcquireRewriteLocks/acquireLocksOnSubLinks vs. rowsecurity |