Re: [HACKERS] Row Level Security UPDATE Confusion - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Row Level Security UPDATE Confusion
Date
Msg-id CA+TgmobBXtNgNCobO9CD-B5VH3Gc4Mb6tY2DPYiMSQzP4ptQ1Q@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Row Level Security UPDATE Confusion  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Fri, Apr 14, 2017 at 9:09 AM, Stephen Frost <sfrost@snowman.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Should pg_current_wal_location() become pg_current_wal_lsn()
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] Row Level Security UPDATE Confusion