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

From Josh Berkus
Subject Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
Date
Msg-id 200307300827.47147.josh@agliodbs.com
Whole thread Raw
In response to [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,

> Um, why not make it an actual full blown security feature by applying
> the following patch?  This gives PostgreSQL real read only
> transactions that users can't escape from.  Notes about the patch:

Way nifty.

I vote in favor of this patch (suitably documented & debugged) for 7.5.

--
Josh Berkus
Aglio Database Solutions
San Francisco

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
Next
From: Tom Lane
Date:
Subject: Re: array expression NULL fix [was: [HACKERS] odd behavior/possible bug]