Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx
Date
Msg-id Zah-54B6fXv9JGXs@paquier.xyz
Whole thread Raw
In response to Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx  (Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>)
Responses Re: [PATCH] Add additional extended protocol commands to psql: \parse and \bindx
List pgsql-hackers
On Wed, Jan 17, 2024 at 10:05:33AM +0100, Anthonin Bonnefoy wrote:
> > I do realize the same is true for plain \bind, but it seems
> > like a bug there too.
>
> The unscanned bind's parameters are discarded later in the
> HandleSlashCmds functions. So adding the ignore_slash_options() for
> inactive branches scans and discards them earlier. I will add it to
> match what's done in the other commands but I don't think it's
> testable as the behaviour is the same unless I miss something.

Hmm.  So it does not lead to any user-visible changes, right?  I can
get your argument about being consistent in the code across the board
for all the backslash commands, though.

> I did add the \bind, \bindx, \close and \parse to the inactive branch
> tests to complete the list.

Could you split the bits for \bind into a separate patch, please?
This requires a separate evaluation, especially if this had better be
backpatched.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Show WAL write and fsync stats in pg_stat_io
Next
From: Masahiko Sawada
Date:
Subject: Re: [PoC] Improve dead tuple storage for lazy vacuum