Re: NAMEDATALEN increase because of non-latin languages

From: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
To: Hannu Krosing <hannuk(at)google(dot)com>
Cc: Julien Rouhaud <rjuju123(at)gmail(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:07:23
Message-ID: CAFBsxsE0sGU=eT63ofG=YKmCtvx8BmVnR8jUzHh=PCB_a4Z4OQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 18, 2021 at 8:03 AM Hannu Krosing <hannuk(at)google(dot)com> wrote:
>
> Could we just make the limitation to be 64 (or 128) _characters_ not
_bytes_ ?

That couldn't work because characters are variable length. The limit has to
be a fixed length in bytes so we can quickly compute offsets in the
attribute tuple.

--
John Naylor
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2021-08-18 12:15:18 Re: Is there now an official way to pass column projection to heap AM
Previous Message John Naylor 2021-08-18 12:04:06 Re: NAMEDATALEN increase because of non-latin languages