> On 27 Jan 2023, at 15:00, Mikhail Gribkov <youzh...@gmail.com> wrote:
> There is a complete framework for disabling various types of the event > triggers separately, but, the list of valid GUC values only include 'all' and > 'none'. Why not adding support for all the event trigger types separately? > Everything is already there in the patch; the only thing needed is expanding > couple of enums. It's cheap in terms of code size and even cheaper in terms > of performance. And moreover - it would be a good example for anyone adding > new trigger types. I can't exactly recall my reasoning, but I do think you're right that if we're to have this GUC it should support the types of existing EVTs. The updated v4 implements that as well as a rebase on top of master and fixing a typo discovered upthread. -- Daniel Gustafsson
v4-0001-Add-GUC-for-temporarily-disabling-event-triggers.patch
Description: Binary data