Common query optimization patterns in PostgreSQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of using indexes in query optimization?

Indexes help the database find rows faster by creating a quick lookup structure, similar to a book's index that lets you find pages without reading the whole book.

beginner

Why should you avoid SELECT * in queries when optimizing?

Using SELECT * fetches all columns, which can slow down queries by transferring unnecessary data. Selecting only needed columns reduces data load and speeds up the query.

beginner

How does query filtering with WHERE clauses improve performance?

WHERE clauses limit the rows processed by the database, so it works with less data and returns results faster, like filtering a list to only what you need.

intermediate

What is the benefit of using EXPLAIN in PostgreSQL?

EXPLAIN shows how PostgreSQL plans to run your query, helping you understand if indexes or joins are used efficiently, so you can improve query speed.

intermediate

Why is avoiding unnecessary JOINs important in query optimization?

Each JOIN adds work for the database. Removing joins that don't add needed data reduces processing time and speeds up the query.

Which of the following helps speed up data retrieval in PostgreSQL?

A Avoiding WHERE clauses

B Using SELECT * to get all columns

C Creating indexes on columns used in WHERE clauses

D Joining all tables regardless of need

Indexes on columns used in WHERE clauses allow faster lookups, improving query speed.

What does the EXPLAIN command do in PostgreSQL?

A Shows the query execution plan

B Deletes data from tables

C Creates a new index

D Optimizes the database automatically

EXPLAIN shows how PostgreSQL plans to execute a query, helping identify optimization opportunities.

Why is it better to select only needed columns instead of using SELECT *?

A It automatically creates indexes

B It makes the query syntax simpler

C It increases the number of rows returned

D It reduces the amount of data transferred and speeds up queries

Selecting only needed columns reduces data transfer and processing, improving performance.

What is a common effect of unnecessary JOINs in a query?

A More data processed and slower queries

B Automatic index creation

C Faster query execution

D Reduced number of rows returned

Unnecessary JOINs increase the amount of data processed, slowing down the query.

How does adding a WHERE clause affect query performance?

A It increases the number of rows returned

B It filters rows, reducing data processed and speeding up the query

C It disables indexes

D It duplicates data in the result

WHERE clauses limit rows processed, making queries faster.

Explain three common patterns to optimize SQL queries in PostgreSQL.

Think about how to reduce data scanned and processed.

Describe how the EXPLAIN command helps in query optimization.

It reveals what the database does behind the scenes.

Practice

1. Which of the following is the best reason to create an index on a column in PostgreSQL?

easy

A. To speed up searches on that column

B. To reduce the size of the database

C. To automatically backup the data

D. To encrypt the data in that column

Solution

1. Step 1: Understand what an index does

   An index helps the database find rows faster by creating a quick lookup structure.

2. Step 2: Match the purpose to the options

   Only speeding up searches matches the purpose of an index; other options are unrelated.

3. Final Answer:

   To speed up searches on that column -> Option A

4. Quick Check:

   Index = Speed up search [OK]

Hint: Indexes speed up searches, not storage or encryption [OK]

Common Mistakes:

• Thinking indexes reduce database size
• Confusing indexes with backups
• Assuming indexes encrypt data

2. Which of the following is the correct syntax to check the query plan in PostgreSQL?

easy

A. EXPLAIN SELECT * FROM users;

B. DESCRIBE SELECT * FROM users;

C. PLAN SELECT * FROM users;

D. SHOW PLAN SELECT * FROM users;

Solution

1. Step 1: Recall the command to view query plans

   PostgreSQL uses EXPLAIN to show how it will run a query.

2. Step 2: Compare options to the correct command

   Only EXPLAIN SELECT * FROM users; is valid syntax for query plans.

3. Final Answer:

   EXPLAIN SELECT * FROM users; -> Option A

4. Quick Check:

   EXPLAIN = Query plan check [OK]

Hint: Use EXPLAIN before your query to see the plan [OK]

Common Mistakes:

• Using SHOW PLAN which is invalid
• Trying PLAN or DESCRIBE which are not PostgreSQL commands
• Missing the EXPLAIN keyword

3. Consider the query:
SELECT id, name FROM employees WHERE department = 'Sales';
Which optimization pattern does this query follow?

medium

A. Using a JOIN to combine tables

B. Using ORDER BY to sort results

C. Using a subquery to filter data

D. Selecting only needed columns instead of *

Solution

1. Step 1: Analyze the SELECT clause

   The query selects only 'id' and 'name', not all columns with '*'.

2. Step 2: Identify the optimization pattern

   Selecting only needed columns reduces data transfer and improves speed.

3. Final Answer:

   Selecting only needed columns instead of * -> Option D

4. Quick Check:

   Selective columns = Better performance [OK]

Hint: Avoid SELECT *; pick only columns you need [OK]

Common Mistakes:

• Confusing JOIN usage with column selection
• Thinking ORDER BY is always an optimization
• Assuming subqueries are used here

4. You have this query:
SELECT * FROM orders WHERE order_date = '2023-01-01';
It runs slowly. Which fix will likely improve performance?

medium

A. Change SELECT * to SELECT COUNT(*)

B. Add an index on the order_date column

C. Remove the WHERE clause

D. Use GROUP BY order_date

Solution

1. Step 1: Identify the cause of slowness

   Query filters on order_date but may scan all rows without an index.

2. Step 2: Apply optimization by indexing

   Adding an index on order_date lets PostgreSQL find matching rows faster.

3. Final Answer:

   Add an index on the order_date column -> Option B

4. Quick Check:

   Index on filter column = Faster query [OK]

Hint: Index columns used in WHERE for faster filtering [OK]

Common Mistakes:

• Removing WHERE loses filtering purpose
• Changing SELECT * to COUNT(*) changes result, not speed
• Using GROUP BY without aggregation is incorrect

5. You want to optimize a query that joins two large tables on a column and filters by a date range. Which combination of patterns will best improve performance?

hard

A. Use subqueries instead of JOINs; do not filter by date

B. Select all columns with *; avoid indexes to save space

C. Create indexes on join columns and filter columns; use EXPLAIN to check plan

D. Add ORDER BY on join column; remove WHERE clause

Solution

1. Step 1: Identify key optimization needs

   Joining large tables and filtering by date needs indexes on join and filter columns.

2. Step 2: Use EXPLAIN to verify query plan

   Checking the plan helps confirm indexes are used and query is efficient.

3. Final Answer:

   Create indexes on join columns and filter columns; use EXPLAIN to check plan -> Option C

4. Quick Check:

   Indexes + EXPLAIN = Best optimization [OK]

Hint: Index join and filter columns; verify with EXPLAIN [OK]

Common Mistakes:

• Selecting all columns wastes resources
• Avoiding indexes slows queries
• Removing WHERE loses filtering benefits