CTE vs subquery performance in PostgreSQL - When to Use Which

The Big Idea

What if your database could think ahead and speed up your queries without extra work?

The Scenario

Imagine you have a big spreadsheet with thousands of rows, and you want to find some specific data by looking through it multiple times manually.

You write down some numbers, then look again, then again, trying to combine results by hand.

The Problem

This manual searching is slow and tiring.

You might make mistakes copying numbers or miss some rows.

It's hard to keep track of what you found and what you still need to check.

The Solution

Using CTEs (Common Table Expressions) or subqueries lets the database do this searching for you in a smart way.

They organize the steps clearly, so the database can optimize and run faster.

You get accurate results without extra effort.

Before vs After

✗ Before

SELECT * FROM (SELECT * FROM sales WHERE amount > 100) AS big_sales WHERE region = 'East';

✓ After

WITH big_sales AS (SELECT * FROM sales WHERE amount > 100) SELECT * FROM big_sales WHERE region = 'East';

What It Enables

You can write clear, easy-to-read queries that run efficiently on large data sets.

Real Life Example

A store manager wants to find all big sales in the East region quickly to plan promotions.

Using CTEs or subqueries helps get this info fast without errors.

Key Takeaways

Manual searching through data is slow and error-prone.

CTEs and subqueries let the database handle complex steps efficiently.

This leads to clearer queries and faster results on big data.

Practice

1. What is a common performance difference between CTEs and subqueries in PostgreSQL before version 12?

easy

A. CTEs and subqueries have identical performance.

B. Subqueries always run slower than CTEs.

C. CTEs act as optimization fences, potentially slowing queries.

D. Subqueries cannot be used inside SELECT statements.

Solution

1. Step 1: Understand CTE behavior in PostgreSQL before v12

   CTEs are treated as optimization fences, meaning the planner executes them separately and does not optimize across them.

2. Step 2: Compare with subqueries

   Subqueries can be inlined and optimized with the rest of the query, often leading to better performance.

3. Final Answer:

   CTEs act as optimization fences, potentially slowing queries. -> Option C

4. Quick Check:

   CTEs before v12 block optimization = A [OK]

Hint: Remember: CTEs block optimization before PostgreSQL 12 [OK]

Common Mistakes:

• Thinking subqueries are always slower
• Assuming CTEs and subqueries perform the same
• Believing subqueries can't be inside SELECT

2. Which of the following is the correct syntax to define a CTE in PostgreSQL?

easy

A. WITH cte_name AS (SELECT * FROM table_name) SELECT * FROM cte_name;

B. SELECT * FROM table_name WITH cte_name AS ();

C. CREATE CTE cte_name SELECT * FROM table_name;

D. WITH (SELECT * FROM table_name) AS cte_name SELECT * FROM cte_name;

Solution

1. Step 1: Recall CTE syntax

   CTEs start with WITH, followed by the CTE name, AS, and a query in parentheses.

2. Step 2: Validate each option

   WITH cte_name AS (SELECT * FROM table_name) SELECT * FROM cte_name; matches the correct syntax. Options A, B, and C have incorrect order or keywords.

3. Final Answer:

   WITH cte_name AS (SELECT * FROM table_name) SELECT * FROM cte_name; -> Option A

4. Quick Check:

   CTE syntax starts with WITH name AS (query) [OK]

Hint: CTE syntax always starts with WITH name AS (query) [OK]

Common Mistakes:

• Placing WITH after SELECT
• Using CREATE keyword for CTE
• Misplacing parentheses

3. Given the following queries, which one is likely to run faster in PostgreSQL 11?

-- Query 1 (CTE):
WITH recent_orders AS (SELECT * FROM orders WHERE order_date > '2024-01-01')
SELECT customer_id, COUNT(*) FROM recent_orders GROUP BY customer_id;

-- Query 2 (Subquery):
SELECT customer_id, COUNT(*) FROM (SELECT * FROM orders WHERE order_date > '2024-01-01') AS recent_orders GROUP BY customer_id;

medium

A. Query 1 runs faster because CTEs are always optimized.

B. Query 2 runs faster because subqueries allow better optimization in PostgreSQL 11.

C. Both queries run at the same speed.

D. Query 1 will cause a syntax error.

Solution

1. Step 1: Understand PostgreSQL 11 optimization

   In PostgreSQL 11, CTEs act as optimization fences, so Query 1 executes the CTE separately.

2. Step 2: Compare with subquery behavior

   Subqueries can be inlined and optimized with the main query, so Query 2 can be faster.

3. Final Answer:

   Query 2 runs faster because subqueries allow better optimization in PostgreSQL 11. -> Option B

4. Quick Check:

   PostgreSQL 11: subqueries optimize better than CTEs [OK]

Hint: Before v12, subqueries usually run faster than CTEs [OK]

Common Mistakes:

• Assuming CTEs always optimize well
• Thinking both queries have same speed
• Believing Query 1 has syntax error

4. Identify the error in this query using a CTE in PostgreSQL:

WITH recent_orders AS SELECT * FROM orders WHERE order_date > '2024-01-01'
SELECT * FROM recent_orders;

medium

A. Missing parentheses around the CTE query.

B. CTE name is invalid.

C. Missing semicolon after CTE.

D. CTEs cannot filter by date.

Solution

1. Step 1: Check CTE syntax

   CTE query must be enclosed in parentheses after AS keyword.

2. Step 2: Identify the missing parentheses

   The query lacks parentheses around SELECT * FROM orders WHERE ...

3. Final Answer:

   Missing parentheses around the CTE query. -> Option A

4. Quick Check:

   CTE query must be in parentheses [OK]

Hint: Always put CTE query inside parentheses after AS [OK]

Common Mistakes:

• Omitting parentheses around CTE query
• Thinking semicolon is required after CTE
• Believing CTE names can't be simple

5. You want to optimize a complex query in PostgreSQL 13 that uses multiple CTEs and subqueries. Which approach is best to improve performance?

hard

A. Avoid both CTEs and subqueries; use temporary tables instead.

B. Replace all CTEs with subqueries to allow better optimization.

C. Use only CTEs because subqueries are deprecated in PostgreSQL 13.

D. Keep CTEs because PostgreSQL 13 can inline them, improving speed.

Solution

1. Step 1: Understand PostgreSQL 13 CTE behavior

   Starting with PostgreSQL 12, CTEs can be inlined and optimized like subqueries.

2. Step 2: Evaluate optimization strategies

   Replacing CTEs with subqueries is not necessary; keeping CTEs maintains readability and performance.

3. Final Answer:

   Keep CTEs because PostgreSQL 13 can inline them, improving speed. -> Option D

4. Quick Check:

   PostgreSQL 12+ inlines CTEs for better optimization [OK]

Hint: PostgreSQL 12+ optimizes CTEs like subqueries [OK]

Common Mistakes:

• Thinking subqueries are deprecated
• Replacing CTEs blindly without testing
• Assuming temporary tables always improve speed