| From: | Jacob Champion <pchampion(at)vmware(dot)com> |
|---|---|
| To: | "john(dot)naylor(at)enterprisedb(dot)com" <john(dot)naylor(at)enterprisedb(dot)com>, "michael(at)paquier(dot)xyz" <michael(at)paquier(dot)xyz> |
| Cc: | "pavel(dot)stehule(at)gmail(dot)com" <pavel(dot)stehule(at)gmail(dot)com>, "laurenz(dot)albe(at)cybertec(dot)at" <laurenz(dot)albe(at)cybertec(dot)at>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "horikyota(dot)ntt(at)gmail(dot)com" <horikyota(dot)ntt(at)gmail(dot)com> |
| Subject: | Re: badly calculated width of emoji in psql |
| Date: | 2021-08-16 17:04:32 |
| Message-ID: | 27788f6c85b9485c3dd845875a3fdc285560c8d9.camel@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)paquier(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ranier Vilela | 2021-08-16 17:06:31 | Re: PG14: Avoid checking output-buffer-length for every encoded byte during pg_hex_encode |
| Previous Message | Álvaro Herrera | 2021-08-16 17:00:00 | Re: Autovacuum on partitioned table (autoanalyze) |