Re: Weird behaviour on a join with multiple keys - Mailing list pgsql-general

From Tom Lane
Subject Re: Weird behaviour on a join with multiple keys
Date
Msg-id 29160.1173453341@sss.pgh.pa.us
Whole thread Raw
In response to Re: Weird behaviour on a join with multiple keys  (Charlie Clark <charlie@begeistert.org>)
Responses Re: Weird behaviour on a join with multiple keys  (Charlie Clark <charlie@begeistert.org>)
List pgsql-general
Charlie Clark <charlie@begeistert.org> writes:
> psytec=# show lc_collate;
> lc_collate
> -------------
> de_DE.UTF-8
> (1 row)

> psytec=# show server_encoding;
> server_encoding
> -----------------
> LATIN1
> (1 row)

There's your problem right there.  The string comparison routines are
built on strcoll(), which is going to expect UTF8-encoded data because
of the LC_COLLATE setting.  If there are any high-bit-set LATIN1
characters in the database, they will most likely look like invalid
encoding to strcoll(), and on most platforms that causes it to behave
very oddly.  You need to keep lc_collate (and lc_ctype) in sync with
server_encoding.

            regards, tom lane

pgsql-general by date:

Previous
From: Rick Schumeyer
Date:
Subject: one-to-one schema design question and ORM
Next
From: Arnaud Lesauvage
Date:
Subject: Bitmap AND multicolumn index used !