| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
| Cc: | Matthias Kurz <m(dot)kurz(at)irregular(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add read-only param to set_config(...) / SET that effects (at least) customized runtime options |
| Date: | 2018-04-20 20:03:17 |
| Message-ID: | 871sf9ejmf.fsf@news-spur.riddles.org.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Chapman" == Chapman Flack <chap(at)anastigmatix(dot)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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2018-04-20 20:06:15 | Re: Corrupted btree index on HEAD because of covering indexes |
| Previous Message | Andrew Gierth | 2018-04-20 19:56:22 | Re: Toast issues with OldestXmin going backwards |