Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Ajay Pal BhullarAjay Pal BhullarReporter
Bingjie MiaoBingjie MiaoStory Points
1Priority
MajorInstabug
Open Instabug
Details
Details
Assignee
Ajay Pal Bhullar
Ajay Pal BhullarReporter
Bingjie Miao
Bingjie MiaoStory Points
1
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created May 23, 2022 at 5:18 PM
Updated March 18, 2023 at 10:55 PM
Resolved May 25, 2022 at 11:06 PM
Currently, if an index scan is not covering, a fetch is done immediately after the index scan, and filters are evaluated after the fetch. There are situations where a filter cannot be effectively used to generate an index span, however the filter only depends on index keys and thus can potentially be evaluated with the index key values only. Such a filter can potentially discard result returned from the index scan and thus reduce unnecessary fetches.
Such filters can be something like:
lower(c1), when c1 is an index key
c1 LIKE "%abc%", like pattern with leading wild card