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

From: Nishant Sharma <nishant(dot)sharma(at)enterprisedb(dot)com>
To: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
Cc: Suraj Kharage <suraj(dot)kharage(at)enterprisedb(dot)com>, Richard Guo <guofenglinux(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: postgres_fdw: wrong results with self join + enable_nestloop off
Date: 2023-06-21 09:46:42
Message-ID: CADrsxdY5BmApKSxSEODuswDQL8M1+eY-6R=ZyiyT=PoLOthVOA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Looks good to me. Tested on master and it works.
New patch used a bool flag to avoid calls for both FDW and custom hook's
call. And a slight change in comment of "has_pseudoconstant_clauses"
function.

Regards,
Nishant.

On Wed, Jun 14, 2023 at 12:19 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
wrote:

> On Mon, Jun 5, 2023 at 10: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 that custom scans have the same issue, so I modified the patch
> further so that it also disallows custom-scan providers to consider
> join pushdown in add_paths_to_joinrel() if necessary. Attached is a
> new version of the patch.
>
> Best regards,
> Etsuro Fujita
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-06-21 10:12:12 Re: [BUG] recovery of prepared transactions during promotion can fail
Previous Message Julian Markwort 2023-06-21 09:11:55 Re: [BUG] recovery of prepared transactions during promotion can fail