PostgreSQL Performance & Query Optimization · Pelajaran

Menulis Ulang Penggabungan Kompleks

Pelajari teknik untuk memfaktorkan ulang kondisi penggabungan yang rumit guna meningkatkan efisiensi perencana kueri dan kecepatan eksekusi.

Pelajaran 2 dari 411 langkah

Menulis Ulang Penggabungan Kompleks adalah pelajaran PostgreSQL Performance & Query Optimization gratis di CoddyKit. Ini adalah pelajaran 2 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar PostgreSQL Performance & Query Optimization, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus PostgreSQL Performance & Query Optimization mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

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.

Jawab di pelajaran interaktif

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.

Gratis untuk memulai

Belajar SQL dengan tutor AI — gratis

Tulis dan jalankan kode asli di browser kamu, dapatkan bantuan instan dari tutor AI 24/7, dan lanjutkan di mana kamu tinggalkan di web atau aplikasi.

Kursus: 22
Pelajaran: 88

Mulai belajar gratis Lihat kursus lengkapnya

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Menulis Ulang Penggabungan Kompleks” gratis?

Ya — teks lengkap “Menulis Ulang Penggabungan Kompleks” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus PostgreSQL Performance & Query Optimization, upgrade ke CoddyKit PRO. Kursus PostgreSQL Performance & Query Optimization mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Menulis Ulang Penggabungan Kompleks”?

Pelajari teknik untuk memfaktorkan ulang kondisi penggabungan yang rumit guna meningkatkan efisiensi perencana kueri dan kecepatan eksekusi. Kamu berlatih PostgreSQL Performance & Query Optimization dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai PostgreSQL Performance & Query Optimization?

Tidak diperlukan pengalaman sebelumnya. PostgreSQL Performance & Query Optimization di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 2 dari 4.

Berapa lama pelajaran “Menulis Ulang Penggabungan Kompleks” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran PostgreSQL Performance & Query Optimization ini?

Ya. Setiap pelajaran PostgreSQL Performance & Query Optimization menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

Memahami Algoritme Penggabungan
Menulis Ulang Penggabungan Kompleks
Subkueri vs. CTE vs. Penggabungan
Mengoptimalkan Join LATERAL dan Pencarian Berkorelasi

← Kembali ke PostgreSQL Performance & Query Optimization