Re: postgres_fdw: wrong results with self join + enable_nestloop off
| От | Etsuro Fujita |
|---|---|
| Тема | Re: postgres_fdw: wrong results with self join + enable_nestloop off |
| Дата | |
| Msg-id | CAPmGK17Gd+hmC2NZF4CzwOZcjv_3ReA4jYgfBKLc4jZLgVW80g@mail.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
Re: postgres_fdw: wrong results with self join + enable_nestloop off |
| Список | pgsql-hackers |
Hi, On Fri, Jun 2, 2023 at 9:31 PM Nishant Sharma <nishant.sharma@enterprisedb.com> wrote: > I also agree that Richard's patch is better. As it fixes the issue at the backend and does not treat pseudoconstant aslocal condition. > > I have tested Richard's patch and observe that it is resolving the problem. Patch looks good to me as well. 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.) 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. My apologies for not reviewing your patch and the long long delay. Best regards, Etsuro Fujita
Вложения
В списке pgsql-hackers по дате отправления: