Re: Questionable description about character sets

From: Andreas Karlsson <andreas(at)proxel(dot)se>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Questionable description about character sets
Date: 2026-02-13 06:48:21
Message-ID: 29fd7c6b-b3cd-4d45-977c-d9ef2f88378a@proxel.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2026-02-13 07:06:26 Re: use the malloc macros in pg_dump.c
Previous Message Bertrand Drouvot 2026-02-13 06:42:42 Re: Replace literal 0 values with the appropriate Invalid* constants