Re: Add read-only param to set_config(...) / SET that effects (at least) customized runtime options

Поиск
Список
Период
Сортировка
От Andrew Gierth
Тема Re: Add read-only param to set_config(...) / SET that effects (at least) customized runtime options
Дата
Msg-id 871sf9ejmf.fsf@news-spur.riddles.org.uk
обсуждение исходный текст
Ответ на Re: Add read-only param to set_config(...) / SET that effects (atleast) customized runtime options  (Chapman Flack <chap@anastigmatix.net>)
Ответы Re: Add read-only param to set_config(...) / SET that effects (atleast) customized runtime options  (Chapman Flack <chap@anastigmatix.net>)
Список pgsql-hackers
>>>>> "Chapman" == Chapman Flack <chap@anastigmatix.net> writes:

 Chapman> It seemed to me at the time to be not hard to implement, even
 Chapman> just as an extension for proof of concept. One small obstacle
 Chapman> is that the check hook on a variable doesn't get called during
 Chapman> attempted RESET, so the only way to block a prohibited RESET
 Chapman> would have to be from an assign hook, which isn't expected to
 Chapman> fail. It could surely throw an error, but which would mess up
 Chapman> the whole RESET, but might be tolerable.

Assign hooks aren't allowed to throw errors under any circumstance
because they're called during transaction abort, and throwing an error
during abort is obviously not tolerable.

-- 
Andrew (irc:RhodiumToad)


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

Предыдущее
От: Andrew Gierth
Дата:
Сообщение: Re: Toast issues with OldestXmin going backwards
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: Corrupted btree index on HEAD because of covering indexes