Date: Sun, 15 Feb 2026 23:07:35 -0600
From: Nico Williams <nico@cryptonector.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Tatsuo Ishii <ishii@postgresql.org>, andreas@proxel.se,
	pgsql-hackers@lists.postgresql.org
Subject: Re: Questionable description about character sets
Message-ID: <aZKmF2C9SAzOgAP9@ubby>
References: <20260211.185847.1679085676298121526.ishii@postgresql.org>
 <29fd7c6b-b3cd-4d45-977c-d9ef2f88378a@proxel.se>
 <20260214.192033.705419152780150580.ishii@postgresql.org>
 <CA+hUKG+HkG-EnYnR_hQzhDCTtdx0Cj-_X-jAzvNkF_=V39jQng@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+hUKG+HkG-EnYnR_hQzhDCTtdx0Cj-_X-jAzvNkF_=V39jQng@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/aZKmF2C9SAzOgAP9%40ubby>
Precedence: bulk

On Mon, Feb 16, 2026 at 05:35:41PM +1300, Thomas Munro wrote:
>                                              [...].  UTF-16 is
> apparently sometimes preferred to save space in other RDBMSs that can
> do it, but I suppose you could achieve the same size most of the time
> with a scheme like that.  [...]

[Off-topic] I think UTF-16 yielding smaller encodings is a truism.  It
really depends on what language the text is mostly written in, but
mostly it's a truism that's not true.  Anyways, UTF-16 has to go away,
and the sooner the better.

Nico
--