Tom Lane wrote:
> David Wheeler <david(at)kineticode(dot)com> writes:
>>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

One possible clue: your original post in this thread was using encoding 
euc-kr, not unicode (utf-8). If your mailer was set to use that 
encoding, perhaps your other client software is/was also?

Just a guess...

Tim

In response to

• Re: UTF-8 and LIKE vs = at 2004-08-23 23:35:29 from Tom Lane

Responses

• Re: UTF-8 and LIKE vs = at 2004-08-24 01:56:07 from David Wheeler

pgsql-general by date

Next:	From: David Wheeler	Date: 2004-08-24 01:56:07
	Subject: Re: UTF-8 and LIKE vs =
Previous:	From: David Wheeler	Date: 2004-08-24 00:53:03
	Subject: Re: UTF-8 and LIKE vs =