| From: | Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru> |
|---|---|
| To: | Daniel Verite <daniel(at)manitou-mail(dot)org>, James Inform <james(dot)inform(at)pharmapp(dot)de> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15892: URGENT: Using an ICU collation in a primary key column breaks ILIKE query |
| Date: | 2019-07-04 17:57:19 |
| Message-ID: | 94c64652-81f6-63b9-b86c-bfc23d5d41d9@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 04.07.2019 19:50, Daniel Verite wrote:
> Yes. It is because of the index that the code checks if the ILIKE
> can be evaluated with an index lookup. Otherwise it doesn't.
>
> If you feel like recompiling with a temporary fix against v11.4 to do
> your own tests, please try the attached patch.
Also this patch works. I thinks we need to use some ICU function to
check whether a char is a letter.
--
Arthur Zakirov
Postgres Professional: http://www.postgrespro.com
Russian Postgres Company
| Attachment | Content-Type | Size |
|---|---|---|
| fix-selfuncs-ilike-v2.patch | text/x-patch | 741 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juan José Santamaría Flecha | 2019-07-04 18:12:30 | Re: BUG #15889: PostgreSQL failed to build due to error MSB8020 with MSVC on windows |
| Previous Message | Manuel Rigger | 2019-07-04 17:08:44 | Re: ALTER TABLE results in "ERROR: could not open relation with OID 43707388" |