Re: psql: Add command to use extended query protocol

Peter Eisentraut <peter.eisentraut@enterprisedb.com>

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

To: Corey Huinker <corey.huinker@gmail.com>

Cc: pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2022-11-22T15:51:27Z

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 21.11.22 23:02, Corey Huinker wrote:
> I got thinking about this, and while things may be fine as-is, I would 
> like to hear some opinions as to whether this behavior is correct:

This is all psql syntax, nothing specific to this command.  The only 
leeway is choosing the appropriate enum slash_option_type, but the 
choices other than OT_NORMAL don't seem to be particularly applicable to 
this.