| From: | Don Seiler <don(at)seiler(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Mixed Locales and Upgrading |
| Date: | 2020-03-17 13:45:41 |
| Message-ID: | CAHJZqBCvZLVCavR4NzvPO9Ufz6McCsaaArhKG9+bvPOQ=isOpg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Mar 17, 2020 at 8:06 AM Don Seiler <don(at)seiler(dot)us> wrote:
> On Mon, Mar 16, 2020 at 10:28 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>>
> Well, in principle you could likewise manually update pg_database's
>> datcollate and datctype columns to say "en_US.utf8". However, there's
>> a much bigger problem here --- what steps if any did this cowboy take
>> to ensure that the data inside the database was valid UTF8?
>
>
Is there a way to programmatically check for data that might be a problem
now?
--
Don Seiler
www.seiler.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2020-03-17 13:56:01 | Re: Mixed Locales and Upgrading |
| Previous Message | Don Seiler | 2020-03-17 13:06:52 | Re: Mixed Locales and Upgrading |