Attaching and detaching partitions in PostgreSQL

Introduction

Attaching and detaching partitions helps organize large tables into smaller parts for easier management and faster queries.

When you want to add a new partition to an existing partitioned table.

When you need to remove a partition from a partitioned table without deleting data.

When reorganizing data by moving it between partitions.

When cleaning up old data by detaching partitions before archiving.

When improving query performance by managing partitions separately.

Syntax

PostgreSQL

ALTER TABLE parent_table ATTACH PARTITION child_table FOR VALUES partition_values;

ALTER TABLE parent_table DETACH PARTITION child_table;

The parent_table must be a partitioned table.

The child_table must have data matching the partition values when attaching.

Examples

Attach the partition sales_2023_q1 to the sales table for the first quarter of 2023.

PostgreSQL

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

Detach the partition sales_2022_q4 from the sales table without deleting its data.

PostgreSQL

ALTER TABLE sales DETACH PARTITION sales_2022_q4;

Sample Program

This example creates a partitioned table orders by order_date. It creates a partition orders_2023 for 2023 data. Then it creates a table old_orders with 2022 data and attaches it as a partition for 2022. Finally, it counts rows in each partition.

PostgreSQL

CREATE TABLE orders (
  order_id SERIAL PRIMARY KEY,
  order_date DATE NOT NULL,
  amount NUMERIC
) PARTITION BY RANGE (order_date);

CREATE TABLE orders_2023 PARTITION OF orders
  FOR VALUES FROM ('2023-01-01') TO ('2024-01-01');

CREATE TABLE old_orders (
  order_id SERIAL PRIMARY KEY,
  order_date DATE NOT NULL,
  amount NUMERIC
);

INSERT INTO old_orders (order_date, amount) VALUES ('2022-06-15', 100), ('2022-12-31', 200);

ALTER TABLE orders ATTACH PARTITION old_orders FOR VALUES FROM ('2022-01-01') TO ('2023-01-01');

SELECT tableoid::regclass AS partition_name, count(*) AS rows_count FROM orders GROUP BY tableoid;

Important Notes

When attaching a partition, the data in the child table must fit the partition range or list defined.

Detaching a partition keeps the data in the child table intact; it just removes it from the parent partitioned table.

You cannot attach a partition if the parent table is not partitioned.

Summary

Attaching partitions adds existing tables as parts of a partitioned table.

Detaching partitions removes them without deleting data.

This helps manage large datasets by splitting them into smaller, manageable pieces.

Practice

1. What does attaching a partition to a partitioned table in PostgreSQL do?

easy

A. It adds an existing table as a part of the partitioned table.

B. It deletes the data from the existing table.

C. It merges two tables into one without partitioning.

D. It creates a new partitioned table from scratch.

Solution

1. Step 1: Understand the purpose of attaching partitions

   Attaching a partition means linking an existing table to a partitioned table so it becomes one of its parts.

2. Step 2: Clarify what happens to data

   The data in the existing table remains intact and is now managed as part of the partitioned table.

3. Final Answer:

   It adds an existing table as a part of the partitioned table. -> Option A

4. Quick Check:

   Attaching partitions = adding existing table [OK]

Hint: Attaching means linking existing tables to partitions [OK]

Common Mistakes:

• Thinking attaching deletes data
• Confusing attaching with creating new tables
• Assuming attaching merges tables without partitioning

2. Which of the following is the correct syntax to attach a partition named part_2023 to a partitioned table sales in PostgreSQL?

easy

A. ALTER TABLE sales ADD PARTITION part_2023;

B. ALTER TABLE sales ATTACH PARTITION part_2023 FOR VALUES FROM ('2023-01-01') TO ('2024-01-01');

C. ALTER TABLE sales ATTACH part_2023 PARTITION;

D. ALTER TABLE sales ATTACH PARTITION part_2023;

Solution

1. Step 1: Recall the correct syntax for attaching partitions

   In PostgreSQL, when attaching an existing partitioned table, the syntax is ALTER TABLE sales ATTACH PARTITION part_2023; without specifying the value range, because the partition table already has the range defined.

2. Step 2: Check each option

   ALTER TABLE sales ATTACH PARTITION part_2023; uses the correct syntax. ALTER TABLE sales ATTACH PARTITION part_2023 FOR VALUES FROM ('2023-01-01') TO ('2024-01-01'); incorrectly includes the value range, which is only used when creating a new partition, not attaching an existing one. Options C and D use invalid syntax.

3. Final Answer:

   ALTER TABLE sales ATTACH PARTITION part_2023; -> Option D

4. Quick Check:

   Attach existing partition without value range [OK]

Hint: Attach existing partitions without value ranges using ATTACH PARTITION [OK]

Common Mistakes:

• Including FOR VALUES clause when attaching existing partitions
• Using ADD PARTITION instead of ATTACH PARTITION
• Incorrect keyword order

3. Given the following commands, what will be the result of querying SELECT count(*) FROM sales; after detaching the partition part_2022?

ALTER TABLE sales DETACH PARTITION part_2022;
SELECT count(*) FROM sales;

medium

A. The count includes rows from all partitions including part_2022.

B. The count will be zero because detaching deletes data.

C. The count excludes rows from part_2022 because it was detached.

D. The query will fail with an error because part_2022 is detached.

Solution

1. Step 1: Understand what detaching a partition does

   Detaching removes the partition from the partitioned table but does not delete its data; it becomes a standalone table.

2. Step 2: Effect on queries on the partitioned table

   After detaching, queries on the partitioned table no longer include data from the detached partition.

3. Final Answer:

   The count excludes rows from part_2022 because it was detached. -> Option C

4. Quick Check:

   Detached partitions excluded from parent queries [OK]

Hint: Detached partitions are excluded from parent table queries [OK]

Common Mistakes:

• Assuming detaching deletes data
• Thinking detached partitions still count in queries
• Expecting query errors after detach

4. You run the command ALTER TABLE sales DETACH PARTITION part_2023; but get an error saying the partition does not exist. What is the most likely cause?

medium

A. The partition part_2023 is not attached to the sales table.

B. You need to use DROP PARTITION instead of DETACH PARTITION.

C. The sales table is not partitioned.

D. You must detach partitions before attaching them.

Solution

1. Step 1: Check if the partition exists and is attached

   The error indicates part_2023 is not currently attached to sales, so it cannot be detached.

2. Step 2: Understand the difference between detach and drop

   DETACH PARTITION removes the link but keeps data; DROP PARTITION deletes data. Using drop won't fix a non-attached partition error.

3. Final Answer:

   The partition part_2023 is not attached to the sales table. -> Option A

4. Quick Check:

   Detach fails if partition not attached [OK]

Hint: Detach only works on attached partitions [OK]

Common Mistakes:

• Trying to detach partitions not attached
• Confusing DETACH with DROP
• Ignoring if table is partitioned

5. You have a large partitioned table orders partitioned by range on order_date. You want to archive data from 2020 by detaching the partition orders_2020 and then attaching it to a new partitioned table archived_orders. Which sequence of commands correctly achieves this without data loss?

hard

A. 1. ALTER TABLE archived_orders ATTACH PARTITION orders_2020;
2. ALTER TABLE orders DETACH PARTITION orders_2020;

B. 1. ALTER TABLE orders DETACH PARTITION orders_2020;
2. ALTER TABLE archived_orders ATTACH PARTITION orders_2020 FOR VALUES FROM ('2020-01-01') TO ('2021-01-01');

C. 1. DROP TABLE orders_2020;
2. CREATE TABLE archived_orders PARTITION OF orders FOR VALUES FROM ('2020-01-01') TO ('2021-01-01');

D. 1. ALTER TABLE orders ATTACH PARTITION orders_2020;
2. ALTER TABLE archived_orders DETACH PARTITION orders_2020;

Solution

1. Step 1: Detach the partition from the original table

   Use ALTER TABLE orders DETACH PARTITION orders_2020; to remove the partition without deleting data.

2. Step 2: Attach the detached partition to the new partitioned table

   Use ALTER TABLE archived_orders ATTACH PARTITION orders_2020 FOR VALUES FROM ('2020-01-01') TO ('2021-01-01'); to add it as a partition.

3. Final Answer:

   Detach from orders, then attach to archived_orders with value range. -> Option B

4. Quick Check:

   Detach then attach to new table preserves data [OK]

Hint: Detach first, then attach to new partitioned table [OK]

Common Mistakes:

• Dropping the partition instead of detaching
• Attaching before detaching
• Not specifying value ranges when attaching