| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Sean Chittenden <sean(at)chittenden(dot)org>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? |
| Date: | 2003-07-30 15:27:47 |
| Message-ID: | 200307300827.47147.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-07-30 15:31:55 | Re: [PATCHES] [PATCH] Re: Why READ ONLY transactions? |
| Previous Message | Josh Berkus | 2003-07-30 15:24:10 | Re: WebGUI vote on whether to drop PostgreSQL support |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-07-30 15:31:55 | Re: [PATCHES] [PATCH] Re: Why READ ONLY transactions? |
| Previous Message | Andrew Dunstan | 2003-07-30 15:09:28 | Re: Feature request -- Log Database Name |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-07-30 15:31:55 | Re: [PATCHES] [PATCH] Re: Why READ ONLY transactions? |
| Previous Message | Fernando Nasser | 2003-07-30 15:24:40 | Re: JDBC stored procs doc patch |