From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: How to create read-only view on 9.3 |
Date: | 2013-08-13 20:24:27 |
Message-ID: | 520A95FB.1050008@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08/13/2013 11:18 AM, Tom Lane wrote:
> Hannu Krosing <hannu(at)2ndQuadrant(dot)com> writes:
>> If you earlier used views for granting limited read access to some views
>> you definitely did not want view users suddenly gain also write access to
>> underlying table.
>
> Unless you'd explicitly granted those users insert/update/delete privilege
> on the view, they wouldn't suddenly be able to do something new in 9.3,
> because no such privileges are granted by default. If you had granted
> such privileges, you don't have much of a leg to stand on for complaining
> that now they can do it.
Ah, ok. I hadn't gotten to the testing phase yet.
I think we should have a script available for revoking all write privs
on all views and link it from somewhere (the release notes?), but I
don't see any need to change anything in the release.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2013-08-13 20:33:49 | Re: Review: UNNEST (and other functions) WITH ORDINALITY |
Previous Message | Greg Stark | 2013-08-13 20:11:52 | Re: Foreground vacuum and buffer access strategy |