Re: foreign join error "variable not found in subplan target list"
Richard Guo <guofenglinux@gmail.com>
From: Richard Guo <guofenglinux@gmail.com>
To: Etsuro Fujita <etsuro.fujita@gmail.com>
Cc: Alexander Pyhalov <a.pyhalov@postgrespro.ru>, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Date: 2022-08-29T09:45:50Z
Lists: pgsql-bugs
On Mon, Aug 29, 2022 at 2:17 PM Etsuro Fujita <etsuro.fujita@gmail.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
Commits
-
postgres_fdw: Avoid 'variable not found in subplan target list' error.
- d4adff0e97f0 10.23 landed
- 07d81d1e5b75 11.18 landed
- 87fd3c9025da 12.13 landed
- 6749d4e8c71b 13.9 landed
- b53d104ae3b9 14.6 landed
- 64387c540805 15.0 landed
- 9320cfdd06e5 16.0 landed