Re: Support named (destination) portals in extended proto for psql meta commands.

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Kirill Reshke <reshkekirill(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Support named (destination) portals in extended proto for psql meta commands.
Date: 2025-12-13 10:33:51
Message-ID: CAGECzQRG35g_6MuNgTq+2P+NTpupM8kq9zvxR3L4M2Ovhx1hQw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, 13 Dec 2025 at 09:56, Kirill Reshke <reshkekirill(at)gmail(dot)com> wrote:
> And I faced a problem, that there is no way to test
> extended query bind commands for non-empty destination portal. So, I
> propose to add a psql meta command just for that purpose. Something
> like \bind_cursor CURSOR_NAME STMT_NAME [params..]

Probably call it bind_portal though. So far we've aligned the meta
command names with the protocol/libpq names (e.g. \parse instead of
\prepare)

> So, sending non-empty portal names was never supported in libpq?
> It makes me think there was a good reason for that. Can somebody
> please clarify on that?

No good reason, just no-one spent the time to implement it. libpq
hasn't implemented most of the somewhat more exotic parts of the
protocol. So yeah, addition is definitely welcome.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2025-12-13 11:00:00 Re: Making jsonb_agg() faster
Previous Message Chao Li 2025-12-13 09:48:13 Re: Remaining dependency on setlocale()