You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Date: 2018-04-27 15:57:13 +0200
From: Manuel <>
To: SQL devs <>
Version: 11.27.11 (Jul2017-SP3)
Last updated: 2018-08-31 13:23:22 +0200
Comment 26412
Date: 2018-04-27 15:57:13 +0200
From: Manuel <>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Build Identifier:
I have recently is much faster when the escape clause is omitted fromt eh like operator. I can provide you the dataset used in my experiments, but it should not be hard to reproduce the issue on any dataset.
In my use case, submitting a query like:
where "country" like '%Aus%'
is almost ten time faster than
where "country" like '%Aus%' escape '!'
while in this case there is no need to escape anything, hence the escape clause can be removed, I found this behaviour quite strange.
On the opposite, when using ilike, the behaviour seems the reversed, and the query runs faster when escape clause is present.
Reproducible: Always
Steps to Reproduce:
Create containing a varchar column, and a significant amount of records (I tried with 200 million records)
submit a query involving the like operator and the escape clause
submit a query involving the like operator without the escape clause
repeat step 2 and 3 using the ilike operator.
Actual Results:
When using the like operator performance is much better when the escape keyword is omitted. When using the ilike operator performance is much better when the escape keyword is present
Expected Results:
Performance not to be affected by the escape keyword
Date: 2018-04-27 15:57:13 +0200
From: Manuel <>
To: SQL devs <>
Version: 11.27.11 (Jul2017-SP3)
Last updated: 2018-08-31 13:23:22 +0200
Comment 26412
Date: 2018-04-27 15:57:13 +0200
From: Manuel <>
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36
Build Identifier:
I have recently is much faster when the escape clause is omitted fromt eh like operator. I can provide you the dataset used in my experiments, but it should not be hard to reproduce the issue on any dataset.
In my use case, submitting a query like:
where "country" like '%Aus%'
is almost ten time faster than
where "country" like '%Aus%' escape '!'
while in this case there is no need to escape anything, hence the escape clause can be removed, I found this behaviour quite strange.
On the opposite, when using ilike, the behaviour seems the reversed, and the query runs faster when escape clause is present.
Reproducible: Always
Steps to Reproduce:
Actual Results:
When using the like operator performance is much better when the escape keyword is omitted. When using the ilike operator performance is much better when the escape keyword is present
Expected Results:
Performance not to be affected by the escape keyword
Comment 26517
Date: 2018-06-27 16:54:06 +0200
From: MonetDB Mercurial Repository <>
Changeset 29ae281a5ed3 made by Sjoerd Mullender sjoerd@acm.org in the MonetDB repo, refers to this bug.
For complete details, see https//devmonetdborg/hg/MonetDB?cmd=changeset;node=29ae281a5ed3
Changeset description:
The text was updated successfully, but these errors were encountered: