Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos

From: David Rowley <dgrowleyml(at)gmail(dot)com>
To: feichanghong(at)qq(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Amit Langote <amitlangote09(at)gmail(dot)com>
Subject: Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
Date: 2025-09-17 21:43:19
Message-ID: CAApHDvoUketXqPj=1TpE81qPHvNj2fXRNomx2h7OkEm4nGqRcw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 18 Sept 2025 at 03:25, PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> I recently encountered a crash when executing a DELETE on PG18. The issue
> can be reproduced on the HEAD branch with the following steps:

Thanks for the report.

The first bad commit is:

commit bb3ec16e14ded1d23a46d3c7e623a965164fa124
Author: Amit Langote <amitlan(at)postgresql(dot)org>
Date: Thu Jan 30 11:57:32 2025 +0900

Move PartitionPruneInfo out of plan nodes into PlannedStmt

David

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message David Rowley 2025-09-17 22:32:35 Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
Previous Message Tom Lane 2025-09-17 18:02:09 Re: BUG #19055: Server crash at ExecInterpExpr