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 CAApHDvpNWPQU790AKFsMpSj4-fK1k7K78jigtPAXneiVT1_BBA@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
Tree view 
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.

David
Attachment

pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos
Next
From: "Euler Taveira"
Date:
Subject: Re: Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary