| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Tomonari Katsumata <katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)jp>, Szymon Guz <mabewlun(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: How to create read-only view on 9.3 |
| Date: | 2013-08-13 18:19:13 |
| Message-ID: | 520A78A1.4030504@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/13/2013 01:33 PM, Hannu Krosing wrote:
>>
>> In any case, using permissions is a somewhat leaky bandaid, since
>> superusers have overriding access privileges anyway. A better way
>> to do what the OP wants might be to have a view trigger that raises an
>> exception.
> Superuser can easily disable or drop the trigger as well.
That's true, but it requires positive action to do so. Thus the trigger
can give you some protection in cases of stupidity, if not cases of malice.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-08-13 18:39:22 | Release schedule for PG 9.3 |
| Previous Message | Tom Lane | 2013-08-13 18:18:45 | Re: How to create read-only view on 9.3 |