[Solved] Why does PostgreSQL use GiST indexes for geometric and text data instead of B-tree indexes? — Ans: Because GiST supports complex data types and custom search strategies | PostgreSQL

PostgreSQL - Indexing Strategies

Why does PostgreSQL use GiST indexes for geometric and text data instead of B-tree indexes?

ABecause GiST supports complex data types and custom search strategies

BBecause B-tree indexes are slower for all data types

CBecause GiST indexes use less disk space than B-tree

DBecause B-tree indexes cannot be created on text columns

Step-by-Step Solution

Solution:

Step 1: Understand index type capabilities
GiST indexes allow indexing of complex data types like geometric shapes and text with custom search strategies like similarity and overlap.
Step 2: Compare with B-tree indexes
B-tree indexes are optimized for simple, ordered data types and equality or range queries, not complex spatial or text similarity searches.
Final Answer:
Because GiST supports complex data types and custom search strategies -> Option A
Quick Check:
GiST supports complex types and strategies, unlike B-tree [OK]

Quick Trick: GiST handles complex data and custom searches [OK]

Common Mistakes:

Master "Indexing Strategies" in PostgreSQL

9 interactive learning modes - each teaches the same concept differently

Why does PostgreSQL use GiST indexes for geometric and text data instead of B-tree indexes?