Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? - Mailing list pgsql-patches

From Tom Lane
Subject Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
Date
Msg-id 25296.1059603775@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?  (Sean Chittenden <sean@chittenden.org>)
Responses Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
List pgsql-patches
Sean Chittenden <sean@chittenden.org> writes:
>> It's not intended to be a security measure, and I would strongly
>> resist any attempt to make it so along the lines you propose.

> Intended or not, it does work.

No, you just haven't thought of a way to get around it yet.  When you do
think of one, you'll be wanting us to contort the GUC system to plug the
loophole.  We've already got a horrid mess in there for the LOG_XXX
variables, and I don't want to add more.

I'm not objecting to the idea of being able to make users read-only.
I'm objecting to using GUC for it.  Send in a patch that, say, adds a
bool column to pg_shadow, and I'll be happy.

            regards, tom lane

pgsql-patches by date:

Previous
From: Sean Chittenden
Date:
Subject: Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
Next
From: Tom Lane
Date:
Subject: Re: ruleutils with pretty-print option