Thread: BUG #17058: Unable to create collation in version 13.

The following bug has been logged on the website:

Bug reference:      17058
Logged by:          Yasushi Yamashita
Email address:      developer@yamashi-ta.jp
PostgreSQL version: 13.3
Operating system:   Windows 10
Description:

[PostgreSQL 13.3, compiled by Visual C++ build 1914, 64-bit]

postgres=# CREATE COLLATION public.ja_jp (LOCALE = 'Japanese_Japan.932');
ERROR:  could not get collation version for locale "Japanese_Japan.932":
error code 87


[PostgreSQL 12.7, compiled by Visual C++ build 1914, 64-bit]

postgres=# CREATE COLLATION public.ja_jp (LOCALE = 'Japanese_Japan.932');
CREATE COLLATION

postgres=# SELECT * FROM pg_collation WHERE collname = 'ja_jp';
  oid  | collname | collnamespace | collowner | collprovider |
collisdeterministic | collencoding |    collcollate     |     collctype
| collversion

-------+----------+---------------+-----------+--------------+---------------------+--------------+--------------------+--------------------+-------------
 16394 | ja_jp    |          2200 |        10 | c            | t
      |            6 | Japanese_Japan.932 | Japanese_Japan.932 |
(1 row)

On Mon, Jun 14, 2021 at 12:31 AM PG Bug reporting form
<noreply@postgresql.org> wrote:
> [PostgreSQL 13.3, compiled by Visual C++ build 1914, 64-bit]
>
> postgres=# CREATE COLLATION public.ja_jp (LOCALE = 'Japanese_Japan.932');
> ERROR:  could not get collation version for locale "Japanese_Japan.932":
> error code 87

Hmm.  I fixed this in 14 with:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=9f12a3b95dd56c897f1aa3d756d8fb419e84a187

Perhaps I should back-patch that to 13.  You can work around the
problem by using 'ja-JP' instead.  That's a "BCP 47 tag", which the
Windows documentation recommends[1].

[1]
https://docs.microsoft.com/en-us/cpp/c-runtime-library/locale-names-languages-and-country-region-strings?view=msvc-160

On Mon, Jun 14, 2021 at 8:33 AM Thomas Munro <thomas.munro@gmail.com> wrote:
> Perhaps I should back-patch that to 13.  You can work around the
> problem by using 'ja-JP' instead.  That's a "BCP 47 tag", which the
> Windows documentation recommends[1].

Done.