postgres.git / summary / log / commit / refs

commit    7a12e8ef0bc66f935ed28c29ef02bf3648fed37f
Author:   Tatsuo Ishii <ishii@postgresql.org>
Date:     Tue Jan 09 10:53:49 2024 +0000

    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 45c9705cb1d..84cdda4d2ea 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


[parent: 97e64911da34]