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)
Список
Дерево обсуждения
Add read-only param to set_config(...) / SET that effects (at least)customized runtime options Matthias Kurz <m.kurz@irregular.at>
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 (at least) customized runtime options Andrew Gierth <andrew@tao11.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>
>>>>> "Chapman" == Chapman Flack 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 по дате отправления
От: Peter Geoghegan
Дата: