Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails

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