From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Don Seiler <don(at)seiler(dot)us>, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Mixed Locales and Upgrading |
Date: | 2020-03-18 02:25:25 |
Message-ID: | 20200318022525.GE214947@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Mar 17, 2020 at 10:45:50AM -0400, Tom Lane wrote:
> Don Seiler <don(at)seiler(dot)us> writes:
>> What are the ramifications of changing collation like that? Should we
>> consider rebuilding indexes ASAP after that?
>
> Text indexes would definitely be at risk here. I'm not really certain
> how bad the problem would be. Do you have a feeling for how much of
> the data is 100% ASCII? If you could be sure of that for any given
> column, you wouldn't have to reindex indexes on that column.
There is no way to know how much indexes would get broken without
having a look at it. Anything ASCII-based should be of no problem.
If you have a doubt, reindexing evey index which includes text column
data is the best course of action in my opinion if you have any
doubts, because that's safe even if it has a higher cost.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | David Gauthier | 2020-03-18 03:14:03 | How can I set all constraints to be deferrable for a DB/schema |
Previous Message | Ian Barwick | 2020-03-18 02:08:53 | Re: Automatic failover |