Re: GUC for temporarily disabling event triggers

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: vignesh C <vignesh21(at)gmail(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: GUC for temporarily disabling event triggers
Date: 2023-01-12 20:26:05
Message-ID: 75137FF2-26FA-4119-BF2D-88BF0FBEE853@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 11 Jan 2023, at 17:38, vignesh C <vignesh21(at)gmail(dot)com> wrote:
>
> On Tue, 29 Nov 2022 at 18:16, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>>
>>> On 3 Nov 2022, at 21:47, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>>
>>> The patch adds a new GUC, ignore_event_trigger with two option values, 'all'
>>> and 'none' (the login event patch had 'login' as well).
>>
>> The attached v2 fixes a small bug which caused testfailures the CFBot.
>
> The patch does not apply on top of HEAD as in [1], please post a rebased patch:

The attached rebased v3 fixes the conflict.

--
Daniel Gustafsson https://vmware.com/

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christophe Pettus 2023-01-12 20:28:39 errdetail vs errdetail_log?
Previous Message Andrey Borodin 2023-01-12 19:46:54 Re: Transaction timeout