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

相关推荐
知行合一。。。5 小时前
RAG--03--Milvus基本用法
数据库·oracle·milvus
TDengine (老段)5 小时前
TDengine 线程模型 — 网络、调度、执行
大数据·数据库·物联网·制造·时序数据库·tdengine·涛思数据
上学的小垃圾6 小时前
01-数据库系统概述
数据库
二进制漫游记7 小时前
FastAPI项目集成 Qdrant向量数据库+阿里云Embedding完整实战(工具封装+业务调用)
数据库·python·阿里云·embedding
2501_928996227 小时前
GPT-4o换DeepSeek迁移成本多少?中科热备解析API聚合平台技术账本
前端·数据库·人工智能
泡干脆面就番茄9 小时前
MySQL_子查询_分页查询与联合查询详解
数据库·mysql
devpotato10 小时前
缓存与数据库更新顺序不一致问题
java·数据库·redis
天若有情67310 小时前
Node+MySQL小型全栈笔记项目实战课程分享
数据库·笔记·mysql
wxwx_bscxy32211 小时前
基于springboot宠物领养系统的设计与实现
数据库·spring boot·后端·spring·宠物
九月要晚安11 小时前
达梦DW与AFC对比
数据库