Am 09.03.2007 um 16:15 schrieb Tom Lane:
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.
That does indeed seem to have been the problem even though the
examples I was looking at were all using plain ASCII characters. Glad
to know it wasn't a bug and to have learned something new.
Charlie
--
Charlie Clark
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-938-5360
GSM: +49-178-782-6226
