| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Daniel Gustafsson <daniel(at)yesql(dot)se>, 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-04-05 22:06:47 |
| Message-ID: | ZC3w91Q5wyDjSfjJ@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 05, 2023 at 10:43:23AM -0400, Tom Lane wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Maybe we should back up and ask why we need more than "on" and "off".
>> If somebody is using this feature in any form more than very
>> occasionally, they should really go home and reconsider their database
>> schema.
>
> +1 ... this seems perhaps overdesigned.
Yes. If you begin with an "on"/"off" switch, it could always be
extended later if someone makes a case for it, with a grammar like one
I mentioned upthread, or even something else. If there is no strong
case for more than a boolean for now, simpler is better.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2023-04-05 22:09:37 | Re: [BUG] pg_stat_statements and extended query protocol |
| Previous Message | Peter Geoghegan | 2023-04-05 22:05:21 | Re: Option to not use ringbuffer in VACUUM, using it in failsafe mode |