Re: pipelining in psql, commit 41625ab

From: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pipelining in psql, commit 41625ab
Date: 2025-04-15 22:00:19
Message-ID: CAGECzQS__HmHXWqkZ6eBDdSE4HF7tpDf44WDA959p69oPrAcXg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 15 Apr 2025 at 23:34, Noah Misch <noah(at)leadboat(dot)com> wrote:
> That said, maybe having
> PQpipelineSync() was a mistake, since I think it's just PQsendPipelineSync() +
> PQflush().

Yes, IMO that's pretty much the case. But we cannot remove that
function because of backwards compatibility.

Note that for all the other commands (e.g \bind, \close, \parse) we
use the send variant of the libpq function too without including send
in the command. However, send means a different thing for those: If
you use the non-send one you get a PGresult back.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ilia Evdokimov 2025-04-15 22:09:20 Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment
Previous Message Jelte Fennema-Nio 2025-04-15 21:38:35 Re: [PoC] Federated Authn/z with OAUTHBEARER