Common query optimization patterns in PostgreSQL

Introduction

Query optimization helps your database find answers faster. It saves time and computer power.

When your database queries take too long to finish.

When you want to reduce the load on your database server.

When you have many users accessing data at the same time.

When you want to make your app or website feel faster.

When you want to save money on database resources.

Syntax

PostgreSQL

-- Example pattern: Use indexes
CREATE INDEX index_name ON table_name(column_name);

-- Example pattern: Use EXPLAIN to check query plan
EXPLAIN SELECT * FROM table_name WHERE column_name = 'value';

Indexes help the database find rows quickly, like an index in a book.

EXPLAIN shows how the database plans to run your query, helping you spot slow parts.

Examples

This creates an index on the email column in the users table to speed up searches by email.

PostgreSQL

CREATE INDEX idx_users_email ON users(email);

This shows the query plan so you can see if the index is used.

PostgreSQL

EXPLAIN SELECT * FROM users WHERE email = '[e-mail]';

Select only needed columns to reduce data transfer and speed up the query.

PostgreSQL

SELECT id, name FROM users WHERE active = true;

Use range queries with proper conditions to allow index use.

PostgreSQL

SELECT * FROM orders WHERE order_date >= '2024-01-01' AND order_date < '2024-02-01';

Sample Program

This example creates a products table, adds some data, creates an index on the category column, and then runs a query filtered by category. EXPLAIN ANALYZE shows how the index helps speed up the query.

PostgreSQL

CREATE TABLE products (
  id SERIAL PRIMARY KEY,
  name TEXT NOT NULL,
  category TEXT NOT NULL,
  price NUMERIC NOT NULL
);

INSERT INTO products (name, category, price) VALUES
('Pen', 'Stationery', 1.20),
('Notebook', 'Stationery', 2.50),
('Coffee Mug', 'Kitchen', 5.00),
('Desk Lamp', 'Electronics', 15.00);

-- Create index on category
CREATE INDEX idx_products_category ON products(category);

-- Query using the index
EXPLAIN ANALYZE SELECT * FROM products WHERE category = 'Stationery';

Important Notes

Indexes speed up searches but slow down inserts and updates, so use them wisely.

Always test your queries with EXPLAIN or EXPLAIN ANALYZE to see if your changes help.

Selecting only needed columns reduces data size and speeds up queries.

Summary

Use indexes to help the database find data faster.

Check query plans with EXPLAIN to understand performance.

Write queries that only get the data you need.

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