Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
| От | Sean Chittenden |
|---|---|
| Тема | Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? |
| Дата | |
| Msg-id | 20030730213335.GD34647@perrin.int.nxad.com обсуждение |
| Ответ на | Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions? (Josh Berkus <josh@agliodbs.com>) |
| Ответы |
Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
|
| Список | 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
В списке pgsql-patches по дате отправления: