From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: 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: <20230303181735.quhcvh2igowmxbs7@alvherre.pgsql>
References: <20230303181735.quhcvh2igowmxbs7@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Fri, 03 Mar 2023 19:17:35 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2553511.1677868886.1@sss.pgh.pa.us>
Date: Fri, 03 Mar 2023 13:41:26 -0500
Message-ID: <2553512.1677868886@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2553512.1677868886%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2023-Mar-03, Tom Lane wrote:
>> Basically just make the recursive steps match on tgparentid instead
>> of name, like this.

> Thank you, looks sane to me.

OK, will work on getting it committed.

> I wonder how come this problem took so long to be detected with Ruby on
> Rails; it's been in released 13.x and 14.x for seven months now.  I
> suppose it would be very useful if the Ruby on Rails community would run
> their tests more often on new Postgres versions (or even on the tip of
> stable branches).

Um ... 13.x and 14.x aren't showing the problem, or is there something
I missed?  But I agree that it'd be good if we could get some Ruby folk
to test more promptly --- it's pretty sad that this didn't get noticed
sooner in v15.

			regards, tom lane