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:31:02 |
Message-ID: | aAFW9my7HtKjNA71@ubby |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Hayato Kuroda (Fujitsu) | 2025-04-18 12:31:07 | RE: BUG #18898: replication process not working... sometimes |
Previous Message | Nico Williams | 2025-04-17 19:18:10 | Re: PostgreSQL v15.12 fails to perform PG_UPGRADE from v13 and v9 on Windows |