Re: SET variable - Permission issues - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: SET variable - Permission issues
Date
Msg-id 4E931E1B0200002500041D25@gw.wicourts.gov
Whole thread Raw
In response to Re: SET variable - Permission issues  (Joe Conway <mail@joeconway.com>)
Responses Re: SET variable - Permission issues  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Joe Conway <mail@joeconway.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


pgsql-hackers by date:

Previous
From: Joe Conway
Date:
Subject: Re: SET variable - Permission issues
Next
From: Simon Riggs
Date:
Subject: Re: unite recovery.conf and postgresql.conf