Re: GUC for temporarily disabling event triggers - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: GUC for temporarily disabling event triggers
Date
Msg-id F77693DD-C7E4-453F-A9DF-6ACB43DDB974@yesql.se
Whole thread Raw
In response to Re: GUC for temporarily disabling event triggers  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: GUC for temporarily disabling event triggers
List pgsql-hackers
> On 6 Sep 2023, at 16:22, Robert Haas <robertmhaas@gmail.com> wrote:
> On Wed, Sep 6, 2023 at 4:50 AM Daniel Gustafsson <daniel@yesql.se> wrote:

>> Fair enough, how about disable_event_trigger instead as per the attached?
>
> I usually prefer to give things a positive sense, talking about
> whether things are enabled rather than disabled. I'd do event_triggers
> = off | on, like we have for row_security. YMMV, though.

Fair enough, I don't have strong opinions and I do agree that making this work
like row_security is a good thing for consistency.  Done in the attached.

--
Daniel Gustafsson


Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Eager page freeze criteria clarification
Next
From: Melanie Plageman
Date:
Subject: Re: Eliminate redundant tuple visibility check in vacuum