--=-UiyZcZrhy3hP4Yl1D+xl
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

bug=3D# select * from example_objects where name =3D '=D0=9C=D0=BE=D0=B4=D0=
=B5=D0=BC=D1=8B';
object_id | name=20=20
-----------+--------
2 | =D0=9C=D0=B5=D0=B1=D0=B5=D0=BB=D1=8C
2 | =D0=9C=D0=BE=D0=B4=D0=B5=D0=BC=D1=8B
(=D0=B7=D0=B0=D0=BF=D0=B8=D1=81=D0=B5=D0=B9: 2)
bug=3D# select version();
version=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=2 0=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=20=2 0=20=20=20=20=20=20=20=20=
=20=20=20=20=20=20=20=20=20
---------------------------------------------------------------------------=
------------------------------------------------------
PostgreSQL 7.4.2 on i386-redhat-linux-gnu, compiled by GCC i386-redhat-lin=
ux-gcc (GCC) 3.3.3 20040216 (Red Hat Linux 3.3.3-2.1)
(1 =D0=B7=D0=B0=D0=BF=D0=B8=D1=81=D1=8C)

Do the following in an installation initdb'd in ru_RU.KOI8-R (It doesn't
happen if you initdb'd with UTF-8). You need to run psql in a locale
that is capable of russian letters, namely an UTF-8 locale, or a KOI8-R
locale. Then:

CREATE DATABASE bug WITH ENCODING=3D'unicode';
\c bug
\i dump.sql
-- here you have to set client_encoding if you chose ru_RU.KOI8-R as the
locale for psql
-- set client_encoding to koi8r;
select * from example_objects where name =3D '=D0=9C=D0=BE=D0=B4=D0=B5=D0=
=BC=D1=8B';

dump.sql is attached, the select statement is included in UTF-8.

Let me know if anything is missing.

--=20
Markus Bertheau <twanger (AT) bluetwanger (DOT) de>

--=-UiyZcZrhy3hP4Yl1D+xl
Content-Disposition: attachment; filename=dump.sql
Content-Type: text/x-sql; name=dump.sql; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

SET client_encoding =3D 'UNICODE';

CREATE TABLE example_objects (
object_id numeric(20,0) NOT NULL,
name character varying(20)
) WITHOUT OIDS;

COPY example_objects (object_id, name) FROM stdin;
1 root
2 =D0=9C=D0=B5=D0=B1=D0=B5=D0=BB=D1=8C
2 =D0=9C=D0=BE=D0=B4=D0=B5=D0=BC=D1=8B
\.
\set echo all;
select * from example_objects where name =3D '=D0=9C=D0=BE=D0=B4=D0=B5=D0=
=BC=D1=8B';


--=-UiyZcZrhy3hP4Yl1D+xl
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


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

--=-UiyZcZrhy3hP4Yl1D+xl--

Am Freitag, 23. Juli 2004 11:49 schrieb Markus Bertheau:
That's your problem. Your locale doesn't match your encoding. You need to
use a compatible combination.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

=D0=92 =D0=9F=D1=82=D0=BD, 23.07.2004, =D0=B2 14:02, Peter Eisentraut =D0=
=BF=D0=B8=D1=88=D0=B5=D1=82:
What is happening in the server that this is required?

--=20
Markus Bertheau <twanger (AT) bluetwanger (DOT) de>


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

Markus Bertheau <twanger (AT) bluetwanger (DOT) de> writes:
If this is a bug, it's a bug in the ru_RU.KOI8-R locale definition.
You can prove that the locale considers the strings equal without
Postgres at all:

[tgl@rh1 tgl]$ cat ru_data
root
root
ÅœÅçÅÝÅçÅ£îŒ
ÅœÅÅÇÅçÅ¥î‹
[tgl@rh1 tgl]$ sort -u ru_data
root
ÅœÅçÅÝÅçÅ£îŒ
ÅœÅÅÇÅçÅ¥î‹
[tgl@rh1 tgl]$ LC_ALL=ru_RU.KOI8-R sort -u ru_data
root
ÅœÅçÅÝÅçÅ£îŒ
[tgl@rh1 tgl]$

(The above is on an RHL 8.0 platform.)

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Am Freitag, 23. Juli 2004 15:30 schrieb Markus Bertheau:
When you ask locale-aware functions to compare strings, convert to lower-case,
or what the case may be, these functions expect the strings to have a certain
encoding (after all they just receive a stream of bytes, so they cannot check
the encoding themselves). So if the function thinks it's comparing two
KOI8-R strings and you are actually passing UTF-8 strings, the results are
going to be close to comparing garbage.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org