Horton

Re: GUC for temporarily disabling event triggers

Daniel Gustafsson <daniel@yesql.se>

View thread View on postgr.es
From: Daniel Gustafsson <daniel@yesql.se>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>, Tom Lane <tgl@sss.pgh.pa.us>, Justin Pryzby <pryzby@telsasoft.com>, Mikhail Gribkov <youzhick@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2023-09-06T20:23:55Z
Lists: pgsql-hackers

Attachments

> 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

Commits

  1. Add GUC for temporarily disabling event triggers

  2. Fix typos in code and comments