3 ms·
Roughly speaking: smaller index size = greater performance. The index also has to be read from disk (if not already in memory), which is faster the smaller it
by Skinney 6y ago
Roughly speaking: smaller index size = greater performance.
The index also has to be read from disk (if not already in memory), which is faster the smaller it is. But also, once in memory, smaller size makes key-lookups or traversals faster.
How much faster? It really depends on your index.
- petergeoghegan 6y agoB-Tree deduplication can also help to control duplicate index tuples caused by MVCC "version churn" -- including in unique indexes. See the paragraph that begins with "B-Tree indexes are not directly aware that under MVCC..." here: https://www.postgresql.org/docs/devel/btree-implementation.html#BTREE-DEDUPLICATION https://www.postgresql.org/docs/devel/btree-implementation.h...