From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Is this an oversight in reparameterizing Memoize path? |
Date: | 2022-12-02 15:13:30 |
Message-ID: | 1932256.1669994010@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Richard Guo <guofenglinux(at)gmail(dot)com> writes:
> When reviewing other patch I noticed there might be an oversight for
> MemoizePath in reparameterize_path. In reparameterize_path we are
> supposed to increase the path's parameterization to required_outer.
> However, AFAICS for MemoizePath we just re-create the same path thus its
> parameterization does not get increased.
Yeah, that sure looks wrong. At minimum we should be recursively
fixing the subpath. (It looks like doing that and re-calling
create_memoize_path might be sufficient.)
According to [1] our code coverage for reparameterize_path is just
awful. MemoizePath in reparameterize_pathlist_by_child isn't
tested either ...
regards, tom lane
[1] https://coverage.postgresql.org/src/backend/optimizer/util/pathnode.c.gcov.html
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2022-12-02 15:18:48 | Re: [PATCH] Check snapshot argument of index_beginscan and family |
Previous Message | Alexander Korotkov | 2022-12-02 15:12:37 | Re: [PATCH] Allow specification of custom slot for custom nodes |