Re: A problem about ParamPathInfo for an AppendPath - Mailing list pgsql-hackers

From Richard Guo
Subject Re: A problem about ParamPathInfo for an AppendPath
Date
Msg-id CAMbWs49kv-yVOGKuPt6qZYHeDneCCPL-KS5uMDkcB3uJgHDtSA@mail.gmail.com
Whole thread Raw
In response to A problem about ParamPathInfo for an AppendPath  (Richard Guo <guofenglinux@gmail.com>)
Responses Re: A problem about ParamPathInfo for an AppendPath  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers

On Tue, Dec 6, 2022 at 5:00 PM Richard Guo <guofenglinux@gmail.com> wrote:
As we can see, MemoizePath can be generated for partitioned AppendPath
but not for union-all AppendPath.

For the fix I think we can relax the check in create_append_path and
always use get_baserel_parampathinfo if the parent is a baserel.
 
BTW, IIUC currently we don't generate any parameterized MergeAppend
paths, as explained in generate_orderedappend_paths.  So the codes that
gather information from a MergeAppend path's param_info for run-time
partition pruning in create_merge_append_plan seem unnecessary.

Attached is a patch for this change and the changes described upthread.

Thanks
Richard
Attachment

pgsql-hackers by date:

Previous
From: Antonin Houska
Date:
Subject: Re: refactor ExecGrant_*() functions
Next
From: John Naylor
Date:
Subject: Re: [PoC] Improve dead tuple storage for lazy vacuum