summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTatsuo Ishii2024-01-09 10:43:19 +0000
committerTatsuo Ishii2024-01-09 10:43:19 +0000
commitd596736a499858de800cabb241c0107c978f1b95 (patch)
tree7327bb82d455e7ff85ebcd008f29d677fdb6e356
parent028b15405b4113e1b0f492bf9908d001a5983a77 (diff)
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
-rw-r--r--doc/src/sgml/information_schema.sgml4
1 files 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 @@
<para>
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., <literal>LATIN1</literal> is an
- encoding form applicable to the <literal>LATIN1</literal>
+ separate names for them (e.g., <literal>LATIN2</literal> is an
+ encoding form applicable to the <literal>LATIN2</literal>
repertoire). But for example Unicode has the encoding forms
<literal>UTF8</literal>, <literal>UTF16</literal>, etc. (not
all supported by PostgreSQL). Encoding forms are not exposed