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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: ahodgson(at)simkin(dot)ca, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
Date: 2023-03-03 14:47:11
Message-ID: 2416983.1677854831@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2023-03-03 15:50:40 Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
Previous Message Alvaro Herrera 2023-03-03 11:21:44 Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails