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

Поиск
Список
Период
Сортировка
От Josh Berkus
Тема Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
Дата
Msg-id 200312011059.50578.josh@agliodbs.com
обсуждение исходный текст
Ответ на Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: [PATCH] Re: [pgsql-advocacy] Why READ ONLY transactions?
Список pgsql-patches
Дерево обсуждения 
Bruce,

> This seems like a valuable feature, as others have mentioned.  However,
> should it also prevent changes to default_transaction_read_only?
>
> What is the use case for this functionality?

I thought that this was rejected thouroughly by Tom some months ago.  He
argued pretty strongly that READ ONLY transactions were *not* a security
feature and that trying to make them one would work very poorly.

--
Josh Berkus
Aglio Database Solutions
San Francisco

В списке pgsql-patches по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: export FUNC_MAX_ARGS as a read-only GUC variable (was: [GENERAL] SELECT Question)
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: export FUNC_MAX_ARGS as a read-only GUC variable