| From: | Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Yilin Zhang <jiezhilove(at)126(dot)com>, KENAN YILMAZ <kenan(dot)yilmaz(at)localus(dot)com(dot)tr>, Andy Fan <zhihuifan1213(at)163(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Bypassing cursors in postgres_fdw to enable parallel plans |
| Date: | 2026-09-03 08:25:10 |
| Message-ID: | CA+FpmFdTSEXO7PCyJmEHhPac0WnMC05RWBW8oUwU0zUDjtg-5A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 2 Sept 2026 at 21:14, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> wrote:
> On Wed, 2 Sept 2026 at 13:49, Rafia Sabih <rafia(dot)pghackers(at)gmail(dot)com>
> wrote:
> > Please find the reworked patchset in the attachment.
> > Looking forward to your feedback on this one.
>
> I tried this patch out with the "postgres compatible" endpoint I built
> for MotherDuck[1]. DuckDB (currently) doesn't support cursors, so that
> is blocking us from supporting postgres_fdw. With this patchset (and a
> few small bugfixes on my side) I was able to get it to work with
> motherduck its postgres endpoint.
>
> [1]: https://motherduck.com/blog/motherduck-now-speaks-postgres/
>
> P.S. I did not review any of the code.
>
Interesting!
Thank you for sharing this information. I am happy to see that the work is
already useful.
--
Regards,
Rafia Sabih
CYBERTEC PostgreSQL International GmbH
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Osama Abdul Qader | 2026-09-03 08:26:59 | Re: REPACK (ANALYZE) within transaction block segfaults |
| Previous Message | Xuneng Zhou | 2026-09-03 08:09:51 | Re: WAIT FOR NO_THROW option could use some documentation |