Horton

Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx

Peter Eisentraut <peter@eisentraut.org>

View thread View on postgr.es
From: Peter Eisentraut <peter@eisentraut.org>
To: Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>, Michael Paquier <michael@paquier.xyz>
Cc: Jelte Fennema-Nio <postgres@jeltef.nl>, Greg Sabino Mullane <htamfids@gmail.com>, vignesh C <vignesh21@gmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2025-06-23T13:25:32Z
Lists: pgsql-hackers 
On 23.06.25 09:04, Anthonin Bonnefoy wrote:
> On Thu, Jun 19, 2025 at 9:09 AM Michael Paquier <michael@paquier.xyz> wrote:
>> Good point.  I would be on board with a \close_prepared then, if
>> that's the consensus we reach, without touching at \bind_named.  We
>> still have time to decide on the name until the release, just let's
>> make sure to not do a rename multiple times.
> 
> True. That would also allow adding a \close_cursor meta-command
> without name ambiguity.
> 
> Since the consensus seems to lean toward \close_prepared, I've
> prepared the patch to rename the command.

Looks good to me, thanks.

Commits

  1. psql: Rename meta-command \close to \close_prepared

  2. psql: Add tests for repeated calls of \bind[_named]

  3. psql: Fix memory leak with repeated calls of \bind

  4. psql: Clean up more aggressively state of \bind[_named], \parse and \close

  5. psql: Add more meta-commands able to use the extended protocol

  6. psql: Add ignore_slash_options in bind's inactive branch