| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Gurjeet Singh" <singh(dot)gurjeet(at)gmail(dot)com>, "Joe Conway" <mail(at)joeconway(dot)com> |
| Cc: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>,"Josh" <josh(at)schemaverse(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: SET variable - Permission issues |
| Date: | 2011-10-10 21:32:27 |
| Message-ID: | 4E931E1B0200002500041D25@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Joe Conway <mail(at)joeconway(dot)com> wrote:
> On 10/10/2011 01:52 PM, Gurjeet Singh wrote:
>> ALTER USER novice SET MIN_VAL OF statement_timeout TO '1';
>> -- So that the user cannot turn off the timeout
>>
>> ALTER DATABASE super_reliable SET ENUM_VALS OF synchronous_commit
>> TO 'on';
>> -- So that the user cannot change the synchronicity of
>> transactions against this database.
>
> I like this better than GRANT/REVOKE on SET.
+1
I would really like a way to prevent normal users from switching
from the default transaction isolation level I set. This seems like
a good way to do that. Putting sane bounds on some other settings,
more to protect against the accidental bad settings than malicious
mischief, would be a good thing, too.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2011-10-10 21:37:32 | Re: unite recovery.conf and postgresql.conf |
| Previous Message | Joe Conway | 2011-10-10 21:23:25 | Re: SET variable - Permission issues |