Request a Demo
Home   >   mailing lists

Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos - Mailing list pgsql-bugs

From David Rowley
Subject Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
Date
Msg-id CAApHDvoUketXqPj=1TpE81qPHvNj2fXRNomx2h7OkEm4nGqRcw@mail.gmail.com
Whole thread Raw
In response to BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
List pgsql-bugs
Tree view 
On Thu, 18 Sept 2025 at 03:25, PG Bug reporting form
<noreply@postgresql.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@postgresql.org>
Date:   Thu Jan 30 11:57:32 2025 +0900

    Move PartitionPruneInfo out of plan nodes into PlannedStmt

David

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #19055: Server crash at ExecInterpExpr
Next
From: David Rowley
Date:
Subject: Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos