MIME-Version: 1.0
From: Flavio Henrique Araque Gurgel <fhagur@gmail.com>
Date: Tue, 28 Aug 2018 16:26:30 +0200
Message-ID: 
 <CAGHTAeOxqeojgvWEuciRvq1xbZYHKK6mGzs=g2rQ8upM3mwVWA@mail.gmail.com>
Subject: Limitation of prepared statement name
To: pgsql-docs@postgresql.org
Content-Type: multipart/alternative; boundary="0000000000006bc3bd05747fa108"
Precedence: bulk

--0000000000006bc3bd05747fa108
Content-Type: text/plain; charset="UTF-8"

Hello all

I just found a limitation in prepared statements names that I didn't know
before and can lead applications to be difficult to debug.

It seems that naming prepared statements is limited to 63 characters as per
https://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS

However, the documentation for PREPARE says nothing about it
https://www.postgresql.org/docs/10/static/sql-prepare.html

The dangerous situation is that PostgreSQL seems to ignore rigthmost
overflowed characters silently. If we try to prepare another statement with
the same 63 leftmost characters as the first one, we get an error of
duplicate prepared statement name.

Wouldn't it be good to include that information on the prepared statement
doc page? Maybe I should notify this as a general bug so we treat this at
the code level.

Best,
Flavio Gurgel

--0000000000006bc3bd05747fa108
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hello all</div><div><br></div><div>I just found a lim=
itation in prepared statements names that I didn&#39;t know before and can =
lead applications to be difficult to debug.</div><div><br></div><div>It see=
ms that naming prepared statements is limited to 63 characters as per<a hre=
f=3D"https://www.postgresql.org/docs/current/static/sql-syntax-lexical.html=
#SQL-SYNTAX-IDENTIFIERS"> https://www.postgresql.org/docs/current/static/sq=
l-syntax-lexical.html#SQL-SYNTAX-IDENTIFIERS</a></div><div><br></div><div>H=
owever, the documentation for PREPARE says nothing about it <a href=3D"http=
s://www.postgresql.org/docs/10/static/sql-prepare.html">https://www.postgre=
sql.org/docs/10/static/sql-prepare.html</a></div><div><br></div><div>The da=
ngerous situation is that PostgreSQL seems to ignore rigthmost overflowed c=
haracters silently. If we try to prepare another statement with the same 63=
 leftmost characters as the first one, we get an error of duplicate prepare=
d statement name.</div><div><br></div><div>Wouldn&#39;t it be good to inclu=
de that information on the prepared statement doc page? Maybe I should noti=
fy this as a general bug so we treat this at the code level.</div><div><br>=
</div><div>Best,</div><div>Flavio Gurgel<br></div><div><br></div></div>

--0000000000006bc3bd05747fa108--