| From: | Nico Williams <nico(at)cryptonector(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Avi Uziel <avi(dot)uziel(at)aidoc(dot)com>, Manika Singhal <manika(dot)singhal(at)enterprisedb(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-17 19:18:10 |
| Message-ID: | aAFT8lYzVNax7VO+@ubby |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
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
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nico Williams | 2025-04-17 19:31:02 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows |
| Previous Message | Keith Paskett | 2025-04-17 19:03:04 | Re: pg_restore error with partitioned table having exclude constraint |