Thread

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

   PG Bug reporting form <noreply@postgresql.org> — 2025-04-14T06:08:13Z

   The following bug has been logged on the website:
   
   Bug reference:      18894
   Logged by:          xu bing
   Email address:      bing.xu.uh@fujifilm.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?
   
   

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

   Laurenz Albe <laurenz.albe@cybertec.at> — 2025-04-14T17:30:42Z

   On Mon, 2025-04-14 at 06:08 +0000, PG Bug reporting form wrote:
   > PostgreSQL version: 17.4
   > Operating system:   windows server 2019 Datacenter
   > 
   > 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?
   
   This is a duplicate of
   https://www.postgresql.org/message-id/flat/CABv1Mx6uBG1OJX3%2BFHewqCoGtGuQqsLniB47WUrrt8sd1PDK1Q%40mail.gmail.com
   and is not a PostgreSQL bug.  Still, it is a problem.
   
   We think that these are just two different names for the same thing.
   But you need the names to be identical for pg_upgrade.
   
   So remove the cluster and run "initdb" by hand, specifying the
   old locale names just like they look on the old cluster.
   
   Yours,
   Laurenz Albe
   
   
   
   

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

   Manika Singhal <manika.singhal@enterprisedb.com> — 2025-04-15T14:46:16Z

   On Mon, Apr 14, 2025 at 10:24 PM PG Bug reporting form <
   noreply@postgresql.org> wrote:
   
   > The following bug has been logged on the website:
   >
   > Bug reference:      18894
   > Logged by:          xu bing
   > Email address:      bing.xu.uh@fujifilm.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?
   >
   >
   Hi,
   
   The updated installers for PostgreSQL 16 and 17 (package revision 2) are
   now available
   on our website for download.
   
   These versions include support for selecting the locales in either of the
   following formats during installation:
   
      -
   
      *BCP-47 names*
      -
   
      *Old style long names*
   
   Please try these new installers at your convenience and let us know if they
   work well for your setup.
   Thanks!
   Manika Singhal
   EDB India