| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
| Cc: | Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: foreign join error "variable not found in subplan target list" |
| Date: | 2022-08-29 09:45:50 |
| Message-ID: | CAMbWs4-c8yC-4bfWt0HPgocUNwg7f_ZMSMYgMjm6bSV=PDNX8Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Aug 29, 2022 at 2:17 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
wrote:
> One thing I noticed while re-reading the patch is that we should use
> create_projection_path() here, to avoid modifying the epq_path in
> place, as it is already used for an unsorted join-pushdown path before
> we get here. So I modified the patch as such. Updated patch
> attached.
The new change looks reasonable to me as there is other ref to this
epq_path.
I'm looking again on how we adjust the PathTarget, and I think we may
need to update the cost and width fields if there are any new columns
added. Maybe we can leverage set_pathtarget_cost_width for that.
Thanks
Richard
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-08-29 13:38:39 | Re: BUG #17598: EXTENSION can no longer create it's own schema! (Create Schema IF NOT EXISTS XXX) |
| Previous Message | PG Bug reporting form | 2022-08-29 08:54:59 | BUG #17600: Not able to install PostgreSql in my laptop |