Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift) - Mailing list pgsql-bugs

From David Rowley
Subject Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
Date
Msg-id CAApHDvq_ajD4SZFePL3nrSFO6GgD7pp9fQMvin3UsJPeiu-sPQ@mail.gmail.com
Whole thread Raw
In response to Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)  (Dmitry Fomin <fomin.list@gmail.com>)
Responses Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Jeff Davis
Date:
Subject: Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade
Next
From: Andrew Bille
Date:
Subject: Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases