From: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> |
---|---|
To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
Cc: | Nishant Sharma <nishant(dot)sharma(at)enterprisedb(dot)com>, Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: postgres_fdw: wrong results with self join + enable_nestloop off |
Date: | 2023-06-08 10:30:52 |
Message-ID: | CAPmGK16J-0OwjJejs629D_rwZzwB=1H5P7i7SJbw0BfEcguxQA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Richard,
On Tue, Jun 6, 2023 at 12:20 PM Richard Guo <guofenglinux(at)gmail(dot)com> wrote:
> On Mon, Jun 5, 2023 at 9:19 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
>> 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.
Yeah, it is unfortunate that we would not get better plans. Given
that it took quite a long time to find this issue, I suppose that
users seldom do foreign joins with pseudoconstant clauses, though.
Anyway thanks for working on this, Richard!
Best regards,
Etsuro Fujita
From | Date | Subject | |
---|---|---|---|
Next Message | Etsuro Fujita | 2023-06-08 10:36:48 | Re: postgres_fdw: wrong results with self join + enable_nestloop off |
Previous Message | Amit Kapila | 2023-06-08 10:29:38 | Re: running logical replication as the subscription owner |