Re: postgres_fdw: wrong results with self join + enable_nestloop off

Поиск
Список
Период
Сортировка
От Richard Guo
Тема Re: postgres_fdw: wrong results with self join + enable_nestloop off
Дата
Msg-id CAMbWs4-XR1r+embqYsGHtqstBeJ73GCGVBUty0WsWksUazjttA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: postgres_fdw: wrong results with self join + enable_nestloop off  (Etsuro Fujita <etsuro.fujita@gmail.com>)
Ответы Re: postgres_fdw: wrong results with self join + enable_nestloop off  (Nishant Sharma <nishant.sharma@enterprisedb.com>)
Re: postgres_fdw: wrong results with self join + enable_nestloop off  (Etsuro Fujita <etsuro.fujita@gmail.com>)
Список pgsql-hackers

On Mon, Jun 5, 2023 at 9:19 PM Etsuro Fujita <etsuro.fujita@gmail.com> wrote:
If the patch is intended for HEAD only, I also think it goes in the
right direction.  But if it is intended for back branches as well, I
do not think so, because it would cause ABI breakage due to changes
made to the ForeignPath struct and the create_foreign_join_path() API.
(For the former, I think we could avoid doing so by adding the new
member at the end of the struct, not in the middle, though.)

Thanks for pointing this out.  You're right.  The patch has backport
issue because of the ABI breakage.  So it can only be applied on HEAD.
 
To avoid this issue, I am wondering if we should modify
add_paths_to_joinrel() in back branches so that it just disallows the
FDW to consider pushing down joins when the restrictlist has
pseudoconstant clauses.  Attached is a patch for that.

I think we can do that in back branches.  But I'm a little concerned
that we'd miss a better plan if FDW cannot push down joins in such
cases.  I may be worrying over nothing though if it's not common that
the restrictlist has pseudoconstant clauses.

Thanks
Richard

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Vik Fearing
Дата:
Сообщение: Add support for AT LOCAL
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: Implement generalized sub routine find_in_log for tap test