Message-ID: <29fd7c6b-b3cd-4d45-977c-d9ef2f88378a@proxel.se>
Date: Fri, 13 Feb 2026 07:48:21 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Questionable description about character sets
To: Tatsuo Ishii <ishii@postgresql.org>, pgsql-hackers@lists.postgresql.org
References: <20260211.185847.1679085676298121526.ishii@postgresql.org>
From: Andreas Karlsson <andreas@proxel.se>
Content-Language: en-US
In-Reply-To: <20260211.185847.1679085676298121526.ishii@postgresql.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/29fd7c6b-b3cd-4d45-977c-d9ef2f88378a%40proxel.se>
Precedence: bulk

On 2/11/26 10:58 AM, Tatsuo Ishii wrote:
> "23.3.1. Supported Character Sets
> Table 23.3 shows the character sets available for use in PostgreSQL."
> 
> https://www.postgresql.org/docs/current/multibyte.html#MULTIBYTE-CHARSET-SUPPORTED
> 
> But the table actually shows encodings (more precisely, "character
> encoding scheme") (BIG5...EUC_JP... UTF8). I think we need one more
> column for "character sets" (more precisely, "coded character sets").
> 
> Encoding   Character set		...
> BIG5       Big5-2003
> :
> EUC_JP     ASCII, JIS X 0208, JIS X 0212, JIS X 0201
> :
> UTF8       Unicode	

Wouldn't that make the table very wide? And for e.g. European character 
encodings I am not sure it is that useful since most or maybe even all 
of them are subsets of unicode, it mostly gets interesting for encodings 
which support characters not in unicode, right?

Andreas