Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows - Mailing list pgsql-bugs

From Manika Singhal
Subject Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
Date
Msg-id CAB1XC2LYiSW8Rz_a8FQhg18A5CHzJaKigWxL1OgPk90Rg7M3Ug@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-bugs


On Thu, Apr 10, 2025 at 12:45 PM Thomas Munro <thomas.munro@gmail.com> wrote:
On Thu, Apr 10, 2025 at 7:03 PM Manika Singhal
<manika.singhal@enterprisedb.com> wrote:
> For now, we can update the locales dropdown in the installer to list all the BCP names first,
> followed by the long (old-style) names — excluding those with non-ASCII characters.
>
> We hope this approach will encourage new users to use only BCP names during installation,
> while still providing compatibility with the old-style names for users who want to use pg_upgrade.
>
> Let us know if this sounds reasonable.

+1


Hi,

As discussed earlier, 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 list in either of the
following formats during installation:

  • BCP-47 names
  • Legacy 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

pgsql-bugs by date:

Previous
From: Manika Singhal
Date:
Subject: Re: BUG #18894: values of JLC_COLLATE and LC_CTYPE in the database have changed from Japanese_Japan.932 to ja-jp
Next
From: Nico Williams
Date:
Subject: Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows