Re: Prepared SQL name collision. The name implicitly is truncated by NAMEDATALEN - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Prepared SQL name collision. The name implicitly is truncated by NAMEDATALEN
Date
Msg-id 909619.1684850832@sss.pgh.pa.us
Whole thread Raw
In response to Prepared SQL name collision. The name implicitly is truncated by NAMEDATALEN  (Alexey Kachalin <kachalin.alexey@gmail.com>)
Responses Re: Prepared SQL name collision. The name implicitly is truncated by NAMEDATALEN  (Alexey Kachalin <kachalin.alexey@gmail.com>)
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Dippu Kumar
Date:
Subject: Re: Need Support to Upgrade from 13.6 to 15.3
Next
From: Peter Eisentraut
Date:
Subject: Re: AW: AW: BUG #17923: Excessive warnings of collation version mismatch in logs