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

From Thomas Munro
Subject Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
Date
Msg-id CA+hUKGLE0k7xg635ab=EVTH4p4zG+0g0-_LzdVKHAyMYWB4qeA@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows  (Manika Singhal <manika.singhal@enterprisedb.com>)
Responses Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
List pgsql-bugs
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



pgsql-bugs by date:

Previous
From: Manika Singhal
Date:
Subject: Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: BUG #18886: identity duplicate key