Re: Row Level Security UPDATE Confusion

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Rod Taylor <rod(dot)taylor(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Row Level Security UPDATE Confusion
Date: 2017-04-14 13:14:11
Message-ID: CA+TgmobBXtNgNCobO9CD-B5VH3Gc4Mb6tY2DPYiMSQzP4ptQ1Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 14, 2017 at 9:09 AM, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> I agree that the documentation could be improved here.

This does not seem like it's only a documentation problem. There
seems to be no principled reason why a grant for ALL shouldn't have
exactly the same effect as one grant per relevant operation type.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-04-14 13:16:15 Re: Row Level Security UPDATE Confusion
Previous Message Robert Haas 2017-04-14 13:11:02 Re: Should pg_current_wal_location() become pg_current_wal_lsn()