Re: Add semi-join pushdown to postgres_fdw

Robins Tharakan <tharakan@gmail.com>

From: Robins Tharakan <tharakan@gmail.com>

To: Alexander Korotkov <aekorotkov@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:20:21Z

Lists: pgsql-hackers

Hi Alexander,

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

-
robins
https://robins.in

Ref:
1.
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=824dbea3e41efa3b35094163c834988dea7eb139

Commits

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

postgres_fdw: Avoid pulling up restrict infos from subqueries
- 729fe699e612 17.5 landed
- 023fb512755f 18.0 landed
Add support for deparsing semi-joins to contrib/postgres_fdw
- 824dbea3e41e 17.0 landed
Move PartitioPruneInfo out of plan nodes into PlannedStmt
- ec386948948c 16.0 cited