From: | Don Seiler <don(at)seiler(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Mixed Locales and Upgrading |
Date: | 2020-04-07 16:41:35 |
Message-ID: | CAHJZqBAGHosweYx74sLHbSkguAt=78m+Bg__-SsbV2FBMKFtPQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Mar 30, 2020 at 4:39 PM Don Seiler <don(at)seiler(dot)us> wrote:
> On Mon, Mar 30, 2020 at 4:30 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> Don Seiler <don(at)seiler(dot)us> writes:
>> > Actually, would I need to re-index on text columns that we know contain
>> > UUID strings? UUID characters seem to be pretty basic alphanumeric ASCII
>> > characters.
>>
>> I think you're all right with respect to those, since they're the
>> same under any encoding. It's columns containing non-ASCII characters
>> that you'd want to worry about reindexing.
>
>
Follow-up question, the locale setting on the host would still be set to
en_US (as would the postgres and template0 databases). Should I look to
change that locale on the system to en_US.UTF-8, or even just for the
postgres user that the DB cluster runs as? What are the ramification for
doing (or not doing) so?
Don.
--
Don Seiler
www.seiler.us
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2020-04-07 16:47:03 | Performance degradation if query returns no rows and column expression is used after upgrading to 12 |
Previous Message | Josef Šimánek | 2020-04-07 16:28:50 | Re: Estimated resources for a 500 connections instance (VM) |