Update comment
authorPeter Eisentraut <peter@eisentraut.org>
Thu, 10 Feb 2022 08:16:17 +0000 (09:16 +0100)
committerPeter Eisentraut <peter@eisentraut.org>
Thu, 10 Feb 2022 08:16:17 +0000 (09:16 +0100)
Update a comment that assumed that libc collations don't support
versioning.  Also improve an adjacent error message a bit.

src/backend/utils/adt/pg_locale.c

index aefa0818d0a3ab2ef60f0cf1bbf49492abcd3558..871a710967cf70ef5a276ea583aa8df3056b54e1 100644 (file)
@@ -1609,11 +1609,11 @@ pg_newlocale_from_collation(Oid collid)
                        {
                                /*
                                 * This could happen when specifying a version in CREATE
-                                * COLLATION for a libc locale, or manually creating a mess in
-                                * the catalogs.
+                                * COLLATION but the provider does not support versioning, or
+                                * manually creating a mess in the catalogs.
                                 */
                                ereport(ERROR,
-                                               (errmsg("collation \"%s\" has no actual version, but a version was specified",
+                                               (errmsg("collation \"%s\" has no actual version, but a version was recorded",
                                                                NameStr(collform->collname))));
                        }