Re: psql: Add command to use extended query protocol - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: psql: Add command to use extended query protocol
Date
Msg-id 202309150951.ra73w7vww3tj@alvherre.pgsql
Whole thread Raw
In response to Re: psql: Add command to use extended query protocol  (Tobias Bussmann <t.bussmann@gmx.net>)
Responses Re: psql: Add command to use extended query protocol
List pgsql-hackers
On 2023-Sep-14, Tobias Bussmann wrote:

> In one of my environments, this feature didn't work as expected.
> Digging into it, I found that it is incompatible with FETCH_COUNT
> being set. Sorry for not recognising this during the betas.
> 
> Attached a simple patch with tests running the cursor declaration
> through PQexecParams instead of PGexec.

Hmm, strange.  I had been trying to make \bind work with extended
protocol, and my findings were that there's interactions with the code
that was added for pipeline mode(*).  I put research aside to work on
other things, but intended to get back to it soon ... I'm really
surprised that it works for you here.

Maybe your tests are just not extensive enough to show that it fails.

(*) This is not actually proven, but Peter had told me that his \bind
stuff had previously worked when he first implemented it before pipeline
landed.  Because that's the only significant change that has happened to
the libpq code lately, it's a reasonable hypothesis.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"No deja de ser humillante para una persona de ingenio saber
que no hay tonto que no le pueda enseñar algo." (Jean B. Say)



pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: pgBufferUsage.blk_{read|write}_time are zero although there are pgBufferUsage.local_blks_{read|written}
Next
From: Daniel Gustafsson
Date:
Subject: Re: Improve the log message output of basic_archive when basic_archive.archive_directory parameter is not set