Re: Prepared SQL name collision. The name implicitly is truncated by NAMEDATALEN

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alexey Kachalin <kachalin(dot)alexey(at)gmail(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Prepared SQL name collision. The name implicitly is truncated by NAMEDATALEN
Date: 2023-05-23 14:07:12
Message-ID: 909619.1684850832@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alexey Kachalin <kachalin(dot)alexey(at)gmail(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2023-05-23 16:18:55 Re: AW: AW: BUG #17923: Excessive warnings of collation version mismatch in logs
Previous Message Dippu Kumar 2023-05-23 11:20:39 Re: Need Support to Upgrade from 13.6 to 15.3