Feedback-ID: ia2694551:Fastmail
Date: Wed, 27 Nov 2024 20:01:09 +0100
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Paul Foerster <paul.foerster@gmail.com>, 
	Adrian Klaver <adrian.klaver@aklaver.com>, pgsql-general list <pgsql-general@lists.postgresql.org>
Subject: Re: PostgreSQL 15.10 update corrective action for ATTACH
 PARTITION/DETACH PARTITION
Message-ID: <202411271901.6wtx66ah4sy6@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <1900196.1732733556@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/202411271901.6wtx66ah4sy6%40alvherre.pgsql>
Precedence: bulk

On 2024-Nov-27, Tom Lane wrote:

> I doubt that there's anything actually wrong with the catalog state at
> this point (perhaps Alvaro would confirm that).  That leads to the
> conclusion that what's wrong is the release notes' query for fingering
> broken constraints, and it needs some additional test to avoid
> complaining about (I suspect) self-reference cases.

Ugh, I hadn't noticed this report, thanks for CCing me.  I'll have a
look at this tomorrow.  You're right that I didn't think of checking
self-referencing FKs with the query.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
<Schwern> It does it in a really, really complicated way
<crab> why does it need to be complicated?
<Schwern> Because it's MakeMaker.