index skip scan 和oracle partition index 未加分区键类似

索引跳过扫描提升了对非前缀列的索引扫描,因为扫描索引块通常比扫描表数据块更快。非前缀索引是指其第一列不包含关键列的索引。

如果将前缀索引想象为类似分区表,
这个概念会更容易理解。在分区对象中,分区键(此处为首列)定义了存储在哪一列的分区数据中。在索引情况下,每个键下方的每一行(前缀列)都会在该键下排序。因此,在对前缀索引进行跳扫描时,前缀值被跳过,非前缀列作为逻辑子索引访问。后列在前缀列内排列,因此可以进行"正常"索引访问,而无需忽略前缀。
在这种情况下,复合指数被逻辑上拆分为更小的子指数。逻辑子索引的数量取决于初始列的基数。因此,即使首列未被用于 where 子句,也可以使用索引。

Applies To

All Users

Summary

This document explains the index skip scan hint usage.

For developers and DBAs who need to know the syntax of the index skip scan hint.

Solution

Index skip scans improve index scans against non-prefix columns since it is often faster to scan index blocks than scanning table data blocks. A non-prefix index is an index which does not contain a key column as its first column.

This concept is easier to understand if one imagines a prefix index to be similar to a partitioned table. In a partitioned object the partition key (in this case the leading column) defines which partition data is stored within. In the index case every row underneath each key (the prefix column) would be ordered under that key. Thus in a skip scan of a prefixed index, the prefixed value is skipped and the non-prefix columns are accessed as logical sub-indexes. The trailing columns are ordered within the prefix column and so a 'normal' index access can be done ignoring the prefix.

In this case a composite index is split logically into smaller subindexes. The number of logical subindexes depends on the cardinality of the initial column. Hence it is now possible to use the index even if the leading column is not used in a where clause.

++Example query and explain plan:++

drop table at2;
create table at2(a varchar2(3),b varchar2(10),c varchar2(5));

begin
for i in 1..1000
loop
insert into at2 values('M', i, 'M');
insert into at2 values('F', i, 'F');
end loop;
end;
/
create index at2_i on at2(a,b,c);
exec dbms_stats.gather_table_stats(OWNNAME => NULL, TABNAME => 'at2',
CASCADE => TRUE, method_opt => 'FOR ALL COLUMNS SIZE 1');

set autotrace traceonly
select * from at2 where b='352';


| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 2 | 14 | 3 (0)| 00:00:01 |
|* 1 | INDEX SKIP SCAN | AT2_I | 2 | 14 | 3 (0)| 00:00:01 |

Predicate Information (identified by operation id):

1 - access("B"='352')
filter("B"='352')

set autotrace off

相关推荐
这个DBA有点耶3 天前
MVCC深入:Read View、版本链与快照读——InnoDB并发控制的内核
数据库·mysql·架构
DBA_G3 天前
从地面到云霄:GBase数据库在民航三大场景的落地实践
数据库
自由能燃气设备3 天前
商用全预混低氮冷凝锅炉免费方案vs付费方案对比+选型避坑指南
大数据·数据库·人工智能
科创致远3 天前
科创致远 ESOP 系统核心效能与实战价值展示
大数据·数据库·人工智能·精益工程
2601_962218613 天前
万象生鲜系统称重自动多退少补算法解决生鲜非标品痛点
大数据·数据库·人工智能·python·算法
张洛闻Eren3 天前
k8s云原生【第十课】:水平 Pod 自动扩缩容
运维·数据库·云原生·kubernetes·github
于平安3 天前
MySQL-触发器
数据库·mysql
白远山3 天前
上海24小时自助健身房解决方案实战指南与经验分享
java·数据库·架构·需求分析
Omics Pro3 天前
斯坦福Nature+Science|广义虚拟细胞基础大模型
数据库·人工智能·算法·机器学习·自然语言处理
2603_965148113 天前
AI+API选品:下一代智能商务助手雏形已现
java·大数据·数据库·人工智能·数据挖掘