Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
David Rowley <dgrowleyml@gmail.com>
From: David Rowley <dgrowleyml@gmail.com>
To: Dmitry Fomin <fomin.list@gmail.com>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2025-10-17T01:21:00Z
Lists: pgsql-bugs
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix incorrect logic for caching ResultRelInfos for triggers
- 2992b9a07ef0 15.15 landed
- a546964db6fb 16.11 landed
- 0d3074615380 17.7 landed
- a2387c32f2f8 18.1 landed
- 39dcfda2d23a 19 (unreleased) landed
On Fri, 17 Oct 2025 at 10:53, Dmitry Fomin <fomin.list@gmail.com> wrote: > -- Crash repro: cascaded UPDATE across partitions > UPDATE t.pipelines > SET partition_id = 50 > WHERE partition_id = 102 AND id = 1; > > > server closed the connection unexpectedly Thanks for the detailed report. It seems to have been caused by ba9a7e3921. For some reason the ResultRelInfo.ri_RootResultRelInfo isn't set for this partition which causes ExecGetChildToRootMap() to think no translation is required. More to come... David