| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Arne Roland <A(dot)Roland(at)index(dot)de> |
| Cc: | vignesh C <vignesh21(at)gmail(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Rename of triggers for partitioned tables |
| Date: | 2021-07-22 17:51:50 |
| Message-ID: | 202107221751.adgv73algddv@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021-Jul-22, Arne Roland wrote:
> alter table middle disable trigger b;
> creates the same kind of inconsistency
> alter trigger b on middle rename to something;
> does.
> With other words: enableing/disabling non-topmost triggers should be forbidden as well.
I'm not so sure about that ... I think enabling/disabling triggers on
individual partitions is a valid use case. Renaming them, not so much.
--
Álvaro Herrera Valdivia, Chile — https://www.EnterpriseDB.com/
"No necesitamos banderas
No reconocemos fronteras" (Jorge González)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-07-22 18:21:42 | Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers) |
| Previous Message | Arne Roland | 2021-07-22 17:45:49 | Re: Rename of triggers for partitioned tables |