opt: include != and IS DISTINCT FROM and IS NOT NULL columns in index recommendations #102206
Labels
A-sql-explain
Issues related to EXPLAIN and EXPLAIN ANALYZE improvements
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
E-quick-win
Likely to be a quick win for someone experienced.
E-starter
Might be suitable for a starter project for new employees or team members.
T-sql-queries
SQL Queries Team
Index recommendations currently do not consider hypothetical indexes on columns used with the following operators:
!=
IS DISTINCT FROM
IS NOT NULL
I think columns used with these operators could go into the R (range) set of columns during hypothetical index creation, as we still generate constrained index scans for them when an index exists.
Jira issue: CRDB-27339
The text was updated successfully, but these errors were encountered: