Re: Issue attaching a table to a partitioned table with an auto-referenced foreign key

Cheetah <fastcat@gmail.com>

From: Matthew Gabeler-Lee <fastcat@gmail.com>
To: Alvaro Herrera <alvherre@kurilemu.de>
Cc: Tender Wang <tndrwang@gmail.com>, Jehan-Guillaume de Rorthais <jgdr@dalibo.com>, pgsql-bugs@lists.postgresql.org, Christoph Berg <myon@debian.org>, PostgreSQL Developers <pgsql-hackers@postgresql.org>, Guillaume Lelarge <guillaume@lelarge.info>, Luca Vallisa <luca.vallisa@gmail.com>
Date: 2025-05-08T17:14:56Z
Lists: pgsql-bugs, pgsql-hackers
On Sat, May 3, 2025 at 9:09 AM Alvaro Herrera <alvherre@kurilemu.de> wrote:
> Y'all are still on time to test this a bit more before next week's
> releases ... if I have made things even worse I can still revert the
> patch.  With luck, that won't be necessary.

I was not able to get to testing this before the release, but I was
able to test today after the release at least.

My earlier test case, and an adjusted version of it that is closer to
my production application (notably adding ON DELETE CASCADE to the
FK), now passes with 15.13.

Thank you :D



Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Handle self-referencing FKs correctly in partitioned tables

  2. Restructure foreign key handling code for ATTACH/DETACH

  3. Fix self-referencing foreign keys with partitioned tables