Re: [GENERAL] Changing collate & ctype for an existing database - Mailing list pgsql-general

From rihad
Subject Re: [GENERAL] Changing collate & ctype for an existing database
Date
Msg-id 2abc80e6-452e-1ce5-e579-a9d05cbe5d2e@mail.ru
Whole thread Raw
In response to Re: [GENERAL] Changing collate & ctype for an existing database  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [GENERAL] Changing collate & ctype for an existing database  (Albe Laurenz <laurenz.albe@wien.gv.at>)
List pgsql-general
On 07/12/2017 11:25 PM, Tom Lane wrote:
> rihad <rihad@mail.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?



pgsql-general by date:

Previous
From: Simon Ruderich
Date:
Subject: [GENERAL] Long wrapped header lines in psql with expanded mode (9.6.3)
Next
From: Pavel Stehule
Date:
Subject: Re: [GENERAL] Long wrapped header lines in psql with expanded mode (9.6.3)