Re: Rename of triggers for partitioned tables
| От | Arne Roland |
|---|---|
| Тема | Re: Rename of triggers for partitioned tables |
| Дата | |
| Msg-id | 4217d1f783704ef7b9261e89065c24f2@index.de обсуждение |
| Ответ на | Re: Rename of triggers for partitioned tables (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
From: Tom Lane <tgl@sss.pgh.pa.us>
> Yeah, we don't support partial indexes on catalogs, and this example
I asked why such an index doesn't exists already. I guess that answers it. I definitely don't want to push for supporting that, especially not knowing what it entails.
Sent: Monday, July 26, 2021 19:38
To: Alvaro Herrera
Subject: Re: Rename of triggers for partitioned tables
To: Alvaro Herrera
Subject: Re: Rename of triggers for partitioned tables
> doesn't make me feel like we ought to open that can of worms.
I asked why such an index doesn't exists already. I guess that answers it. I definitely don't want to push for supporting that, especially not knowing what it entails.
> But then maybe this function shouldn't assume there's only one match?
I'd consider a duplication here a serious bug. That is pretty much catalog corruption. Having two children within a single child table sounds like it would break a lot of things.
That being said this function is hardly performance critical. I don't know whether throwing an elog indicating what's going wrong here would be worth it.
Regards
Arne
В списке pgsql-hackers по дате отправления: