| From: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
|---|---|
| To: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Add pg_get_event_trigger_ddl() function |
| Date: | 2026-07-22 06:14:00 |
| Message-ID: | CAN4CZFM+j04o_gejjYZVZKMYmF4N-6+4wOavvFxDR78FY6TnwQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> That did cross my mind, but while "enabled" feels more natural grammatically,
> "enable" corresponds to the "ENABLE" clause which is to be emitted (or omitted).
> Except when it's "DISABLE"... I can't think of any better phrasing
> which is reasonably
> short and conveys the meaning "emit the clause which indicates the trigger is to
> be disabled or enabled, and if the latter in what context".
Yeah, I agree with this reasoning, I wasn't even sure to mention this
or not. I only did because the ALTER EVENT TRIGGER documentation also
mentions "disabled", so there's some precedent of using that form.
Keeping it "enable" is fine with me.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-07-22 06:21:27 | Fix missing FORMAT when deparsing JSON_ARRAY(query) |
| Previous Message | solai v | 2026-07-22 06:08:13 | Re: [PATCH] Add pg_get_event_trigger_ddl() function |