Re: Changing collate & ctype for an existing database

From: rihad <rihad(at)mail(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Changing collate & ctype for an existing database
Date: 2017-07-13 13:37:25
Message-ID: 2abc80e6-452e-1ce5-e579-a9d05cbe5d2e@mail.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 07/12/2017 11:25 PM, Tom Lane wrote:
> rihad <rihad(at)mail(dot)ru> writes:
>> What if only English letters are used in the textual indices (ascii
>> 0-127), would they still be impacted after datctype&datcollate
>> "C"->"en_US.UTF-8" change?
> Yes, as even minimal testing would have told you. C sort order is
> more case-sensitive, for instance.
>
> regards, tom lane
> .
>
Btw, can we wrap the update of datcollate &datctype and rebuilding of
textual indices inside a transaction with effectively 0 downtime?

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Pavel Stehule 2017-07-13 14:05:43 Re: Long wrapped header lines in psql with expanded mode (9.6.3)
Previous Message Simon Ruderich 2017-07-13 12:40:57 Long wrapped header lines in psql with expanded mode (9.6.3)