Re: RLS fails to work with UPDATE ... WHERE CURRENT OF
От | Robert Haas |
---|---|
Тема | Re: RLS fails to work with UPDATE ... WHERE CURRENT OF |
Дата | |
Msg-id | CA+TgmoZsCux4Kbj3+r11Tn5bfV_AqVLndpw0NRUipWO=ORZgrQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: RLS fails to work with UPDATE ... WHERE CURRENT OF (Joe Conway <mail@joeconway.com>) |
Ответы |
Re: RLS fails to work with UPDATE ... WHERE CURRENT OF
|
Список | pgsql-hackers |
On Thu, Jul 9, 2015 at 5:47 PM, Joe Conway <mail@joeconway.com> wrote: > On 06/08/2015 02:08 AM, Dean Rasheed wrote: >> Actually I think it is fixable just by allowing the CURRENT OF >> expression to be pushed down into the subquery through the >> security barrier view. The planner is then guaranteed to generate a >> TID scan, filtering by any other RLS quals, which ought to be the >> optimal plan. Patch attached. > > This looks good to me. I have tested and don't find any issues with > it. Will commit in a day or so unless someone has objections. Is this fix needed in all versions that support security barrier views, or just in 9.5 and 9.6 that have RLS specifically? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: