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

From Amit Langote
Subject Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
Date
Msg-id CA+HiwqG7Heq9WuzwtNixdqYEOAgcEgmx7dQGkGE0Bwt3v0EBXw@mail.gmail.com
Whole thread Raw
In response to Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
List pgsql-bugs
On Thu, Sep 18, 2025 at 7:32 AM David Rowley <dgrowleyml@gmail.com> wrote:
> On Thu, 18 Sept 2025 at 09:43, David Rowley <dgrowleyml@gmail.com> wrote:
> > 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
>
> I think the attached is the correct fix.  I also wonder if it's worth
> an isolation test to exercise this code.

Thanks for the patch, David, and for the report, Fei.  I indeed forgot
to update EvalPlanQualStart() in that commit.

I agree about adding an isolation test, which I have done in the
attached updated patch.

--
Thanks, Amit Langote

Attachment

pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: TRAP: failed Assert("outerPlan != NULL") in postgres_fdw.c
Next
From: feichanghong
Date:
Subject: Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos