Re: A problem about ParamPathInfo for an AppendPath

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A problem about ParamPathInfo for an AppendPath
Date: 2022-12-12 09:55:01
Message-ID: CAMbWs49kv-yVOGKuPt6qZYHeDneCCPL-KS5uMDkcB3uJgHDtSA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Dec 6, 2022 at 5:00 PM Richard Guo <guofenglinux(at)gmail(dot)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 Content-Type Size
v1-0001-Fix-ParamPathInfo-for-AppendPath.patch application/octet-stream 4.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2022-12-12 10:14:02 Re: [PoC] Improve dead tuple storage for lazy vacuum
Previous Message Antonin Houska 2022-12-12 09:44:39 Re: refactor ExecGrant_*() functions