Search Postgresql Archives

Re: C locale + unicode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Tom, thanks for the info.

Do upper() and lower() only work correctly for postgres v8 UTF-8 encoded databases? (They don't seem to work on chars > standard ascii on my 7.4.6 db). Is this locale or encoding specific issue?

Is there likely to be a significant difference in speed between a database using a UTF-8 locale and the C locale (if you don't care about the small issues you detailed below)?

Thanks.

John Sidney-Woollett

Tom Lane wrote:

John Sidney-Woollett <johnsw@xxxxxxxxxxxxx> writes:

Does anyone know if it's permitted to use the 'C' locale with a UNICODE encoded database in 7.4.6?


Yes.


And will it work correctly?


For suitably small values of "correctly", sure.  Textual sort ordering
would be by byte values, which might be a bit unintuitive for Unicode
characters.  And I don't think upper()/lower() would work very nicely
for characters outside the basic ASCII set.  But AFAIR those are the
only gotchas.  People in the Far East, who tend not to care about either
of those points, use 'C' locale with various multibyte character sets
all the time.

			regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
      subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
      message can get through to the mailing list cleanly

---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux