GUC for temporarily disabling event triggers

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: GUC for temporarily disabling event triggers
Date: 2022-11-03 20:47:35
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

In the thread discussing the login event trigger patch it was argued that we
want to avoid recommending single-user mode for troubleshooting tasks, and a
GUC for temporarily disabling event triggers was proposed.

Since the login event trigger patch lost momentum, I've broken out the GUC part
into a separate patch to see if there is interest in that part alone, to chip
away at situations requiring single-user mode.

The patch adds a new GUC, ignore_event_trigger with two option values, 'all'
and 'none' (the login event patch had 'login' as well). This can easily be
expanded to have the different types of events, or pared down to a boolean
on/off. I think it makes more sense to make it more fine-grained but I think
there is merit in either direction.

If there is interest in this I'm happy to pursue a polished version of this

Daniel Gustafsson

Attachment Content-Type Size
v1-0001-Add-GUC-for-temporarily-disabling-event-triggers.patch application/octet-stream 10.2 KB


Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2022-11-03 21:22:15 Re: proposal: possibility to read dumped table's name from file
Previous Message Dave Page 2022-11-03 20:44:16 Re: Tracking last scan time