Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: Add Pipelining support in psql
From: "Daniel Verite" <daniel@manitou-mail.org>
To: "Anthonin Bonnefoy" <anthonin.bonnefoy@datadoghq.com>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>,
 Michael Paquier <michael@paquier.xyz>,
 PostgreSQL Hackers <pgsql-hackers@postgresql.org>
In-Reply-To: 
 <CAO6_Xqq4JEHRaGyC=r+dpi0Ejbp2P3aUo-KfR2NuipCvE-o_ZA@mail.gmail.com>
Date: Tue, 18 Mar 2025 10:36:28 +0100
Message-Id: <9aa66158-13c3-4f57-8367-ddf6f392fca7@manitou-mail.org>
Archived-At: 
 <https://www.postgresql.org/message-id/9aa66158-13c3-4f57-8367-ddf6f392fca7%40manitou-mail.org>
Precedence: bulk

	Anthonin Bonnefoy wrote:

> 0002: Allows ';' to send a query using extended protocol when within a
> pipeline by using PQsendQueryParams

It's a nice improvement!

> with 0 parameters. It is not
> possible to send parameters with extended protocol this way and
> everything will be propagated through the query string, similar to a
> simple query.

It's actually possible to use parameters

\startpipeline=20
\bind 'foo'
select $1;
\endpipeline

 ?column?=20
----------
 foo
(1 row)

I suspect there's a misunderstanding that \bind can only be placed
after the query, because it's always written like that in the regression
tests, and in the documentation.
But that's just a notational preference.


Best regards,
--=20
Daniel V=E9rit=E9=20
https://postgresql.verite.pro/