Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Manika Singhal <manika(dot)singhal(at)enterprisedb(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Avi Uziel <avi(dot)uziel(at)aidoc(dot)com>, Ben Caspi <benc(at)aidoc(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org, Liran Amrani <lirana(at)aidoc(dot)com>, Shahar Amram <shahara(at)aidoc(dot)com>, Sandeep Thakkar <sandeep(dot)thakkar(at)enterprisedb(dot)com>, tgl(at)sss(dot)pgh(dot)pa(dot)us
Subject: Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
Date: 2025-04-10 07:14:21
Message-ID: CA+hUKGLE0k7xg635ab=EVTH4p4zG+0g0-_LzdVKHAyMYWB4qeA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Apr 10, 2025 at 7:03 PM Manika Singhal
<manika(dot)singhal(at)enterprisedb(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message hubert depesz lubaczewski 2025-04-10 11:13:27 Re: BUG #18886: identity duplicate key
Previous Message Manika Singhal 2025-04-10 07:02:58 Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows