From: | Sean Chittenden <sean(at)chittenden(dot)org> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? |
Date: | 2003-07-30 21:33:35 |
Message-ID: | 20030730213335.GD34647@perrin.int.nxad.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-advocacy pgsql-hackers pgsql-patches |
> > 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.
Heh, there ain't much to debug: it's pretty straight forward. I ran
all the use cases/syntaxes I could think of and they worked as
expected. It's a pretty chump little ditty that I originally wrote
for the sake of the 7.4 PR, but it's proving to be quite useful here
in my tree... though I like the name "jail_read_only_transactions"
more... patch updated for new name.
-sc
--
Sean Chittenden
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2003-07-30 21:40:05 | Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? |
Previous Message | Sean Chittenden | 2003-07-30 21:10:26 | Re: [PATCHES] [PATCH] Re: Why READ ONLY transactions? |
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2003-07-30 21:40:05 | Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? |
Previous Message | Sean Chittenden | 2003-07-30 21:10:26 | Re: [PATCHES] [PATCH] Re: Why READ ONLY transactions? |
From | Date | Subject | |
---|---|---|---|
Next Message | Sean Chittenden | 2003-07-30 21:40:05 | Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? |
Previous Message | Sean Chittenden | 2003-07-30 21:10:26 | Re: [PATCHES] [PATCH] Re: Why READ ONLY transactions? |