Re: psql: Add command to use extended query protocol

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>

To: Daniel Verite <daniel@manitou-mail.org>, "David G. Johnston" <david.g.johnston@gmail.com>

Cc: Pavel Stehule <pavel.stehule@gmail.com>, Corey Huinker <corey.huinker@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>, Pgsql-Hackers <pgsql-hackers@postgresql.org>

Date: 2022-11-08T12:39:14Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

psql: Add command to use extended query protocol
- 5b66de3433e2 16.0 landed

On 08.11.22 13:02, Daniel Verite wrote:
>> A pset variable to control the default seems reasonable as well.
>> The implication would be that if you set that pset variable there is
>> no way to have individual commands use simple query mode directly.
> +1 except that it would be a \set variable for consistency with the
> other execution-controlling variables. \pset variables control only
> the display.

Is there a use case for a global setting?

It seems to me that that would be just another thing that a 
super-careful psql script would have to reset to get a consistent 
starting state.