Advanced PostgreSQL: Indexing, Partitioning, Replication · 강의

파티션 연결 및 분리

ATTACH PARTITION과 DETACH PARTITION을 사용하여 파티션 테이블 안팎으로 데이터를 효율적으로 이동하는 방법을 배웁니다.

레슨 2/411개 단계

파티션 연결 및 분리은(는) CoddyKit의 무료 Advanced PostgreSQL: Indexing, Partitioning, Replication 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 Advanced PostgreSQL: Indexing, Partitioning, Replication 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. Advanced PostgreSQL: Indexing, Partitioning, Replication 강의에는 총 4개의 강의가 포함되어 있습니다.

이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.

Move Data Efficiently

Partitioned tables in PostgreSQL are powerful for managing large datasets. But how do you handle data that needs to be added or removed from these partitions?

This lesson introduces ATTACH PARTITION and DETACH PARTITION, two critical commands that allow you to efficiently move data in and out of your partitioned tables with minimal disruption.

The DETACH PARTITION Command

DETACH PARTITION is used to separate an existing partition from its parent partitioned table. When a partition is detached, it becomes a standalone, regular table.

Syntax: ALTER TABLE parent_table DETACH PARTITION child_table;
Why use it? For archiving old data, performing maintenance on a specific partition, or moving data to a different storage tier.

The main partitioned table remains available for queries during this operation.

Detach for Archiving

Imagine you have a sales table partitioned by month. After a year, you might want to archive the oldest months to reduce the active dataset size.

Instead of deleting data, which can be slow and resource-intensive, you can detach the old partition. This converts it into a separate table, which you can then move, compress, or delete without affecting the main sales table.

Detach in Action

Let's see DETACH PARTITION in action. We'll create a partitioned table, add a partition, insert some data, and then detach it.

After running, try SELECT * FROM sales; and SELECT * FROM sales_2023_q1; in your console to see the effect.

CREATE TABLE sales (
    sale_id SERIAL,
    sale_date DATE,
    amount DECIMAL(10, 2)
) PARTITION BY RANGE (sale_date);

CREATE TABLE sales_2023_q1 PARTITION OF sales
FOR VALUES FROM ('2023-01-01') TO ('2023-04-01');

INSERT INTO sales (sale_date, amount) VALUES ('2023-02-15', 100.00);

ALTER TABLE sales DETACH PARTITION sales_2023_q1;

The ATTACH PARTITION Command

ATTACH PARTITION is the opposite: it adds an existing, independent table as a new partition to a partitioned table.

Syntax: ALTER TABLE parent_table ATTACH PARTITION child_table FOR VALUES FROM (...) TO (...);
Why use it? For bulk loading new data, adding new time ranges, or integrating data from external sources.

The attached table must match the parent's schema (columns, types, and NOT NULL constraints).

Attach for New Data

A common scenario for ATTACH PARTITION is to load large amounts of new data.

Instead of inserting millions of rows directly into a partitioned table (which can be slow due to locking and index updates), you can:

Create a new, empty table with the same schema.
Load all your new data into this temporary table.
Once data is loaded and validated, attach this table as a new partition to your main partitioned table.

This minimizes downtime on the main table.

Attach in Action

Let's demonstrate ATTACH PARTITION. We'll create a partitioned table, then create a separate table, load data into it, and finally attach it as a new partition.

After running, try SELECT * FROM sales_main; in your console to confirm the data is now part of the partitioned table.

CREATE TABLE sales_main (
    sale_id SERIAL,
    sale_date DATE,
    amount DECIMAL(10, 2)
) PARTITION BY RANGE (sale_date);

CREATE TABLE sales_2024_q1_temp (
    sale_id SERIAL,
    sale_date DATE,
    amount DECIMAL(10, 2)
);

INSERT INTO sales_2024_q1_temp (sale_date, amount) VALUES ('2024-03-10', 250.50);

ALTER TABLE sales_main ATTACH PARTITION sales_2024_q1_temp
FOR VALUES FROM ('2024-01-01') TO ('2024-04-01');

Benefits of ATTACH/DETACH

These commands offer significant advantages for managing large partitioned tables:

Zero-Downtime Operations: Detaching/attaching usually involves metadata changes, not full table rewrites, keeping the main table online.
Faster Data Loading: Pre-loading data into a separate table and then attaching is much faster than direct inserts for large volumes.
Efficient Archiving/Deletion: Quickly remove old data from active queries by detaching, then process the standalone table separately.
Simplified Maintenance: You can rebuild indexes or run VACUUM on a detached partition without impacting the performance of the main table.

Important Considerations

While powerful, there are a few things to keep in mind:

Schema Match: The child table's schema must exactly match the parent's, including column order, types, and NOT NULL constraints.
Indexes: Indexes on the parent table are NOT automatically applied to an attached child. You must create them manually on the new partition.
Foreign Keys: Foreign key constraints referencing the partitioned table can complicate detachment.
Data Validation: When attaching, PostgreSQL will verify that all data in the child table falls within the specified partition range. This scan can be time-consuming for very large tables, but can be skipped with ATTACH PARTITION ... CONCURRENTLY (PostgreSQL 13+) if you've already ensured data integrity.

Quick Check: Partition Management

You've learned about the flexibility and efficiency offered by ATTACH PARTITION and DETACH PARTITION.

Which of the following is a key advantage of using ALTER TABLE ... ATTACH PARTITION for loading new data into a partitioned table?

인터랙티브 레슨에서 답해보세요

Recap: Partition Flexibility

In this lesson, you explored how ATTACH PARTITION and DETACH PARTITION provide powerful mechanisms for managing data in PostgreSQL partitioned tables.

DETACH PARTITION allows you to remove a partition, converting it into a standalone table for archiving or maintenance.
ATTACH PARTITION enables you to add an existing table as a new partition, ideal for efficient bulk data loading.

Mastering these commands is crucial for maintaining high performance and flexibility in large-scale partitioned environments.

무료로 시작

AI 튜터와 함께 Advanced PostgreSQL: Indexing, Partitioning, Replication을(를) 배우세요 — 무료

브라우저에서 실제 코드를 작성하고 실행하며, 24/7 AI 튜터로부터 즉각적인 도움을 받고, 웹이나 앱에서 중단한 부분부터 계속 학습하세요.

코스: 11
레슨: 44

무료로 학습 시작 전체 코스 보기

자주 묻는 질문

“파티션 연결 및 분리” 강의는 무료인가요?

네 — “파티션 연결 및 분리” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Advanced PostgreSQL: Indexing, Partitioning, Replication 강의 전체를 잠금 해제할 수 있습니다. Advanced PostgreSQL: Indexing, Partitioning, Replication 강의에는 총 4개의 강의가 포함되어 있습니다.

“파티션 연결 및 분리”에서 뭘 배우나요?

ATTACH PARTITION과 DETACH PARTITION을 사용하여 파티션 테이블 안팎으로 데이터를 효율적으로 이동하는 방법을 배웁니다. 브라우저에서 직접 실행하는 실습 코드로 Advanced PostgreSQL: Indexing, Partitioning, Replication을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Advanced PostgreSQL: Indexing, Partitioning, Replication을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Advanced PostgreSQL: Indexing, Partitioning, Replication은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 2번째 강의입니다.

“파티션 연결 및 분리” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Advanced PostgreSQL: Indexing, Partitioning, Replication 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Advanced PostgreSQL: Indexing, Partitioning, Replication 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

← Advanced PostgreSQL: Indexing, Partitioning, Replication(으)로 돌아가기