Message-ID: <5c247f374cd29995f4161d02ed104c1052660509.camel@cybertec.at>
Subject: Re: pass open cursor via USING in execute staement
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: domenico.l76@gmail.com, pgsql-docs@lists.postgresql.org
Date: Thu, 01 Jun 2023 16:23:44 +0200
In-Reply-To: 
 <168557387260.1230014.3975398352224062825@wrigleys.postgresql.org>
References: 
	<168557387260.1230014.3975398352224062825@wrigleys.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4 (3.46.4-1.fc37) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/5c247f374cd29995f4161d02ed104c1052660509.camel%40cybertec.at>
Precedence: bulk

On Wed, 2023-05-31 at 22:57 +0000, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/15/plpgsql-statements.html
>=20
> Should be documented if this statement is allowed or not (if not, maybe s=
et
> as desired feature :-) )
>=20
> EXECUTE format('update %I set col1=3D$1, col2=3Dnow() WHERE current of $3=
',
> tabname)
> =C2=A0=C2=A0 USING myVal, myOpenCursor;

That is not supported.  Parameters can only be used in a place where consta=
nts
(SQL literals) might appear, not instead of identifiers (names of tables, c=
olumns etc.)

I looked, and that is really not documented anywhere.
One of PREPARE or the extended query protocol might be good places.

Yours,
Laurenz Albe