pg.ddx.io pgsql-committers@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pgsql: Doc: fix character_sets view. 6+ messages / 1 participants [nested] [flat]
* pgsql: Doc: fix character_sets view. @ 2024-01-09 11:06 Tatsuo Ishii <ishii@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Tatsuo Ishii @ 2024-01-09 11:06 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ master Details ------- https://git.postgresql.org/pg/commitdiff/d596736a499858de800cabb241c0107c978f1b95 Modified Files -------------- doc/src/sgml/information_schema.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: fix character_sets view. @ 2024-01-09 11:07 Tatsuo Ishii <ishii@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Tatsuo Ishii @ 2024-01-09 11:07 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_16_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/a12774ba0e0a6125f46d8ddd59a5afe83a6e7a78 Modified Files -------------- doc/src/sgml/information_schema.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: fix character_sets view. @ 2024-01-09 11:07 Tatsuo Ishii <ishii@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Tatsuo Ishii @ 2024-01-09 11:07 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_15_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/c74aad093d096fdec6d39eb2cad544274b919a93 Modified Files -------------- doc/src/sgml/information_schema.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: fix character_sets view. @ 2024-01-09 11:07 Tatsuo Ishii <ishii@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Tatsuo Ishii @ 2024-01-09 11:07 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_14_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/7a12e8ef0bc66f935ed28c29ef02bf3648fed37f Modified Files -------------- doc/src/sgml/information_schema.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: fix character_sets view. @ 2024-01-09 11:07 Tatsuo Ishii <ishii@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Tatsuo Ishii @ 2024-01-09 11:07 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_13_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/fb198942b3baf6b599dfaf6d78ecd4cd7c5ad1b7 Modified Files -------------- doc/src/sgml/information_schema.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
* pgsql: Doc: fix character_sets view. @ 2024-01-09 11:07 Tatsuo Ishii <ishii@postgresql.org> 0 siblings, 0 replies; 6+ messages in thread From: Tatsuo Ishii @ 2024-01-09 11:07 UTC (permalink / raw) To: pgsql-committers@lists.postgresql.org 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 Branch ------ REL_12_STABLE Details ------- https://git.postgresql.org/pg/commitdiff/469d836a90cca12e730512a445e1d78b9bc6039e Modified Files -------------- doc/src/sgml/information_schema.sgml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2024-01-09 11:07 UTC | newest] Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2024-01-09 11:06 pgsql: Doc: fix character_sets view. Tatsuo Ishii <ishii@postgresql.org> 2024-01-09 11:07 pgsql: Doc: fix character_sets view. Tatsuo Ishii <ishii@postgresql.org> 2024-01-09 11:07 pgsql: Doc: fix character_sets view. Tatsuo Ishii <ishii@postgresql.org> 2024-01-09 11:07 pgsql: Doc: fix character_sets view. Tatsuo Ishii <ishii@postgresql.org> 2024-01-09 11:07 pgsql: Doc: fix character_sets view. Tatsuo Ishii <ishii@postgresql.org> 2024-01-09 11:07 pgsql: Doc: fix character_sets view. Tatsuo Ishii <ishii@postgresql.org>
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox