From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
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, 03 Mar 2023 09:47:11 -0500
Message-ID: <2416983.1677854831@sss.pgh.pa.us> (raw)
In-Reply-To: <20230303112144.tzw3yeos2c5w3q6y@alvherre.pgsql>
References: <20230303112144.tzw3yeos2c5w3q6y@alvherre.pgsql>
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
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: tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, 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: <2416983.1677854831@sss.pgh.pa.us>
* 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