MIME-Version: 1.0
References: 
 <CA+hUKG+VEg7OsbRNbRcakp2k+078PCDhZ6HUJjvGvJ839ivxDQ@mail.gmail.com>
In-Reply-To: 
 <CA+hUKG+VEg7OsbRNbRcakp2k+078PCDhZ6HUJjvGvJ839ivxDQ@mail.gmail.com>
Reply-To: assam258@gmail.com
From: Henson Choi <assam258@gmail.com>
Date: Thu, 16 Apr 2026 10:23:32 +0900
Message-ID: 
 <CAAAe_zANMo3o280YU96Nt=JK=mq=PfygvgT1GnG=7Wuh+Es1GQ@mail.gmail.com>
Subject: Re: Experimenting with wider Unicode storage
To: Thomas Munro <thomas.munro@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>,
 Tatsuo Ishii <ishii@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000e5e7bd064f89ae53"
Archived-At: 
 <https://www.postgresql.org/message-id/CAAAe_zANMo3o280YU96Nt%3DJK%3Dmq%3DPfygvgT1GnG%3D7Wuh%2BEs1GQ%40mail.gmail.com>
Precedence: bulk

--000000000000e5e7bd064f89ae53
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Thomas,

Thank you for sharing this very interesting and creative approach.
Encoding is indeed a crucial factor in capacity planning and
performance benchmarking =E2=80=94 I find this direction quite compelling.

I'm currently working on a few other things, so my responses may not
always be quick, but I wanted to let you know I'm genuinely
interested in following this work.

As it happens, I'm currently collaborating with Ishii-san =E2=80=94 who, as
you know, is one of the original architects of multibyte/CJK support
in PostgreSQL =E2=80=94 on Row Pattern Recognition; that might also be a
thread worth keeping an eye on.

It also strikes me that this is a topic worth considering in the
context of the rapid growth of SNS and AI-generated data. The
pervasive use of emoji =E2=80=94 which cannot be represented in legacy
encodings like EUC-KR at all =E2=80=94 is in fact accelerating the migratio=
n
toward Unicode in Korea and other Asian markets. This makes the
storage efficiency of Unicode for CJK characters an increasingly
practical concern, not just a theoretical one.

I'd like to take some time to analyze the current situation around
character encoding in Korea =E2=80=94 where both EUC-KR legacy systems and
UTF-8 coexist in complex ways =E2=80=94 review the patches you've attached,
and then share some thoughts and feedback.

Best regards,
Henson

--000000000000e5e7bd064f89ae53
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Hi Thomas,<br><br>Thank =
you for sharing this very interesting and creative approach.<br>Encoding is=
 indeed a crucial factor in capacity planning and<br>performance benchmarki=
ng =E2=80=94 I find this direction quite compelling.<br><br>I&#39;m current=
ly working on a few other things, so my responses may not<br>always be quic=
k, but I wanted to let you know I&#39;m genuinely<br>interested in followin=
g this work.<br><br>As it happens, I&#39;m currently collaborating with Ish=
ii-san =E2=80=94 who, as<br>you know, is one of the original architects of =
multibyte/CJK support<br>in PostgreSQL =E2=80=94 on Row Pattern Recognition=
; that might also be a<br>thread worth keeping an eye on.<br><br>It also st=
rikes me that this is a topic worth considering in the<br>context of the ra=
pid growth of SNS and AI-generated data. The<br>pervasive use of emoji =E2=
=80=94 which cannot be represented in legacy<br>encodings like EUC-KR at al=
l =E2=80=94 is in fact accelerating the migration<br>toward Unicode in Kore=
a and other Asian markets. This makes the<br>storage efficiency of Unicode =
for CJK characters an increasingly<br>practical concern, not just a theoret=
ical one.<br><br>I&#39;d like to take some time to analyze the current situ=
ation around<br>character encoding in Korea =E2=80=94 where both EUC-KR leg=
acy systems and<br>UTF-8 coexist in complex ways =E2=80=94 review the patch=
es you&#39;ve attached,<br>and then share some thoughts and feedback.<br><b=
r>Best regards,<br>Henson</div></div>
</div>

--000000000000e5e7bd064f89ae53--