| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rolf Jentsch <RJentsch(at)electronicpartner(dot)de> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG: ILIKE with single-byte encoding |
| Date: | 2008-03-01 03:28:19 |
| Message-ID: | 24984.1204342099@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Rolf Jentsch <RJentsch(at)electronicpartner(dot)de> writes:
> With PostgreSQL 8.3.0 the following bug has been introduced with the ILIKE or
> ~~* operator:
> In a database with single-byte encoding as LATIN1 the expression
> SELECT 'a' ILIKE '%';
> returns false.
> For the single-byte case there are some places where a (signed) char
> value is compared to the return value auf tolower() which is an int.
Patch applied, thanks! It turns out there was a second bug on the very
same line: some machines have problems if the argument of tolower()
isn't explicitly cast to unsigned char ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manos Tsagias | 2008-03-01 11:39:11 | BUG #4004: out of memory |
| Previous Message | Steve Clark | 2008-02-29 21:29:36 | ecpg produces code that won't compile |