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