From: | Arne Roland <A(dot)Roland(at)index(dot)de> |
---|---|
To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
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:45:49 |
Message-ID: | 85343944ff5f43d8b30fdd258a97d85b@index.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Sent: Thursday, July 22, 2021 19:33
To: Arne Roland
Subject: Re: Rename of triggers for partitioned tables
On 2021-Jul-22, Arne Roland wrote:
> Since it is sort of the same problem, I think it might be worthwhile
> to address it as well within this patch. Adding two to four ereports
> doesn't sound like scope creeping to me, even though it touches
> completely different code. I'll look into that as well.
I don't understand what you mean. But here's an updated patch, with the
following changes
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.
Regards
Arne
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2021-07-22 17:51:50 | Re: Rename of triggers for partitioned tables |
Previous Message | Alvaro Herrera | 2021-07-22 17:41:33 | Re: Rename of triggers for partitioned tables |