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

David Rowley <dgrowleyml@gmail.com>

From: David Rowley <dgrowleyml@gmail.com>

To: Amit Langote <amitlangote09@gmail.com>

Cc: feichanghong <feichanghong@qq.com>, pgsql-bugs@lists.postgresql.org

Date: 2025-09-18T03:47:37Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Fix EPQ crash from missing partition pruning state in EState
- 9a82a64edcd8 18.0 landed
- 8741e48e5dda 19 (unreleased) landed
Calculate agglevelsup correctly when Aggref contains a CTE.
- b0cc0a71e0a0 19 (unreleased) cited
Move PartitionPruneInfo out of plan nodes into PlannedStmt
- bb3ec16e14de 18.0 cited

On Thu, 18 Sept 2025 at 15:37, Amit Langote <amitlangote09@gmail.com> wrote:
> Fixed.  Will push this barring objections.

Thanks for adding the test case.

> +# Test that EState.es_part_prune_infos is properly set in EvalPlanQualStart()
> +# Bug #19056

I don't think it's that useful to note down the bug number that caused
that test to be added. I think it'd be better to write something like:

"Exercise run-time partition pruning code in an EPQ plan"

If someone really wants to know why the test was added, git blame
linking back to the discussion in the commit message is the normal
workflow.

David