0Pricing
PostgreSQL Performance & Query Optimization · Pelajaran

Subkueri vs. CTE vs. Penggabungan

Bandingkan subkueri, Common Table Expressions (CTE), dan penggabungan untuk menyusun kueri secara optimal.

Subkueri vs. CTE vs. Penggabungan adalah pelajaran PostgreSQL Performance & Query Optimization gratis di CoddyKit. Ini adalah pelajaran 3 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.

Welcome to Query Construction

In this lesson, we'll explore three fundamental ways to combine and structure data in PostgreSQL: Subqueries, Common Table Expressions (CTEs), and Joins.

Understanding their differences and optimal use cases is key to writing efficient and readable SQL.

Joins: The Foundation

You're already familiar with JOINs! They are the primary way to combine rows from two or more tables based on a related column between them.

  • Purpose: Link related data across tables.
  • Readability: Often straightforward for direct relationships.
  • Performance: Highly optimized by PostgreSQL for combining large datasets.

What are Subqueries?

A subquery (or inner query) is a query nested inside another SQL query. It can return a single value (scalar), a single row, a single column, or a table.

  • Placement: In SELECT, FROM, WHERE, or HAVING clauses.
  • Use Cases: Filtering with IN/EXISTS, calculating aggregate values for comparison, or providing derived tables.

Subquery in Action

Here's a simple example where a subquery helps find products with prices above the average. Notice how the inner query runs first.

CREATE TABLE products (
  product_id SERIAL PRIMARY KEY,
  product_name VARCHAR(50),
  price DECIMAL(10, 2)
);

INSERT INTO products (product_name, price) VALUES
('Laptop', 1200.00),
('Mouse', 25.00),
('Keyboard', 75.00),
('Monitor', 300.00),
('Webcam', 50.00);

SELECT product_name, price
FROM products
WHERE price > (SELECT AVG(price) FROM products);

DROP TABLE products;

What are CTEs?

A Common Table Expression (CTE), defined with the WITH clause, creates a temporary, named result set that you can reference within a single SQL statement.

  • Purpose: Improve readability, organize complex queries, and enable recursion.
  • Scope: Only available for the query immediately following the WITH clause.
  • Readability: Breaks down complex logic into logical, readable steps.

CTE in Action

Let's rewrite the previous example using a CTE. Notice how it defines "average_price" first, making the main query clearer.

CREATE TABLE products (
  product_id SERIAL PRIMARY KEY,
  product_name VARCHAR(50),
  price DECIMAL(10, 2)
);

INSERT INTO products (product_name, price) VALUES
('Laptop', 1200.00),
('Mouse', 25.00),
('Keyboard', 75.00),
('Monitor', 300.00),
('Webcam', 50.00);

WITH AverageProductPrice AS (
  SELECT AVG(price) AS avg_price
  FROM products
)
SELECT p.product_name, p.price
FROM products p, AverageProductPrice app
WHERE p.price > app.avg_price;

DROP TABLE products;

Choosing Joins

JOINs are your go-to when you need to combine data from different tables that have a direct, logical relationship.

  • Direct Relationships: When tables are linked by foreign keys.
  • Performance: Highly optimized by the planner for combining large datasets efficiently.
  • Result Set: Creates a single, wider result set from matching rows.

They are often the most performant for combining large tables.

Choosing Subqueries

Subqueries are useful for specific filtering or calculating values that depend on the main query's data, often acting as a single value or a list.

  • Scalar Values: When you need a single value (e.g., WHERE price > (SELECT AVG(price))).
  • Filtering: With IN, NOT IN, EXISTS, NOT EXISTS clauses.
  • Derived Tables: In the FROM clause for temporary, unnamed result sets.

They can sometimes be less readable for complex logic.

Choosing CTEs

CTEs excel when you need to break down complex queries into logical, readable steps or handle recursive data structures.

  • Readability: Improves understanding of multi-step logic.
  • Recursion: Essential for querying hierarchical or graph-like data.
  • Reusability: A CTE can be referenced multiple times within the same main query.

They are often preferred over complex subqueries for clarity.

Performance: It's Complicated!

Often, a query written with a subquery can be rewritten as a JOIN or a CTE, and vice-versa. PostgreSQL's optimizer is smart!

  • Optimizer Role: It often transforms these constructs internally into the most efficient execution plan.
  • Readability First: Prioritize clear, maintainable code.
  • EXPLAIN ANALYZE: Always use it to truly understand the performance impact of your chosen approach, rather than guessing.

Compare & Contrast

Consider the following scenarios. Which SQL construct is generally the most suitable choice for each?

Recap: Constructing Optimal Queries

You've learned to differentiate between JOINs, Subqueries, and CTEs:

  • JOINs: Best for direct table relationships and combining large datasets.
  • Subqueries: Ideal for scalar values, IN/EXISTS filtering, and derived tables.
  • CTEs: Shine for readability, multi-step logic, and recursive queries.

Remember to prioritize readability and use EXPLAIN ANALYZE to confirm performance!

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Subkueri vs. CTE vs. Penggabungan” gratis?

Ya — teks lengkap “Subkueri vs. CTE vs. Penggabungan” 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 “Subkueri vs. CTE vs. Penggabungan”?

Bandingkan subkueri, Common Table Expressions (CTE), dan penggabungan untuk menyusun kueri secara optimal. 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 3 dari 4.

Berapa lama pelajaran “Subkueri vs. CTE vs. Penggabungan” 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

  1. Memahami Algoritme Penggabungan
  2. Menulis Ulang Penggabungan Kompleks
  3. Subkueri vs. CTE vs. Penggabungan
  4. Mengoptimalkan Join LATERAL dan Pencarian Berkorelasi
← Kembali ke PostgreSQL Performance & Query Optimization