You created a GiST index on a text column for full-text search but your queries are still slow. Which of the following is a likely cause?

medium📝 Debug Q14 of 15

PostgreSQL - Indexing Strategies

AYou created the index on the wrong table

BGiST indexes do not support text search

CYou forgot to use the <code>@@</code> operator in your WHERE clause

DYou need to vacuum the table before using the index

Step-by-Step Solution

Solution:

Step 1: Understand GiST index usage for full-text search
GiST indexes support full-text search but queries must use the @@ operator to use the index.
Step 2: Analyze options
The most likely cause is forgetting the @@ operator, which prevents index usage. GiST indexes do not support text search is false--GiST supports text search. Options A and D are possible but less directly related to index usage.
Final Answer:
You forgot to use the @@ operator in your WHERE clause -> Option C
Quick Check:
Full-text search needs @@ operator to use GiST index [OK]

Quick Trick: Use @@ operator in WHERE to leverage GiST full-text index [OK]

Common Mistakes:

Master "Indexing Strategies" in PostgreSQL

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free