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

From Nico Williams
Subject Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
Date
Msg-id aAFT8lYzVNax7VO+@ubby
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>)
Responses Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
List pgsql-bugs
On Wed, Apr 16, 2025 at 12:34:29PM +1200, Thomas Munro wrote:
>         [...]. Non-UTF-8 text does seem to be almost extinct in the
> wild now... *except* on Windows.  I think/hope that will eventually

Sigh, yes.

> change too, you can see it starting...  [...]

Yes, MSFT devs seem keen to push the UTF-8 codepage, which is a most
welcome development.

>
https://www.postgresql.org/message-id/flat/CA%2BhUKGLrx02%3DwT647oYz7x0GW%3DPyQdma0s4U6w9h%3DsuFjcciTw%40mail.gmail.com

I replied.

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.

Nico
-- 



pgsql-bugs by date:

Previous
From: Keith Paskett
Date:
Subject: Re: pg_restore error with partitioned table having exclude constraint
Next
From: Nico Williams
Date:
Subject: Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows