Adjust comments about collate.linux.utf8 regression test.

This test should now work in any database with UTF8 encoding, regardless
of the database's default locale.  The former restriction was really
"doesn't work if default locale is C", and that was because of not handling
mbstowcs/wcstombs correctly.

2 files changed, 4 insertions, 2 deletions

diff --git a/src/test/regress/expected/collate.linux.utf8.out b/src/test/regress/expected/collate.linux.utf8.out
index 9813b6847c8..c065ae98ebb 100644
--- a/src/test/regress/expected/collate.linux.utf8.out
+++ b/src/test/regress/expected/collate.linux.utf8.out
@@ -1,6 +1,7 @@
 /*
  * This test is for Linux/glibc systems and assumes that a full set of
- * locales is installed.  It must be run in a UTF-8 locale.
+ * locales is installed.  It must be run in a database with UTF-8 encoding,
+ * because other encodings don't support all the characters used.
  */
 SET client_encoding TO UTF8;
 CREATE TABLE collate_test1 (
diff --git a/src/test/regress/sql/collate.linux.utf8.sql b/src/test/regress/sql/collate.linux.utf8.sql
index dfb10e4d15b..e16d96a3316 100644
--- a/src/test/regress/sql/collate.linux.utf8.sql
+++ b/src/test/regress/sql/collate.linux.utf8.sql
@@ -1,6 +1,7 @@
 /*
  * This test is for Linux/glibc systems and assumes that a full set of
- * locales is installed.  It must be run in a UTF-8 locale.
+ * locales is installed.  It must be run in a database with UTF-8 encoding,
+ * because other encodings don't support all the characters used.
  */
 
 SET client_encoding TO UTF8;