David Wheeler <david(at)kineticode(dot)com> writes:
>> Is the problem query using an index?  If so, does REINDEX help?

> Doesn't look like it:

> bric=3D# reindex index udx_keyword__name;
> REINDEX
> bric=3D# select * from keyword where name =3D'=BA=CF=C7=D1=C0=C7';
>    id  |  name  | screen_name | sort_name | active
> ------+--------+-------------+-----------+--------
>   1218 | =B1=B9=B9=E6=BA=F1 | =B1=B9=B9=E6=BA=F1      | =B1=B9=B9=E6=BA=F1=
>     |      1
> (1 row)

Hmm.  I tried putting your string into a UNICODE database and I got
ERROR:  invalid byte sequence for encoding "UNICODE": 0xc7

So there's something funny happening here.  What is your client_encoding
setting?

			regards, tom lane

In response to

• Re: UTF-8 and LIKE vs = at 2004-08-23 23:18:00 from David Wheeler

Responses

• Re: UTF-8 and LIKE vs = at 2004-08-23 23:49:15 from David Wheeler
• Re: UTF-8 and LIKE vs = at 2004-08-24 01:49:45 from Tim Allen

pgsql-general by date

Next:	From: David Wheeler	Date: 2004-08-23 23:49:15
	Subject: Re: UTF-8 and LIKE vs =
Previous:	From: Ian Barwick	Date: 2004-08-23 23:34:46
	Subject: Re: UTF-8 and LIKE vs =