Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: Dmitry Fomin <fomin(dot)list(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Segfault in RI UPDATE CASCADE on partitioned tables with LIKE+ATTACH child (attnum drift)
Date: 2025-10-17 01:21:00
Message-ID: CAApHDvq_ajD4SZFePL3nrSFO6GgD7pp9fQMvin3UsJPeiu-sPQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, 17 Oct 2025 at 10:53, Dmitry Fomin <fomin(dot)list(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Bille 2025-10-17 07:05:51 Re: BUG #19074: pg_dump from v18 loses the NOT NULL flag in the inherited table field when dumping v17-databases
Previous Message Jeff Davis 2025-10-16 19:40:49 Re: BUG #19078: Segfaults in tts_minimal_store_tuple() following pg_upgrade