Hello,
just a quick patch for a single-letter typo in a comment
in src/backend/commands/collationcmds.c
...
* set of language+region combinations, whereas the latter only returns
- * language+region combinations of they are distinct from the language's
+ * language+region combinations if they are distinct from the language's
* base collation. So there might not be a de-DE or en-GB, which
would be
...
(please see the attached patch).
--
Anton Voloshin
Postgres Professional: https://www.postgrespro.com
Russian Postgres Company
diff --git a/src/backend/commands/collationcmds.c
b/src/backend/commands/collationcmds.c
index 55a0e24a35..b8ec6f5756 100644
--- a/src/backend/commands/collationcmds.c
+++ b/src/backend/commands/collationcmds.c
@@ -577,7 +577,7 @@ pg_import_system_collations(PG_FUNCTION_ARGS)
* We use uloc_countAvailable()/uloc_getAvailable() rather than
* ucol_countAvailable()/ucol_getAvailable(). The former returns a full
* set of language+region combinations, whereas the latter only returns
- * language+region combinations of they are distinct from the language's
+ * language+region combinations if they are distinct from the language's
* base collation. So there might not be a de-DE or en-GB, which would be
* confusing.
*/