LATERAL join for correlated subqueries in PostgreSQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a LATERAL join in PostgreSQL?

A LATERAL join allows a subquery in the FROM clause to reference columns from tables that appear before it in the same FROM clause. It helps run correlated subqueries that depend on each row of the preceding table.

beginner

Why use LATERAL join instead of a normal join?

LATERAL join lets the subquery use values from each row of the previous table, enabling row-by-row processing. Normal joins cannot do this because they treat tables independently.

intermediate

How do you write a LATERAL join in SQL?

Use the keyword LATERAL before a subquery in the FROM clause. Example: FROM table1, LATERAL (SELECT ... WHERE table1.column = ...) AS alias

intermediate

What is a practical example of a LATERAL join?

Finding the top 1 related record per row. For example, for each customer, find their most recent order using LATERAL to run a subquery per customer.

advanced

Can LATERAL join improve query performance?

Yes, because it avoids repeated full scans by running a correlated subquery efficiently per row, often faster than separate queries or complex joins.

What does the LATERAL keyword allow in a FROM clause?

A Subquery can reference columns from preceding tables

B Subquery runs independently without referencing other tables

C Subquery can only reference columns from following tables

D Subquery is executed after the main query finishes

LATERAL allows the subquery to use columns from tables that appear before it in the FROM clause.

Which of these is a correct use of LATERAL join?

A SELECT * FROM customers, orders

B SELECT * FROM customers JOIN orders ON customers.id = orders.customer_id

C SELECT * FROM customers WHERE EXISTS (SELECT * FROM orders)

D SELECT * FROM customers, LATERAL (SELECT * FROM orders WHERE orders.customer_id = customers.id LIMIT 1) AS recent_order

Option D shows a LATERAL join where the subquery references the outer table 'customers' for each row.

What is a key benefit of using LATERAL joins?

A They replace GROUP BY clauses

B They allow correlated subqueries in the FROM clause

C They speed up all queries automatically

D They eliminate the need for indexes

LATERAL joins enable correlated subqueries that depend on each row of a preceding table.

In PostgreSQL, what happens if you omit LATERAL before a correlated subquery in FROM?

A The query will fail or not run as expected

B The subquery will still reference outer tables correctly

C The subquery runs faster

D The subquery is ignored

Without LATERAL, the subquery cannot reference outer tables and will cause an error or unexpected results.

Which SQL clause is LATERAL most closely related to?

A WHERE

B GROUP BY

C FROM

D ORDER BY

LATERAL is used in the FROM clause to allow subqueries to reference preceding tables.

Explain what a LATERAL join is and why it is useful in SQL queries.

Think about how subqueries can depend on each row of another table.

Describe a scenario where using a LATERAL join improves query results or performance.

Consider queries that need the top related record for each row.

Practice

1. What is the main purpose of using a LATERAL join in PostgreSQL?

easy

A. To run a subquery for each row of the main table using that row's data

B. To join two tables without any condition

C. To create a temporary table for all rows at once

D. To speed up queries by caching results

Solution

1. Step 1: Understand what LATERAL join does

   A LATERAL join allows a subquery to use columns from the current row of the main query.

2. Step 2: Identify the main purpose

   This means the subquery runs once per row, using that row's data to produce related results.

3. Final Answer:

   To run a subquery for each row of the main table using that row's data -> Option A

4. Quick Check:

   LATERAL join = per-row subquery execution [OK]

Hint: LATERAL runs subqueries per row using that row's data [OK]

Common Mistakes:

• Thinking LATERAL joins all rows at once
• Confusing LATERAL with regular JOIN
• Assuming LATERAL speeds up queries by caching

2. Which of the following is the correct syntax to use a LATERAL join in PostgreSQL?

easy

A. SELECT a.id, b.value FROM table_a a JOIN (SELECT value FROM table_b WHERE b.a_id = a.id) b ON true;

B. SELECT a.id, b.value FROM table_a a JOIN LATERAL (SELECT value FROM table_b WHERE b.a_id = a.id) b ON true;

C. SELECT a.id, b.value FROM table_a a LEFT JOIN LATERAL table_b b ON b.a_id = a.id;

D. SELECT a.id, b.value FROM table_a a CROSS JOIN table_b b WHERE b.a_id = a.id;

Solution

1. Step 1: Identify correct LATERAL syntax

   LATERAL must be explicitly stated before the subquery or table function to allow referencing outer query columns.

2. Step 2: Check each option

   SELECT a.id, b.value FROM table_a a JOIN LATERAL (SELECT value FROM table_b WHERE b.a_id = a.id) b ON true; correctly uses JOIN LATERAL with a subquery referencing outer alias 'a'. SELECT a.id, b.value FROM table_a a JOIN (SELECT value FROM table_b WHERE b.a_id = a.id) b ON true; misses LATERAL keyword. SELECT a.id, b.value FROM table_a a LEFT JOIN LATERAL table_b b ON b.a_id = a.id; uses LATERAL but tries to join a table directly without subquery syntax. SELECT a.id, b.value FROM table_a a CROSS JOIN table_b b WHERE b.a_id = a.id; uses CROSS JOIN without LATERAL, so no correlation.

3. Final Answer:

   SELECT a.id, b.value FROM table_a a JOIN LATERAL (SELECT value FROM table_b WHERE b.a_id = a.id) b ON true; -> Option B

4. Quick Check:

   Correct LATERAL syntax includes keyword before subquery [OK]

Hint: LATERAL keyword must precede subquery to access outer columns [OK]

Common Mistakes:

• Omitting LATERAL keyword before subquery
• Using regular JOIN without correlation
• Trying to join tables directly without subquery

3. Given the tables:
users(id, name)
orders(id, user_id, amount)
What will this query return?

SELECT u.name, o.amount FROM users u JOIN LATERAL (SELECT amount FROM orders WHERE user_id = u.id ORDER BY amount DESC LIMIT 1) o ON true;

medium

A. Users with all their orders listed

B. All orders with user names repeated

C. Syntax error due to missing ON condition

D. Each user with their highest order amount

Solution

1. Step 1: Understand the LATERAL subquery

   The subquery selects the highest order amount per user by ordering descending and limiting to 1.

2. Step 2: Analyze the JOIN LATERAL effect

   For each user row, the subquery runs and returns that user's top order amount, joining on true to include all users with orders.

3. Final Answer:

   Each user with their highest order amount -> Option D

4. Quick Check:

   LATERAL subquery returns top order per user [OK]

Hint: LATERAL runs subquery per user to get top order [OK]

Common Mistakes:

• Thinking it returns all orders per user
• Assuming syntax error due to ON true
• Confusing join with CROSS JOIN

4. Identify the error in this query:

SELECT u.name, o.amount FROM users u JOIN LATERAL (SELECT amount FROM orders WHERE user_id = u.id ORDER BY amount DESC LIMIT 1) o;

medium

A. Subquery cannot reference outer query columns

B. Incorrect alias usage for orders table

C. Missing ON clause after LATERAL join

D. ORDER BY not allowed in subqueries

Solution

1. Step 1: Check JOIN syntax

   Every JOIN requires an ON clause or USING clause to specify join condition.

2. Step 2: Verify the query

   The query uses JOIN LATERAL but omits ON clause, causing syntax error.

3. Final Answer:

   Missing ON clause after LATERAL join -> Option C

4. Quick Check:

   JOIN must have ON or USING clause [OK]

Hint: Always add ON clause after JOIN LATERAL [OK]

Common Mistakes:

• Forgetting ON clause after JOIN LATERAL
• Thinking subquery can't use outer columns
• Believing ORDER BY is disallowed in subqueries

5. You want to list each customer with their two most recent orders using LATERAL join. Which query correctly achieves this?

hard

A. SELECT c.name, o.order_id FROM customers c JOIN LATERAL (SELECT order_id FROM orders WHERE customer_id = c.id ORDER BY order_date DESC LIMIT 2) o ON true;

B. SELECT c.name, o.order_id FROM customers c JOIN orders o ON o.customer_id = c.id ORDER BY o.order_date DESC LIMIT 2;

C. SELECT c.name, o.order_id FROM customers c CROSS JOIN LATERAL orders o WHERE o.customer_id = c.id LIMIT 2;

D. SELECT c.name, o.order_id FROM customers c LEFT JOIN LATERAL (SELECT order_id FROM orders WHERE customer_id = c.id ORDER BY order_date ASC LIMIT 2) o ON true;

Solution

1. Step 1: Understand the requirement

   We want two most recent orders per customer, so order by order_date DESC and limit 2 in subquery.

2. Step 2: Check each option

   SELECT c.name, o.order_id FROM customers c JOIN LATERAL (SELECT order_id FROM orders WHERE customer_id = c.id ORDER BY order_date DESC LIMIT 2) o ON true; uses JOIN LATERAL with correct ordering and limit, joining on true to include all customers with orders. SELECT c.name, o.order_id FROM customers c JOIN orders o ON o.customer_id = c.id ORDER BY o.order_date DESC LIMIT 2; limits total rows, not per customer. SELECT c.name, o.order_id FROM customers c CROSS JOIN LATERAL orders o WHERE o.customer_id = c.id LIMIT 2; uses CROSS JOIN LATERAL incorrectly without subquery. SELECT c.name, o.order_id FROM customers c LEFT JOIN LATERAL (SELECT order_id FROM orders WHERE customer_id = c.id ORDER BY order_date ASC LIMIT 2) o ON true; orders ASC, which gives oldest orders, not recent.

3. Final Answer:

   SELECT c.name, o.order_id FROM customers c JOIN LATERAL (SELECT order_id FROM orders WHERE customer_id = c.id ORDER BY order_date DESC LIMIT 2) o ON true; -> Option A

4. Quick Check:

   LATERAL with ORDER BY DESC and LIMIT 2 per customer [OK]

Hint: Use LATERAL with ORDER BY DESC and LIMIT for top N per row [OK]

Common Mistakes:

• Limiting total rows instead of per customer
• Ordering ascending instead of descending
• Using CROSS JOIN LATERAL without subquery