From: Tom Lane <tgl@sss.pgh.pa.us>
To: Flavio Henrique Araque Gurgel <fhagur@gmail.com>
cc: pgsql-docs@postgresql.org
Subject: Re: Limitation of prepared statement name
In-reply-to: 
 <CAGHTAeOxqeojgvWEuciRvq1xbZYHKK6mGzs=g2rQ8upM3mwVWA@mail.gmail.com>
References: 
 <CAGHTAeOxqeojgvWEuciRvq1xbZYHKK6mGzs=g2rQ8upM3mwVWA@mail.gmail.com>
Comments: In-reply-to Flavio Henrique Araque Gurgel <fhagur@gmail.com>
	message dated "Tue, 28 Aug 2018 16:26:30 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <28415.1535473275.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Tue, 28 Aug 2018 12:21:15 -0400
Message-ID: <28416.1535473275@sss.pgh.pa.us>
Precedence: bulk

Flavio Henrique Araque Gurgel <fhagur@gmail.com> writes:
> It seems that naming prepared statements is limited to 63 characters as =
per
> https://www.postgresql.org/docs/current/static/sql-syntax-lexical.html#S=
QL-SYNTAX-IDENTIFIERS

Yeah, just like every other SQL identifier in Postgres...

> The dangerous situation is that PostgreSQL seems to ignore rigthmost
> overflowed characters silently.

It's hardly silent:

regression=3D# prepare foo123456789012345678901234567890123456789012345678=
9012345678901234567890 as select 1;
NOTICE:  identifier "foo12345678901234567890123456789012345678901234567890=
12345678901234567890" will be truncated to "foo123456789012345678901234567=
890123456789012345678901234567890"
PREPARE

> Wouldn't it be good to include that information on the prepared statemen=
t
> doc page?

You could as well argue that every single page that describes creating
any sort of object ought to repeat this information.  I doubt that people
would find that to be an improvement.

			regards, tom lane