On 10/16/2014 12:25 PM, Fujii Masao wrote: > Hi, > > While I was checking the behavior of RLS, I found that the policy for SELECT > doesn't seem to be applied to RETURNING. Is this intentional?
This is why I was opposed to having a "SELECT" policy at all. It should be "VISIBLE", "INSERT", "UPDATE", "DELETE". I say "VISIBLE" instead of "READ" because I don't think the rows affected by an UPDATE or DELETE should be affected by whether or not they have a RETURNING clause. That's IMO nonsensical.and violates the usual expectations about which clauses can have filtering effects. So the read-filtering policy should apply to all statements. Not just SELECT. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
