Horton
Menu

Re: Add semi-join pushdown to postgres_fdw

Alexander Korotkov <aekorotkov@gmail.com>

View thread
From: Alexander Korotkov <aekorotkov@gmail.com>
To: Robins Tharakan <tharakan@gmail.com>
Cc: Alexander Pyhalov <a.pyhalov@postgrespro.ru>, Tomas Vondra <tomas.vondra@enterprisedb.com>, "Fujii.Yuki@df.MitsubishiElectric.co.jp" <Fujii.Yuki@df.mitsubishielectric.co.jp>, Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>, Ian Lawrence Barwick <barwick@gmail.com>, "tndrwang@gmail.com" <tndrwang@gmail.com>
Date: 2025-03-18T00:27:35Z
Lists: pgsql-hackers 
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.

------
Regards,
Alexander Korotkov
Supabase

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. postgres_fdw: Avoid pulling up restrict infos from subqueries

  2. Add support for deparsing semi-joins to contrib/postgres_fdw

  3. Move PartitioPruneInfo out of plan nodes into PlannedStmt