BUG #18894: values of JLC_COLLATE and LC_CTYPE in the database have changed from Japanese_Japan.932 to ja-jp

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: bing(dot)xu(dot)uh(at)fujifilm(dot)com
Subject: BUG #18894: values of JLC_COLLATE and LC_CTYPE in the database have changed from Japanese_Japan.932 to ja-jp
Date: 2025-04-14 06:08:13
Message-ID: 18894-be1784bdcbdc93e8@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18894
Logged by: xu bing
Email address: bing(dot)xu(dot)uh(at)fujifilm(dot)com
PostgreSQL version: 17.4
Operating system: windows server 2019 Datacenter
Description:

In PostgreSQL 17.1, the values of JLC_COLLATE and LC_CTYPE in the database
are Japanese_Japan.932. However, in PostgreSQL 17.4,
they have changed to ja-JP. When upgrading from PostgreSQL 14.13 to
PostgreSQL 17.4,
the values of JLC_COLLATE and LC_CTYPE remain as Japanese_Japan.932.

I would like to know if this change affects data sorting and other
operations. If it does,
what parameters should be specified during the upgrade to change
Japanese_Japan.932 to ja-JP?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Gang Chen 2025-04-14 08:55:04 回复: BUG #18892: When the view already exists, CREATE OR REPLACE VIEW does not check whether the table exists.
Previous Message David Rowley 2025-04-13 23:26:10 Re: BUG #18885: ERROR: corrupt MVNDistinct entry - 2