Re: Add semi-join pushdown to postgres_fdw

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru>
Cc: Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, "Fujii(dot)Yuki(at)df(dot)MitsubishiElectric(dot)co(dot)jp" <Fujii(dot)Yuki(at)df(dot)mitsubishielectric(dot)co(dot)jp>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Ian Lawrence Barwick <barwick(at)gmail(dot)com>
Subject: Re: Add semi-join pushdown to postgres_fdw
Date: 2024-02-12 02:27:14
Message-ID: CAPpHfdsgBv+O9NL6sE=ifJY=6uvdbLLgknPp9UqwELAiDjjPwQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi, Pavel!

On Fri, Feb 9, 2024 at 10:08 PM Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> wrote:
> But optimization not used for NOT EXISTS:

Right, anti-joins are not supported yet.

> Also, optimization not used after deleting first condition (a.aircraft_code = '320'):

This is a costing issue. Optimization worlds for me when set
"use_remote_estimate = true" for the server;

> But the worst thing is that replacing AND with OR causes breaking session and server restart:

I haven't managed to reproduce this yet. Could you give more details:
machine, OS, compile options, backtrace?

------
Regards,
Alexander Korotkov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2024-02-12 02:29:46 Re: Improve documentation of upgrade for streaming replication section.
Previous Message Ashutosh Bapat 2024-02-12 01:22:24 Re: Printing backtrace of postgres processes