| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 15:29:33 |
| Message-ID: | CA+TgmoappZX33b23mD6LE1oGr2a_83PgH1Cc7L4ukGtXs1zM4w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 5, 2023 at 8:12 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> > 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.
I don't care for the debug_xxx renaming, myself. I think that should
be reserved for things where we believe there's no reason to ever use
it in production/real life, or for things whose purpose is to emit
debugging messages. Neither is the case here.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2023-09-05 15:29:56 | Re: cataloguing NOT NULL constraints |
| Previous Message | Robert Haas | 2023-09-05 15:20:44 | Re: SLRUs in the main buffer pool - Page Header definitions |