Advanced PostgreSQL: Indexing, Partitioning, Replication · Lesson

Attaching and Detaching Partitions

Learn to efficiently move data in and out of partitioned tables using ATTACH PARTITION and DETACH PARTITION.

Attaching and Detaching Partitions is a free Advanced PostgreSQL: Indexing, Partitioning, Replication lesson on CoddyKit — lesson 2 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Advanced PostgreSQL: Indexing, Partitioning, Replication learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

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.

Frequently asked questions

Is the “Attaching and Detaching Partitions” lesson free?

Yes — the full text of “Attaching and Detaching Partitions” is free to read here on the web, and the Advanced PostgreSQL: Indexing, Partitioning, Replication course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Advanced PostgreSQL: Indexing, Partitioning, Replication course, upgrade to CoddyKit PRO.

What will I learn in “Attaching and Detaching Partitions”?

Learn to efficiently move data in and out of partitioned tables using ATTACH PARTITION and DETACH PARTITION. You practise Advanced PostgreSQL: Indexing, Partitioning, Replication with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Advanced PostgreSQL: Indexing, Partitioning, Replication?

No prior experience is required. Advanced PostgreSQL: Indexing, Partitioning, Replication on CoddyKit is structured for beginners through advanced learners; this is — lesson 2 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Attaching and Detaching Partitions” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Advanced PostgreSQL: Indexing, Partitioning, Replication lesson?

Yes. Every Advanced PostgreSQL: Indexing, Partitioning, Replication lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

← Back to Advanced PostgreSQL: Indexing, Partitioning, Replication