Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails - Mailing list pgsql-bugs

From Alvaro Herrera
Subject Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
Date
Msg-id 20230303112144.tzw3yeos2c5w3q6y@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On 2023-Mar-01, Tom Lane wrote:

> Interestingly, although that commit was back-patched to v11, the failure
> does not occur in pre-v15 branches.  So what's different about v15?

Hmm, I think f4566345cf40 probably explains that.

> 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.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17819: The assert failed #17334 has not been repaired
Next
From: Tom Lane
Date:
Subject: Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails