On 07/12/2017 11:25 PM, Tom Lane wrote:
rihad <ri...@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
.
Thanks. It would be great if initdb didn't assume an implicit encoding,
to prevent such fundamental configuration mistakes in the future. More
often than not collation/ctype settings of an ssh login session used to
run initdb aren't what must be used to set up the cluster. It'd be great
if initdb didn't go any further if not provided with an explicit
encoding. The error message would require the user to think twice before
proceeding, and to read up on the matter. Explicit is better than
implicit, as the old saying goes :)
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
