Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
From: "Daniel Verite" <daniel@manitou-mail.org>
Subject: Re: Add Pipelining support in psql
To: "Michael Paquier" <michael@paquier.xyz>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>,
 Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>,
 PostgreSQL Hackers <pgsql-hackers@postgresql.org>
In-Reply-To: <Z9or5qJwixm_PDC-@paquier.xyz>
Date: Wed, 19 Mar 2025 14:05:34 +0100
Message-Id: <f873e847-8e9b-4257-8eca-66ec35b03f4d@manitou-mail.org>
Archived-At: 
 <https://www.postgresql.org/message-id/f873e847-8e9b-4257-8eca-66ec35b03f4d%40manitou-mail.org>
Precedence: bulk

	Michael Paquier wrote:

> Perhaps an \extended command that behaves outside a pipeline makes
> sense to force the use of queries without parameters to use the
> extended mode, but I cannot get much excited about the concept knowing
> all the meta-commands we have now (not talking about the pipeline
> part, which is different, as we can treat queries in batches).

When psql started supporting the extended query protocol, the question
of enabling it more globally rather than query-by-query was discussed
a bit [1]. The idea was to switch to it with a setting or a variable
rather than a metacommand.
Some pros and cons were mentioned in the thread, but on the whole
it was not convincing enough to get implemented.

[1]
https://www.postgresql.org/message-id/e8dd1cd5-0e04-3598-0518-a605159fe314%=
40enterprisedb.com


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