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
Date: Tue, 23 May 2023 10:07:12 -0400
Message-ID: <909619.1684850832@sss.pgh.pa.us> (raw)
In-Reply-To: <CAF9fLqtmtPqjLD06gnxFB_oLtx7SKm-gAe+7JNzXQG5iRb=utA@mail.gmail.com>
References: <CAF9fLqtmtPqjLD06gnxFB_oLtx7SKm-gAe+7JNzXQG5iRb=utA@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, kachalin.alexey@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: Prepared SQL name collision. The name implicitly is truncated by NAMEDATALEN
In-Reply-To: <909619.1684850832@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox