0Pricing
PostgreSQL Performance & Query Optimization · 课时

重写复杂连接

学习重构复杂连接条件的技术，以提升查询规划器的效率和执行速度。

重写复杂连接 是 CoddyKit 上的免费 PostgreSQL Performance & Query Optimization 课时。 这是第 2 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 PostgreSQL Performance & Query Optimization 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 PostgreSQL Performance & Query Optimization 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Optimize Complex Joins

When queries involve multiple tables and intricate conditions, they can become difficult to read and for PostgreSQL to optimize efficiently. Rewriting these complex join conditions is a powerful way to improve both clarity and performance.

In this lesson, you'll learn several techniques to refactor your SQL queries, making them more understandable and helping the query planner execute them faster.

Explicit vs. Implicit Joins

Older SQL queries sometimes use a comma-separated list of tables in the FROM clause and define join conditions in the WHERE clause. This is known as an implicit join.

Modern, preferred practice uses explicit joins (INNER JOIN, LEFT JOIN, etc.) with an ON clause. This clearly separates join conditions from filtering conditions, improving readability and intent.

-- Implicit Join (avoid this!)
SELECT p.name, c.name
FROM products p, categories c
WHERE p.category_id = c.id;

-- Explicit Join (preferred)
SELECT p.name, c.name
FROM products p
INNER JOIN categories c ON p.category_id = c.id;

Deconstruct Complex ON Clauses

A single ON clause can contain multiple conditions. While sometimes necessary, overly complex ON clauses can obscure the core join logic. Try to keep ON conditions focused purely on how tables relate.

If conditions are about filtering the joined result, consider moving them to the WHERE clause. This helps the planner understand the join relationship first, then apply filters.

-- Complex ON clause (less clear)
SELECT o.id, p.name
FROM orders o
JOIN products p ON o.product_id = p.id AND p.price > 100 AND p.category_id = 5;

-- Simplified ON, moving filters to WHERE
SELECT o.id, p.name
FROM orders o
JOIN products p ON o.product_id = p.id
WHERE p.price > 100 AND p.category_id = 5;

`USING` for Shared Columns

When two tables share a join column with the exact same name, the USING clause provides a concise and elegant alternative to ON. It implicitly equates the columns from both tables.

This can make your join conditions cleaner, especially in queries with many joins on similarly named foreign keys.

-- Using ON clause
SELECT u.name, o.order_id
FROM users u
INNER JOIN orders o ON u.user_id = o.user_id;

-- Using USING clause (cleaner)
SELECT u.name, o.order_id
FROM users u
INNER JOIN orders o USING (user_id);

Break Down with CTEs

Common Table Expressions (CTEs), introduced with the WITH clause, are excellent for breaking down complex queries into logical, readable, and manageable steps. They act like temporary, named result sets.

By factoring out complex subqueries or intermediate results into CTEs, you can improve readability and sometimes guide the query planner to a more efficient execution path.

-- Complex query with inline subquery
SELECT p.name, c.name, sub.total_orders
FROM products p
JOIN categories c ON p.category_id = c.id
JOIN (
    SELECT product_id, COUNT(id) AS total_orders
    FROM orders
    GROUP BY product_id
    HAVING COUNT(id) > 5
) AS sub ON p.id = sub.product_id;

-- Rewritten with CTE for clarity
WITH PopularProducts AS (
    SELECT product_id, COUNT(id) AS total_orders
    FROM orders
    GROUP BY product_id
    HAVING COUNT(id) > 5
)
SELECT p.name, c.name, pp.total_orders
FROM products p
JOIN categories c ON p.category_id = c.id
JOIN PopularProducts pp ON p.id = pp.product_id;

Filter Early, Join Less

A common optimization strategy is to reduce the amount of data processed as early as possible. If you can filter a table or subquery before joining it, the join operation will have fewer rows to process, which often leads to faster execution.

CTEs or subqueries can be used to pre-filter data, ensuring only relevant rows participate in subsequent joins.

-- Joining then filtering (less efficient if filter is very selective)
SELECT p.name, o.order_date
FROM products p
JOIN orders o ON p.id = o.product_id
WHERE p.price > 50 AND o.order_date > '2023-01-01';

-- Pre-filtering orders with a CTE (more efficient)
WITH RecentExpensiveOrders AS (
    SELECT product_id, order_date
    FROM orders
    WHERE order_date > '2023-01-01'
)
SELECT p.name, reo.order_date
FROM products p
JOIN RecentExpensiveOrders reo ON p.id = reo.product_id
WHERE p.price > 50;

`UNION ALL` for OR Conditions

When a JOIN condition contains an OR clause (e.g., ON A.x = B.y OR A.x = B.z), PostgreSQL might struggle to use indexes effectively for both parts of the OR.

You can sometimes rewrite such a query using UNION ALL to split it into two simpler joins. Each part can then be optimized independently. Be mindful that UNION ALL includes duplicates, unlike UNION.

-- Query with OR in JOIN condition (can be less efficient)
SELECT p.name, c.name
FROM products p
JOIN categories c ON p.category_id = c.id OR p.category_id = c.parent_id;

-- Rewritten with UNION ALL (often better for index usage on each part)
SELECT p.name, c.name
FROM products p JOIN categories c ON p.category_id = c.id
UNION ALL
SELECT p.name, c.name
FROM products p JOIN categories c ON p.category_id = c.parent_id;

`LATERAL` for Row-Dependent Logic

A LATERAL JOIN allows a subquery (or function) in the FROM clause to reference columns from previous FROM items. This is incredibly powerful for scenarios where you need to perform a calculation or retrieve related rows for *each* row of an outer table.

It's often used to rewrite complex correlated subqueries, making them more explicit and sometimes more performant for operations like fetching the 'top N' related items per group.

-- Find the latest order for each product using LATERAL
SELECT p.name, o.order_date, o.quantity
FROM products p
JOIN LATERAL (
    SELECT order_date, quantity
    FROM orders
    WHERE orders.product_id = p.id
    ORDER BY order_date DESC
    LIMIT 1
) AS o ON TRUE;

Eliminate Unnecessary Joins

A simple yet effective rewriting technique is to remove any joins to tables that are not actually needed. If a table isn't used for selecting columns, filtering rows (in WHERE), or ordering the results, then joining to it is redundant.

Unnecessary joins add overhead, consume resources, and can sometimes confuse the query planner, leading to less optimal execution plans.

-- Redundant join to categories table (c.name is not selected or filtered)
SELECT p.name, p.price
FROM products p
JOIN categories c ON p.category_id = c.id;

-- Optimized query (removed redundant join)
SELECT p.name, p.price
FROM products p;

Refactoring Challenge

Consider a complex query that joins several tables and includes a subquery to filter or aggregate data. You want to improve its readability and help PostgreSQL find a better execution plan.

Key Rewriting Takeaways

You've learned powerful techniques to rewrite and optimize complex joins in PostgreSQL:

  • Explicit Joins: Use INNER JOIN, LEFT JOIN with ON for clarity.
  • Simplify ON: Keep join conditions focused, move filters to WHERE.
  • USING Clause: For shared column names, it's concise.
  • CTEs: Break down complex queries into readable, manageable steps.
  • Pre-filtering: Reduce data before joins using subqueries or CTEs.
  • UNION ALL for OR: Split complex OR conditions into simpler, independent joins.
  • LATERAL Joins: For row-dependent subqueries and advanced patterns.
  • Eliminate Redundant Joins: Remove unnecessary tables to reduce overhead.

Applying these strategies will lead to more maintainable and performant PostgreSQL queries.

常见问题解答

「重写复杂连接」课时是免费的吗？

是的 — 「重写复杂连接」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 PostgreSQL Performance & Query Optimization 课程的其余内容，请升级到 CoddyKit PRO。 PostgreSQL Performance & Query Optimization 课程共包含 4 节课。

「重写复杂连接」这节课中我会学到什么？

学习重构复杂连接条件的技术，以提升查询规划器的效率和执行速度。 你通过在浏览器中直接运行的动手代码来练习 PostgreSQL Performance & Query Optimization，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 PostgreSQL Performance & Query Optimization 需要有经验吗？

无需任何先前经验。CoddyKit 上的 PostgreSQL Performance & Query Optimization 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 2 节课，共 4 节。

「重写复杂连接」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 PostgreSQL Performance & Query Optimization 课中编写并运行代码吗？

能。每节 PostgreSQL Performance & Query Optimization 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

  1. 了解连接算法
  2. 重写复杂连接
  3. 子查询、CTE 与连接的比较
  4. 优化 LATERAL 连接与相关查找
← 返回 PostgreSQL Performance & Query Optimization