Re: RLS related docs
От | Dean Rasheed |
---|---|
Тема | Re: RLS related docs |
Дата | |
Msg-id | CAEZATCXGzy3P992CHtzf8Nh4_StTqGUzrVAsRzOjW=K6qrMSPg@mail.gmail.com обсуждение исходный текст |
Ответ на | RLS related docs (Joe Conway <mail@joeconway.com>) |
Ответы |
Re: RLS related docs
|
Список | pgsql-hackers |
On 25 May 2016 at 02:04, Joe Conway <mail@joeconway.com> wrote: > Please see attached two proposed patches for the docs related to RLS: > > 1) Correction to pg_restore > 2) Additional mentions that "COPY FROM" does not allow RLS to be enabled > > Comments? > The pg_restore change looks good -- that was clearly wrong. Also, +1 for the new note in pg_dump. For COPY, I think perhaps it would be more logical to put the new note immediately after the third note which describes the privileges required, since it's kind of related, and then we can talk about the RLS policies required, e.g.: If row-level security is enabled for the table, COPY table TO is internally converted to COPY (SELECT * FROM table)TO, and the relevant security policies are applied. Currently, COPY FROM is not supported for tables with row-levelsecurity. > Related question: I believe > > COPY tbl TO ... > > is internally converted to > > COPY (select * FROM tbl) TO ... > > when RLS is involved. Do we want to document that? > I think so, yes, because that makes it clearer what policies will be applied. Regards, Dean
В списке pgsql-hackers по дате отправления: