Re: Add semi-join pushdown to postgres_fdw - Mailing list pgsql-hackers

From Alexander Pyhalov
Subject Re: Add semi-join pushdown to postgres_fdw
Date
Msg-id c266bb209089a93bdcd61f6c4a4bfb42@postgrespro.ru
Whole thread Raw
In response to Re: Add semi-join pushdown to postgres_fdw  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Add semi-join pushdown to postgres_fdw
List pgsql-hackers
Alexander Korotkov писал(а) 2025-03-18 03:27:
> Hi, Robins!
> 
> On Tue, Mar 18, 2025 at 2:20 AM Robins Tharakan <tharakan@gmail.com> 
> wrote:
>> On Mon, 4 Dec 2023 at 07:22, Alexander Korotkov <aekorotkov@gmail.com> 
>> wrote:
>> >
>> >
>> > Now, I think this looks good.  I'm going to push this if no objections.
>> 
>> After this commit, I began seeing an unexpected ERROR - see this 
>> bug-report.
>> https://www.postgresql.org/message-id/18852-fb75b88160678f78%40postgresql.org
> 
> Thank you for pointing.
> I'll check this in the next couple of days.
> 

Hi.
It seems conditions, coming from semi-joins, are handled incorrectly 
under left and right join. When deparsing left/right joins and there are 
semi-joins in inner or outer part of the query, the corresponding part 
is deparsed as subquery. And we can't refer subquery vars from above, so 
just should not pull up the restrictinfos. The attached patch does 
exactly this.
-- 
Best regards,
Alexander Pyhalov,
Postgres Professional
Attachment

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Index AM API cleanup
Next
From: Xuneng Zhou
Date:
Subject: Re: Fwd: [BUG]: the walsender does not update its IO statistics until it exits