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-17 09:42:15
Message-ID: CAPpHfdubqtP-hMGO7rstR2iUCdq=jOWwy=9p0cdJZHi0BMpJoQ@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

On Mon, Aug 17, 2026 at 9:57 AM Alexander Pyhalov
<a(dot)pyhalov(at)postgrespro(dot)ru> wrote:
>
> Alexander Korotkov писал(а) 2026-08-15 03:49:
> > 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
>
> Hi.
> Looks good to me.

Good. I'm going to push this if no objections.

------
Regards,
Alexander Korotkov
Supabase

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Junwang Zhao 2026-08-17 09:45:48 Re: Allow table AMs to define their own reloptions
Previous Message Junwang Zhao 2026-08-17 09:40:43 Re: Allow table AMs to define their own reloptions