NAMEDATALEN increase because of non-latin languages

From: Денис Романенко <deromanenko(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: NAMEDATALEN increase because of non-latin languages
Date: 2021-08-18 11:07:46
Message-ID: CALSd-crdmj9PGdvdioU=a5W7P=TgNmEB2QP9wiF6DTUbBuMXrQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello dear hackers. I understand the position of the developers community
about NAMEDATALEN length - and, in fact, 63 bytes is more than enough - but
only if we speak about latin languages.

Postgresql has wonderful support for unicode in table and column names. And
it looks like very good idea to create table with names on native language
for databases across the world. But when I want to create, for example,
table with name "Catalog_Контрагенты_КонтактнаяИнформация" (that stands in
Russian for catalog of counteragent contacts) it will be auto-shrinked to
"Catalog_Контрагенты_КонтактнаяИнформ". And this is not a fictional problem
- many words in Russian are just longer than it's English counterparts and
I have many examples like this.

Although recompiling the source is not so hard, updating is hard. I know
that is not free for disk space because of storing table names and field
names but, from my point of view, in 2021 year convenience is more
important than disk space.

I ask you to consider increasing NAMEDATALEN for maybe 128 bytes in future
releases.

Sorry for wasted time for this message if this topic is not match with
direction of postgresql development (and thank you for your hard work)

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2021-08-18 11:15:37 Re: NAMEDATALEN increase because of non-latin languages
Previous Message Ranier Vilela 2021-08-18 11:06:18 Re: Fix uninitialized variable access (src/backend/utils/mmgr/freepage.c)