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 22:32:35
Message-ID: CAApHDvpNWPQU790AKFsMpSj4-fK1k7K78jigtPAXneiVT1_BBA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, 18 Sept 2025 at 09:43, David Rowley <dgrowleyml(at)gmail(dot)com> wrote:
> 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

I think the attached is the correct fix. I also wonder if it's worth
an isolation test to exercise this code.

David

Attachment Content-Type Size
19056_fix.patch application/octet-stream 916 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Euler Taveira 2025-09-17 22:34:56 Re: Read Replica termination occurs when its max_active_replication_origins setting is lower than the primary
Previous Message David Rowley 2025-09-17 21:43:19 Re: BUG #19056: ExecInitPartitionExecPruning segfault due to NULL es_part_prune_infos