>> On 4 Jan 2024, at 13:39, Tatsuo Ishii <is...@sraoss.co.jp> wrote: > >>> Attached is the patch that does this. > > I don't think the patch was attached? > >> Any objection? > > I didn't study the RFC in depth but as expected it seems to back up your > change > so the change seems reasonable.
Oops. Sorry. Patch attached. Best reagards, -- Tatsuo Ishii SRA OSS LLC English: http://www.sraoss.co.jp/index_en/ Japanese:http://www.sraoss.co.jp
diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index 0ca7d5a9e0..9e66be4e83 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