Postgres Pro
Downloads
Home   >   mailing lists

Re: Re: [GENERAL] Re: [GENERAL] Re: [GENERAL] Different encoding for string values and identifier strings? Or (select 'tést' as tést) returns different values for string and identifier... - Mailing list pgsql-general

From Tom Lane
Subject Re: Re: [GENERAL] Re: [GENERAL] Re: [GENERAL] Different encoding for string values and identifier strings? Or (select 'tést' as tést) returns different values for string and identifier...
Date
Msg-id 27031.1300496513@sss.pgh.pa.us
Whole thread Raw
In response to Re: [GENERAL] Re: [GENERAL] Re: [GENERAL] Different encoding for string values and identifier strings? Or (select 'tést' as tést) returns different values for string and identifier...  ("Francisco Figueiredo Jr." <francisco@npgsql.org>)
Responses Re: [GENERAL] Re: [GENERAL] Re: [GENERAL] Re: [GENERAL] Different encoding for string values and identifier strings? Or (select 'tést' as tést) returns different values for string and identifier...
List pgsql-general
Tree view 
"Francisco Figueiredo Jr." <francisco@npgsql.org> writes:
> My database has encoding set to UTF-8 although my lc_collate is pt.BR.UTF-8
> this lc setting my have cause some trouble?

Hmmm ... actually, it strikes me that this may be a downcasing problem.
PG will try to feed an unquoted identifier through tolower(), and that
basically can't work on multibyte characters.  Most implementations of
tolower() are smart enough to not change high-bit-set bytes in UTF8
locales, but maybe your platform's is not ...

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: error messages during restore
Next
From: Stefan Keller
Date:
Subject: Insert value input syntax of an array of types without ARRAY/ROW nor casting?