From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: Arne Roland <A.Roland@index.de>, vignesh C <vignesh21@gmail.com>,
        Zhihong Yu <zyu@yugabyte.com>,
        Pg Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: Rename of triggers for partitioned tables
In-reply-to: <202107261714.kuzrvstzrufh@alvherre.pgsql>
References: <202107261714.kuzrvstzrufh@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Mon, 26 Jul 2021 13:14:20 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <171675.1627321096.1@sss.pgh.pa.us>
Date: Mon, 26 Jul 2021 13:38:16 -0400
Message-ID: <171676.1627321096@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/171676.1627321096%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.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