From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: ahodgson@simkin.ca
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17817: DISABLE TRIGGER ALL on a partitioned table with foreign key fails
Date: Fri, 3 Mar 2023 12:21:44 +0100
Message-ID: <20230303112144.tzw3yeos2c5w3q6y@alvherre.pgsql> (raw)
In-Reply-To: <1554133.1677703918@sss.pgh.pa.us>
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/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: alvherre@alvh.no-ip.org, tgl@sss.pgh.pa.us, 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>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox