From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Benjamin Weaver <benjamin(dot)weaver(at)classics(dot)ox(dot)ac(dot)uk> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: unicode searches failing that use % and LIKE operators |
Date: | 2007-10-22 21:01:45 |
Message-ID: | 25825.1193086905@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Benjamin Weaver <benjamin(dot)weaver(at)classics(dot)ox(dot)ac(dot)uk> writes:
> Postgres 8.1.4
> server_encoding UTF8
> lc_collate en_GB.UTF-8
> lc_ctype en_GB.UTF-8
Hmph, nothing strange-looking there. I tried to reproduce the problem
here, without success. Now I was using 8.1.10 on Linux (I gather your
platform is not Linux from the spelling of the locale names), but there
hasn't been any change in the LIKE code in the 8.1 branch.
One thing that would be worth trying is to turn on query logging
(set log_statement = 'all') and verify that the problem query appears in
the postmaster log as you expect; this is just to eliminate any doubt
about whether the string encoding is getting messed up somewhere between
client and server.
Assuming you don't find a smoking gun that way, can you put together a
self-contained test case? There must be some detail of what you're
doing that I failed to reproduce.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Martin Marques | 2007-10-22 21:01:58 | Re: Bitmap Heap scan 8.1/8.2 |
Previous Message | Chris Browne | 2007-10-22 20:59:40 | Re: How to use 'toast' |