From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexey Kachalin <kachalin.alexey@gmail.com>
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Prepared SQL name collision. The name implicitly is truncated by
 NAMEDATALEN
In-reply-to: 
 <CAF9fLqtmtPqjLD06gnxFB_oLtx7SKm-gAe+7JNzXQG5iRb=utA@mail.gmail.com>
References: 
 <CAF9fLqtmtPqjLD06gnxFB_oLtx7SKm-gAe+7JNzXQG5iRb=utA@mail.gmail.com>
Comments: In-reply-to Alexey Kachalin <kachalin.alexey@gmail.com>
	message dated "Tue, 23 May 2023 08:00:11 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <909618.1684850832.1@sss.pgh.pa.us>
Date: Tue, 23 May 2023 10:07:12 -0400
Message-ID: <909619.1684850832@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/909619.1684850832%40sss.pgh.pa.us>
Precedence: bulk

Alexey Kachalin <kachalin.alexey@gmail.com> writes:
> Prepared SQL name collision.  The name implicitly is truncated by
> NAMEDATALEN

This is not a bug.  You exceeded a well-documented implementation
limit, and the response is as documented.

> Is it possible to know which value was used at compilation time from
> application code?

You can do

=# show max_identifier_length;
 max_identifier_length 
-----------------------
 63
(1 row)

or various equivalent ways of inspecting that parameter.

			regards, tom lane