CTE materialization behavior in PostgreSQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to define a CTE named 'cte_example' that selects all columns from 'employees'.

PostgreSQL

WITH cte_example AS (SELECT * FROM [1]) SELECT * FROM cte_example;

Drag options to blanks, or click blank then click option'

Aemployees

Bdepartments

Csalaries

Dprojects

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing a table unrelated to employees like 'departments'.

Using a table that doesn't exist in the database.

The CTE 'cte_example' selects all columns from the 'employees' table. Using 'employees' in the FROM clause is correct.

2fill in blank

medium

Complete the code to prevent CTE materialization by using the 'MATERIALIZED' or 'NOT MATERIALIZED' keyword.

PostgreSQL

WITH cte_data AS [1] (SELECT id, name FROM employees) SELECT * FROM cte_data;

Drag options to blanks, or click blank then click option'

ANOT MATERIALIZED

BRECURSIVE

CTEMPORARY

DMATERIALIZED

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'MATERIALIZED' which forces materialization.

Using unrelated keywords like 'TEMPORARY' or 'RECURSIVE'.

Using 'NOT MATERIALIZED' tells PostgreSQL to inline the CTE instead of materializing it.

3fill in blank

hard

Fix the error in the query by choosing the correct keyword to force materialization of the CTE.

PostgreSQL

WITH cte_sales AS [1] (SELECT * FROM sales WHERE amount > 100) SELECT * FROM cte_sales;

Drag options to blanks, or click blank then click option'

ATEMPORARY

BMATERIALIZED

CNOT MATERIALIZED

DRECURSIVE

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'NOT MATERIALIZED' which disables materialization.

Using unrelated keywords like 'TEMPORARY' or 'RECURSIVE'.

The 'MATERIALIZED' keyword forces PostgreSQL to store the CTE result temporarily, which can be useful for performance reasons.

4fill in blank

hard

Fill both blanks to write a CTE that is not materialized and filters employees with salary greater than 50000.

PostgreSQL

WITH cte_high_salary AS [1] (SELECT * FROM employees WHERE salary [2] 50000) SELECT * FROM cte_high_salary;

Drag options to blanks, or click blank then click option'

ANOT MATERIALIZED

B>

C<

DMATERIALIZED

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'MATERIALIZED' instead of 'NOT MATERIALIZED'.

Using '<' instead of '>' for filtering salaries.

The CTE is declared as 'NOT MATERIALIZED' to avoid storing intermediate results. The filter uses '>' to select salaries greater than 50000.

5fill in blank

hard

Fill all three blanks to create a materialized CTE that selects project names and filters projects started after 2020.

PostgreSQL

WITH cte_projects AS [1] (SELECT name AS [2] FROM projects WHERE start_date [3] '2020-12-31') SELECT * FROM cte_projects;

Drag options to blanks, or click blank then click option'

AMATERIALIZED

Bproject_name

C>

DNOT MATERIALIZED

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'NOT MATERIALIZED' instead of 'MATERIALIZED'.

Not renaming the column properly.

Using '<' instead of '>' for date comparison.

The CTE is forced to materialize with 'MATERIALIZED'. The column 'name' is renamed to 'project_name'. The filter uses '>' to select projects started after December 31, 2020.

Practice

1. What does CTE materialization control in PostgreSQL?

easy

A. The data type of columns in the CTE

B. The order of execution of SQL statements

C. The type of join used in the query

D. Whether the CTE results are stored temporarily or inlined into the main query

Solution

1. Step 1: Understand CTE basics

   A Common Table Expression (CTE) is a temporary result set used within a query.

2. Step 2: Identify materialization role

   Materialization controls if PostgreSQL stores the CTE result temporarily or inlines it into the main query for optimization.

3. Final Answer:

   Whether the CTE results are stored temporarily or inlined into the main query -> Option D

4. Quick Check:

   CTE materialization = store or inline [OK]

Hint: Materialization means store or inline CTE results [OK]

Common Mistakes:

• Confusing materialization with join types
• Thinking it controls execution order
• Assuming it changes data types

2. Which of the following is the correct syntax to force PostgreSQL to store a CTE result instead of inlining it?

easy

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

B. WITH cte_name AS NOT MATERIALIZED (SELECT * FROM table_name)

C. WITH cte_name AS MATERIALIZED (SELECT * FROM table_name)

D. WITH cte_name AS MATERIALIZED SELECT * FROM table_name

Solution

1. Step 1: Recall correct CTE syntax with materialization

   PostgreSQL syntax to force materialization is WITH cte_name AS MATERIALIZED (query).

2. Step 2: Check options for syntax correctness

   WITH cte_name AS MATERIALIZED (SELECT * FROM table_name) matches the correct syntax; others have misplaced keywords or missing parentheses.

3. Final Answer:

   WITH cte_name AS MATERIALIZED (SELECT * FROM table_name) -> Option C

4. Quick Check:

   Materialized keyword goes right after AS [OK]

Hint: Use AS MATERIALIZED right before the query in parentheses [OK]

Common Mistakes:

• Placing MATERIALIZED outside parentheses
• Using NOT MATERIALIZED to force storage
• Omitting parentheses around the query

3. Given the query:

WITH cte AS MATERIALIZED (SELECT id FROM users WHERE active = true) SELECT * FROM cte WHERE id < 10;

What is the effect of MATERIALIZED here?

medium

A. The CTE result is stored temporarily before filtering by id < 10

B. The CTE is inlined and filtered directly without storing

C. The query will produce a syntax error

D. The CTE is ignored and the main query runs alone

Solution

1. Step 1: Understand MATERIALIZED effect on CTE

   Using MATERIALIZED forces PostgreSQL to store the CTE result before the outer query uses it.

2. Step 2: Analyze query filtering

   The outer query filters the stored CTE result by id < 10, so filtering happens after storage.

3. Final Answer:

   The CTE result is stored temporarily before filtering by id < 10 -> Option A

4. Quick Check:

   MATERIALIZED = store then filter [OK]

Hint: MATERIALIZED stores CTE before outer query filters [OK]

Common Mistakes:

• Thinking filtering happens before storing
• Assuming MATERIALIZED causes syntax error
• Believing CTE is ignored

4. Consider this query:

WITH cte AS NOT MATERIALIZED (SELECT * FROM orders WHERE amount > 100) SELECT * FROM cte WHERE amount < 500;

Why might this query fail or behave unexpectedly?

medium

A. NOT MATERIALIZED is not supported in this PostgreSQL version causing syntax error

B. The CTE is stored and filtering is delayed causing slow performance

C. The query ignores the WHERE clause inside the CTE

D. The CTE is materialized twice causing duplicate rows

Solution

1. Step 1: Check PostgreSQL support for NOT MATERIALIZED

   NOT MATERIALIZED was introduced in PostgreSQL 12; older versions do not support it and cause syntax errors.

2. Step 2: Analyze query behavior if unsupported

   If the version is older, the query fails with syntax error due to unrecognized keyword.

3. Final Answer:

   NOT MATERIALIZED is not supported in this PostgreSQL version causing syntax error -> Option A

4. Quick Check:

   NOT MATERIALIZED requires PostgreSQL 12+ [OK]

Hint: Check PostgreSQL version for NOT MATERIALIZED support [OK]

Common Mistakes:

• Assuming NOT MATERIALIZED always works
• Thinking filtering is ignored
• Believing CTE duplicates rows

5. You have a complex query with a CTE that is used multiple times in the main query. You want to optimize performance by avoiding repeated execution of the CTE. Which materialization behavior should you choose and why?

hard

A. Use NOT MATERIALIZED to inline the CTE and let PostgreSQL optimize repeated execution

B. Use MATERIALIZED to store the CTE result once and reuse it multiple times

C. Avoid using CTEs and write subqueries instead for better performance

D. Use MATERIALIZED to force PostgreSQL to re-execute the CTE each time

Solution

1. Step 1: Understand repeated CTE usage

   If a CTE is referenced multiple times, storing its result once avoids repeated computation.

2. Step 2: Choose materialization behavior

   Using MATERIALIZED forces storing the CTE result, so it is computed once and reused, improving performance.

3. Final Answer:

   Use MATERIALIZED to store the CTE result once and reuse it multiple times -> Option B

4. Quick Check:

   MATERIALIZED = store once, reuse many [OK]

Hint: Store CTE once with MATERIALIZED to reuse efficiently [OK]

Common Mistakes:

• Thinking NOT MATERIALIZED avoids repeated execution
• Believing MATERIALIZED causes repeated execution
• Avoiding CTEs unnecessarily