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

From Andrew Gierth
Subject Re: Add read-only param to set_config(...) / SET that effects (at least) customized runtime options
Date
Msg-id 871sf9ejmf.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: Add read-only param to set_config(...) / SET that effects (atleast) customized runtime options  (Chapman Flack <chap@anastigmatix.net>)
Responses Re: Add read-only param to set_config(...) / SET that effects (atleast) customized runtime options
List 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 by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: Toast issues with OldestXmin going backwards
Next
From: Peter Geoghegan
Date:
Subject: Re: Corrupted btree index on HEAD because of covering indexes