From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: ahodgson@simkin.ca, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with
 foreign key fails
In-reply-to: <20230303112144.tzw3yeos2c5w3q6y@alvherre.pgsql>
References: <20230303112144.tzw3yeos2c5w3q6y@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Fri, 03 Mar 2023 12:21:44 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2416982.1677854831.1@sss.pgh.pa.us>
Date: Fri, 03 Mar 2023 09:47:11 -0500
Message-ID: <2416983.1677854831@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2416983.1677854831%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2023-Mar-01, Tom Lane wrote:
>> It's a reasonable bet that we're trying to look up the child trigger
>> using the name of its parent trigger ... but why are we searching by
>> name at all, rather than OID?  Seems mighty failure-prone.

> I have no recollection of this, but we probably didn't have the OID
> originally.  It may be that simply changing that is enough to solve the
> problem.  I'll try to have a look later today, but I'm not sure I'll
> have time.

I can throw together a patch for what I was thinking of.

			regards, tom lane