From: | Ted Yu <yuzhihong(at)gmail(dot)com> |
---|---|
To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | vignesh C <vignesh21(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: GUC for temporarily disabling event triggers |
Date: | 2023-01-12 21:04:56 |
Message-ID: | CALte62x7c9R0ohKcQSr5N9PFB-D6pCb_THhwWzTscR7ZB6OHvg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jan 12, 2023 at 12:26 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > 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/
>
> Hi,
`this GUC allows to temporarily suspending event triggers.`
It would be better to mention the name of GUC in the description.
Typo: suspending -> suspend
w.r.t. guc `ignore_event_trigger`, since it is supposed to disable event
triggers for a short period of time, is there mechanism to turn it off
(IGNORE_EVENT_TRIGGER_ALL) automatically ?
Cheers
From | Date | Subject | |
---|---|---|---|
Next Message | Christophe Pettus | 2023-01-12 21:07:04 | Re: errdetail vs errdetail_log? |
Previous Message | Andres Freund | 2023-01-12 20:35:32 | Re: errdetail vs errdetail_log? |