Re: NAMEDATALEN increase because of non-latin languages

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Hannu Krosing <hannuk(at)google(dot)com>
Cc: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, Денис Романенко <deromanenko(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: NAMEDATALEN increase because of non-latin languages
Date: 2021-08-18 12:28:09
Message-ID: CAOBaU_ZRWGwNa-kHtUea5BA5+GpU34i8ZnGoqS_mZfapKVhfwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 18, 2021 at 8:03 PM Hannu Krosing <hannuk(at)google(dot)com> wrote:
>
> Also - have we checked that at least the truncation does not cut utf-8
> characters in half ?

Yes, same for all other places that can truncate text (like the query
text in pg_stat_activity and similar). See usage of pg_mbcliplen() in
truncate_identifier.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Fan 2021-08-18 12:29:33 Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series)
Previous Message Laurenz Albe 2021-08-18 12:24:13 Re: Improve documentation for pg_upgrade, standbys and rsync