Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vq6zt-004owC-2P for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Feb 2026 09:59:02 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vq6zs-0039iJ-1b for pgsql-hackers@arkaria.postgresql.org; Wed, 11 Feb 2026 09:59:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vq6zs-0039iB-0S for pgsql-hackers@lists.postgresql.org; Wed, 11 Feb 2026 09:59:01 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vq6zq-00000000806-3ZaD for pgsql-hackers@lists.postgresql.org; Wed, 11 Feb 2026 09:59:00 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:From:Subject:To:Message-Id:Date:Sender:Reply-To:Cc:Content-ID: Content-Description:In-Reply-To:References; bh=DWoXUyNbK9n4lyi1w/vUJvme5oDFLRqTdimsnWKF8Pk=; b=IT3DeNF1o8M1jvMxYCHua39h9z 6bTMfcdzAEPIOLZQF0y6yirL9597N9JPEm2K5O9Mlr7RnnMk2BiV1r2tCPnybCQm9ncfTV0kPVbye HfiWbF70o2HxmXD6B8IJKLiEpNVwWvV/oKEu2k6njuBEnrgZdCdSLqm4dluvHXpM/MezFCzGxZTaI oLyQfQrXByla+TakOqAPxGiOFLLrZlJxqQbPlmHwBfV+Y7VJNvurfoVQQOZT0Se34VKOypZ9xeCt7 Eo6pkdW/DXwxw0hXkLHFKlDSAvuM2vcjrrdEHzUPF6gzrlY+k/6nwGxwYOACGmJNaB/BrCB3T7C5Q 3Mye1fGw==; Received: from [2409:11:4120:300:968e:efa2:38a6:c725] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vq6zn-000J5w-1y for pgsql-hackers@lists.postgresql.org; Wed, 11 Feb 2026 09:58:58 +0000 Date: Wed, 11 Feb 2026 18:58:47 +0900 (JST) Message-Id: <20260211.185847.1679085676298121526.ishii@postgresql.org> To: pgsql-hackers@lists.postgresql.org Subject: Questionable description about character sets From: Tatsuo Ishii X-Mailer: Mew version 6.8 on Emacs 29.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:968e:efa2:38a6:c725 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk "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 Best regards, -- Tatsuo Ishii SRA OSS K.K. English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp