Re: Function scan FDW pushdown

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Alexander Pyhalov <a(dot)pyhalov(at)postgrespro(dot)ru>
Cc: solaimurugan vellaipandiyan <drsolaimurugan(dot)v(at)gmail(dot)com>, Álvaro Herrera <alvherre(at)kurilemu(dot)de>, g(dot)kashkin(at)postgrespro(dot)ru, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Function scan FDW pushdown
Date: 2026-08-15 00:49:23
Message-ID: CAPpHfdv99rqDdZOmo6onNaFkvW_ETj0yVW90yRpNxVtM1iFgWg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

> Hi. I've updated comment a bit, as we currently have to handle NULL
> records correctly,
> this is not a nice-to-have feature which we need for future changes to
> be more safe.

Thank you. I've further improved that comment. Also, I've revised the
cost calculation in init_func_stub_fpinfo() to reflect the cost of the
function execution on the remote side. I have to edit the regression
test query to reliably exercise the pushdown.

------
Regards,
Alexander Korotkov
Supabase

Attachment Content-Type Size
v14-0001-postgres_fdw-push-down-FUNCTION-RTE-into-foreign.patch application/octet-stream 87.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2026-08-15 01:08:01 Re: Optimize UUID parse using SIMD
Previous Message Alexander Korotkov 2026-08-15 00:01:17 Re: Implement waiting for wal lsn replay: reloaded