Re: psql: Add command to use extended query protocol

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Jehan-Guillaume de Rorthais <jgdr(at)dalibo(dot)com>
Cc: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql: Add command to use extended query protocol
Date: 2022-11-02 12:55:22
Message-ID: CAFj8pRCh8UQ6_5WP=e2t8b5HsLTJf92TAYZH2FNyrLQULSTS9A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

st 2. 11. 2022 v 13:43 odesílatel Jehan-Guillaume de Rorthais <
jgdr(at)dalibo(dot)com> napsal:

> Hi,
>
> On Fri, 28 Oct 2022 08:52:51 +0200
> Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> wrote:
>
> > This adds a new psql command \gp that works like \g (or semicolon) but
> > uses the extended query protocol. Parameters can also be passed, like
> >
> > SELECT $1, $2 \gp 'foo' 'bar'
>
> As I wrote in my TCE review, would it be possible to use psql vars to set
> some
> named parameters for the prepared query? This would looks like:
>
> \set p1 foo
> \set p2 bar
> SELECT :'p1', :'p2' \gp
>
> This seems useful when running psql script passing it some variables using
> -v arg. It helps with var position, changing some between exec, repeating
> them
> in the query, etc.
>
> Thoughts?
>

I don't think it is possible. The variable evaluation is done before
parsing the backslash command.

Regards

Pavel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-11-02 13:06:02 Re: Allow file inclusion in pg_hba and pg_ident files
Previous Message Jehan-Guillaume de Rorthais 2022-11-02 12:43:27 Re: psql: Add command to use extended query protocol