Horton

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

Nico Williams <nico@cryptonector.com>

View thread
From: Nico Williams <nico@cryptonector.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>, Avi Uziel <avi.uziel@aidoc.com>, Manika Singhal <manika.singhal@enterprisedb.com>, Ben Caspi <benc@aidoc.com>, pgsql-bugs@lists.postgresql.org, Liran Amrani <lirana@aidoc.com>, Shahar Amram <shahara@aidoc.com>, Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>, tgl@sss.pgh.pa.us
Date: 2025-04-17T19:31:02Z
Lists: pgsql-bugs 
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.