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

From Avi Uziel
Subject Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
Date
Msg-id CAMjTNpt0GNgmf6PEbriTqAdWXcUmnJZntB4Hp=n_aVD=RsBEHw@mail.gmail.com
Whole thread Raw
In response to Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows  (Nico Williams <nico@cryptonector.com>)
List pgsql-bugs
Hi,

I'm struggling with the upgrade process related to this issue, and I hope you can help me.

As mentioned at the beginning of this thread, I'm trying to upgrade cluster version 13.13 to 15.12 on Windows.
My v13.13 cluster uses "English_United States.1252" locale.

When I install the new cluster v15.12, on Windows using the CLI command, I would like to pass this locale using the  "--locale" flag.
This way, the "old" and "new" clusters will have the same locale, and the "pg_upgrade" will work.

The issue is that running the installed using "--locale 'English_United States.1252'" fails with an error "locale specified not supported".
Can you please clarify this for me?

Thanks,
Avi


On Thu, Apr 17, 2025 at 10:31 PM Nico Williams <nico@cryptonector.com> wrote:
On Thu, Apr 17, 2025 at 02:18:10PM -0500, Nico Williams wrote:
> What I might consider is to require that all new PG DBs must run in
> UTF-8 locales and/or codepages only, and provide a migration tool for
> existing DBs while not breaking them.

And declare that PG 19 or 20 will not support non-UTF-8 locales /
codepages.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18900: Missing RPM python3-kazoo for RHEL9 - patroni RPM cannot be installed
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: Disabled logical replication origin session causes primary key errors