Re: GUC for temporarily disabling event triggers

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Mikhail Gribkov <youzhick(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: GUC for temporarily disabling event triggers
Date: 2023-09-05 12:12:32
Message-ID: A435FBF6-9CEA-46C9-B5F3-00E6E5D7BADD@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 6 Apr 2023, at 00:06, Michael Paquier <michael(at)paquier(dot)xyz> wrote:

> If there is no strong
> case for more than a boolean for now, simpler is better.

The attached version of the patch replaces it with a boolean flag for turning
off all event triggers, and I also renamed it to the debug_xxx "GUC namespace"
which seemed more appropriate.

--
Daniel Gustafsson

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2023-09-05 12:30:41 Re: persist logical slots to disk during shutdown checkpoint
Previous Message Daniel Gustafsson 2023-09-05 12:06:14 Re: pg_basebackup: Always return valid temporary slot names