Date: Sun, 15 Feb 2015 02:13:28 -0700 (MST)
From: David G Johnston <david.g.johnston@gmail.com>
To: pgsql-hackers@postgresql.org
Message-ID: <1423991608861-5838021.post@n5.nabble.com>
In-Reply-To: <tencent_52390E301F51636C42CD9500@qq.com>
References: <tencent_52390E301F51636C42CD9500@qq.com>
Subject: Re: restrict global access to be readonly
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

happy times wrote
> Sure, we can utilize the   runtime parameter
> default_transaction_read_only, however, it does not restrict user from
> changing transaction attribute to non-readonly mode, so is not safe. 

ISTM that implementing a means to make this setting only super-user
changeable would be a quick(er) solution to the problem - the decision as to
what to disallow is already decided.

It seems like it would have to be a separate GUC but it would require any
new SQL but would simply leverage the existing settings system to setup
database-user values that only a super-user can change.

David J.


--
View this message in context: http://postgresql.nabble.com/restrict-global-access-to-be-readonly-tp5837818p5838021.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers