From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
        Alexey Bashtanov <bashtanov@imap.cc>,
 Franck Verrot <franck@verrot.fr>,
        pgsql-hackers@postgresql.org
Subject: Re: [PATCH]: Allow errors in parameter values to be reported during
 the BIND phase itself..
In-reply-to: <20210104170939.GH9712@telsasoft.com>
References: <20210104170939.GH9712@telsasoft.com>
Comments: In-reply-to Justin Pryzby <pryzby@telsasoft.com>
	message dated "Mon, 04 Jan 2021 11:09:39 -0600"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3087633.1615848349.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 15 Mar 2021 18:45:49 -0400
Message-ID: <3087634.1615848349@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3087634.1615848349%40sss.pgh.pa.us>
Precedence: bulk

Justin Pryzby <pryzby@telsasoft.com> writes:
> For example:
> $ python3.5 -c "import pg; db=3Dpg.DB(); q =3D db.query(\"SET log_parame=
ter_max_length_on_error=3D-1;\"); db.prepare('p', 'SELECT \$1::smallint');=
 db.query_prepared('p',66666);"
> 2021-01-03 02:21:04.547 CST [20157] ERROR:  value "66666" is out of rang=
e for type smallint
> 2021-01-03 02:21:04.547 CST [20157] CONTEXT:  unnamed portal with parame=
ters: $1 =3D '66666'
> 2021-01-03 02:21:04.547 CST [20157] STATEMENT:  SELECT $1::smallint

> When there are many bind params, this can be useful to determine which i=
s out
> of range.  Think 900 int/smallint columns, or less-wide tables being ins=
erted
> multiple rows at a time with VALUES(),(),()...

> Of course, this isn't as good as showing the column name, so I might pur=
sue
> Tom's suggestion for that at some point.

I started to look at this, and immediately began to wonder where is the
previous discussion you're evidently referring to.  Can you dig up an
archives link?

			regards, tom lane