Re: Rename of triggers for partitioned tables
| От | Arne Roland |
|---|---|
| Тема | Re: Rename of triggers for partitioned tables |
| Дата | |
| Msg-id | 85343944ff5f43d8b30fdd258a97d85b@index.de обсуждение исходный текст |
| Ответ на | Re: Rename of triggers for partitioned tables (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
| Ответы |
Re: Rename of triggers for partitioned tables
|
| Список | pgsql-hackers |
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
Sent: Thursday, July 22, 2021 19:33
To: Arne Roland
Subject: Re: Rename of triggers for partitioned tables
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
> 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
В списке pgsql-hackers по дате отправления: