Re: Rename of triggers for partitioned tables

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Arne Roland <A(dot)Roland(at)index(dot)de>, 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-26 17:38:16
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Arne complained that there should be a unique constraint on (tgrelid,
> tgparentid) which would sidestep the need for this to be a loop. I
> don't think it's really necessary, and I'm not sure how to create a
> system index WHERE tgparentid <> 0.

Yeah, we don't support partial indexes on catalogs, and this example
doesn't make me feel like we ought to open that can of worms. But
then maybe this function shouldn't assume there's only one match?

regards, tom lane

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message 蔡梦娟 (玊于) 2021-07-26 17:38:58 Why don't update minimum recovery point in xact_redo_abort
Previous Message Bruce Momjian 2021-07-26 17:35:41 Re: Have I found an interval arithmetic bug?