Advanced PostgreSQL: Indexing, Partitioning, Replication · 课时

附加和分离分区

学习使用 ATTACH PARTITION 和 DETACH PARTITION，高效地将数据移入和移出分区表。

附加和分离分区 是 CoddyKit 上的免费 Advanced PostgreSQL: Indexing, Partitioning, Replication 课时。这是第 2 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 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 课程的其余内容，请升级到 CoddyKit PRO。 Advanced PostgreSQL: Indexing, Partitioning, Replication 课程共包含 4 节课。

「附加和分离分区」这节课中我会学到什么？

学习使用 ATTACH PARTITION 和 DETACH PARTITION，高效地将数据移入和移出分区表。你通过在浏览器中直接运行的动手代码来练习 Advanced PostgreSQL: Indexing, Partitioning, Replication，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Advanced PostgreSQL: Indexing, Partitioning, Replication 需要有经验吗？

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

「附加和分离分区」课时需要多长时间？

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

我能在这节 Advanced PostgreSQL: Indexing, Partitioning, Replication 课中编写并运行代码吗？

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

此课程中的所有课时

← 返回 Advanced PostgreSQL: Indexing, Partitioning, Replication