From: | aman gupta <amangpt89(at)gmail(dot)com> |
---|---|
To: | pgadmin-hackers(at)lists(dot)postgresql(dot)org, pgsql-general(at)lists(dot)postgresql(dot)org |
Cc: | manoj(dot)t(dot)kumar(at)ericsson(dot)com, rajesh(dot)tiwari(at)ericsson(dot)com |
Subject: | Optimizing Postgresql ILIKE while query |
Date: | 2018-10-22 05:56:44 |
Message-ID: | CAC=C=veOiz2vo35uEhGhhq2YMmXcGj_ciA1S5hXDS3kCOq-zkA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgsql-general |
Hi Team,
Greetings for the day!!
Platform:
PostgreSQL 9.6.2 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5
20150623 (Red Hat 4.8.5-11), 64-bit
Issue:
We have the base table which contains 22M records and we created a view on
top of it while querying the view with ILIKE clause it took 44 seconds and
with LIKE Clause 20 Seconds
Query:
fm_db_custom_db=# EXPLAIN (ANALYZE, TIMING OFF)
select
destination,hostname,inputfilename,inputtime,logicalservername,outputfilename,outputtime,processinglink,source,totalinputbytes,totalinputcdrs,totaloutputbytes,totaloutputcdrs
from mmsuper.test_20m_view where inputfilename ilike
'%SDPOUTPUTCDR_4001_BLSDP09_ADM_4997_18-10-15-02549.ASN%';
Also attaching the comparison for both ILIKE and LIKE test performed.
Expectation:
How can we optimize our ILIKE query, since it is hardcoded in the
application and we can't use any other keyword than ILIKE .
BR//
Aman Gupta
+918447611183
amangpt89(at)gmail(dot)com
Attachment | Content-Type | Size |
---|---|---|
LIKE_Clause_ILIKE_Clause_Postgres_Response.txt | text/plain | 13.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2018-10-22 06:00:51 | Re: Optimizing Postgresql ILIKE while query |
Previous Message | Akshay Joshi | 2018-10-19 13:30:29 | [pgAdmin4][Patch]: RM #3232 Backup with incorrect path stays in broken state |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2018-10-22 06:00:51 | Re: Optimizing Postgresql ILIKE while query |
Previous Message | Олег Самойлов | 2018-10-22 05:33:47 | Re: BUG: Incorrect working with POSIX locale if database in UTF-8 encoding |