From d596736a499858de800cabb241c0107c978f1b95 Mon Sep 17 00:00:00 2001 From: Tatsuo Ishii Date: Tue, 9 Jan 2024 19:43:19 +0900 Subject: [PATCH] Doc: fix character_sets view. The note regarding character encoding form in "The Information Schema" said that LATIN1 character repertoires only use one encoding form LATIN1. This is not correct because LATIN1 has another encoding form ISO-2022-JP-2. To fix this, replace LATIN1 with LATIN2, which is not supported by ISO-2022-JP-2, thus it can be said that LATIN2 only uses one encoding form. Back-patch to supported branches. Author: Tatsuo Ishii Reviewed-by: Daniel Gustafsson Discussion: https://postgr.es/m/flat/20240102.153925.1147403616414525145.t-ishii%40sranhm.sra.co.jp --- doc/src/sgml/information_schema.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index 0ca7d5a9e0b..9e66be4e83d 100644 --- a/doc/src/sgml/information_schema.sgml +++ b/doc/src/sgml/information_schema.sgml @@ -697,8 +697,8 @@ An encoding of some character repertoire. Most older character repertoires only use one encoding form, and so there are no - separate names for them (e.g., LATIN1 is an - encoding form applicable to the LATIN1 + separate names for them (e.g., LATIN2 is an + encoding form applicable to the LATIN2 repertoire). But for example Unicode has the encoding forms UTF8, UTF16, etc. (not all supported by PostgreSQL). Encoding forms are not exposed