Re: badly calculated width of emoji in psql

Поиск
Список
Период
Сортировка
От Jacob Champion
Тема Re: badly calculated width of emoji in psql
Дата
Msg-id 27788f6c85b9485c3dd845875a3fdc285560c8d9.camel@vmware.com
обсуждение исходный текст
Ответ на Re: badly calculated width of emoji in psql  (John Naylor <john.naylor@enterprisedb.com>)
Ответы Re: badly calculated width of emoji in psql  (John Naylor <john.naylor@enterprisedb.com>)
Список pgsql-hackers
On Mon, 2021-08-16 at 11:24 -0400, John Naylor wrote:
> 
> On Sun, Aug 15, 2021 at 10:45 PM Michael Paquier <michael@paquier.xyz> wrote:
> 
> > How large do libpgcommon deliverables get with this patch?  Skimming
> > through the patch, that just looks like a couple of bytes, still.
> 
> More like a couple thousand bytes. That's because the width
> of mbinterval doubled. If this is not desirable, we could teach the
> scripts to adjust the width of the interval type depending on the
> largest character they saw.

True. Note that the combining character table currently excludes
codepoints outside of the BMP, so if someone wants combinations in
higher planes to be handled correctly in the future, the mbinterval for
that table may have to be widened anyway.

--Jacob

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Álvaro Herrera
Дата:
Сообщение: Re: Autovacuum on partitioned table (autoanalyze)
Следующее
От: Ranier Vilela
Дата:
Сообщение: Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode