pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Nico Williams <nico@cryptonector.com>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Avi Uziel <avi.uziel@aidoc.com>
Cc: Manika Singhal <manika.singhal@enterprisedb.com>
Cc: Ben Caspi <benc@aidoc.com>
Cc: pgsql-bugs@lists.postgresql.org, Liran Amrani <lirana@aidoc.com>
Cc: Shahar Amram <shahara@aidoc.com>
Cc: Sandeep Thakkar <sandeep.thakkar@enterprisedb.com>
Cc: tgl@sss.pgh.pa.us
Subject: Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
Date: Thu, 17 Apr 2025 14:18:10 -0500
Message-ID: <aAFT8lYzVNax7VO+@ubby> (raw)
In-Reply-To: <CA+hUKGJZGBnATo4-hci-ZoDTLrXWjYT0ZS8_F2XirQ8+Nc1RHg@mail.gmail.com>
References: <CABv1Mx6uBG1OJX3+FHewqCoGtGuQqsLniB47WUrrt8sd1PDK1Q@mail.gmail.com>
	<CAB1XC2KYtPk1h-nopnq3nQMNAG8knA419WozrzSPnkT9LyOfNA@mail.gmail.com>
	<CAMjTNpvFL8P3Y_gdoY_K-f8RbPd3KLNF_8v_Gf5u4HkJ=g3gGQ@mail.gmail.com>
	<a5eefdf4ff9d38c1eb4d4a1e4e4984b386a71218.camel@cybertec.at>
	<CA+hUKGKcbtDSvTySZgmpm2GyzBwTKnEQsaYpgbT6zw0-1qLz6Q@mail.gmail.com>
	<Z/6E91nSacY/8zj1@ubby>
	<CA+hUKGKtbcF-cF__hbx3Cixzp2iPoBAy+9OtQFMhuy3nuF0f-A@mail.gmail.com>
	<Z/7QqnX3R9s+te4O@ubby>
	<CA+hUKGJZGBnATo4-hci-ZoDTLrXWjYT0ZS8_F2XirQ8+Nc1RHg@mail.gmail.com>

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%3DsuFjcci...

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
-- 





view thread (18+ messages)  latest in thread

Message-ID: <aAFT8lYzVNax7VO+@ubby>
Permalink:  ../aAFT8lYzVNax7VO+@ubby/
Also on:    postgresql.org/message-id/aAFT8lYzVNax7VO+@ubby

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: nico@cryptonector.com, thomas.munro@gmail.com, laurenz.albe@cybertec.at, avi.uziel@aidoc.com, manika.singhal@enterprisedb.com, benc@aidoc.com, lirana@aidoc.com, shahara@aidoc.com, sandeep.thakkar@enterprisedb.com, tgl@sss.pgh.pa.us
  Subject: Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows
  In-Reply-To: <aAFT8lYzVNax7VO+@ubby>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox