0Pricing
Advanced PostgreSQL: Indexing, Partitioning, Replication · 강의

파티션 테이블 관리

파티션을 추가, 삭제, 변경하는 모범 사례와 기본 파티션을 처리하는 방법을 배웁니다.

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

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

Managing Partitioned Tables

As your database grows, managing partitioned tables becomes crucial. This lesson explores how to dynamically add, remove, and modify partitions to keep your data organized and performant.

We'll cover adding new partitions for future data, detaching old partitions for archiving, and attaching existing tables as new partitions. We'll also look at handling data that doesn't fit any defined partition.

Setting Up a Partitioned Table

Before we manage partitions, let's create a base partitioned table. We'll use a simple sales_data table, partitioned by sale_date using a range partitioning strategy.

This table will serve as our example throughout the lesson.

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

-- Add an initial partition for December 2023
CREATE TABLE sales_2023_12 PARTITION OF sales_data
FOR VALUES FROM ('2023-12-01') TO ('2024-01-01');

INSERT INTO sales_data (sale_date, amount) VALUES ('2023-12-15', 150.75);
SELECT * FROM sales_data;

Adding New Partitions

As time passes, you'll need to add new partitions for incoming data. This is typically done using the CREATE TABLE ... PARTITION OF ... command, similar to how we created the initial partition.

This method creates a new, empty child table and links it to the parent partitioned table for a specified range of values.

Example: Adding a New Month

Let's add a partition for January 2024. This ensures that any new sales data for January will automatically be directed to its own dedicated storage segment.

Notice how we define the specific date range for this new partition.

-- Add a partition for January 2024
CREATE TABLE sales_2024_01 PARTITION OF sales_data
FOR VALUES FROM ('2024-01-01') TO ('2024-02-01');

INSERT INTO sales_data (sale_date, amount) VALUES ('2024-01-20', 200.50);

-- Verify data is in the correct partition (optional check)
SELECT tableoid::regclass, * FROM sales_data WHERE sale_date = '2024-01-20';

Detaching Old Partitions

Over time, older partitions might contain historical data that is rarely accessed but still needs to be preserved. Detaching a partition allows you to remove it from the partitioned table structure without deleting the data.

The detached partition becomes a standalone, regular table, which can then be archived, moved, or even dropped if no longer needed.

Example: Archiving Old Data

Let's detach the sales_2023_12 partition. After detachment, it will exist as a separate table named sales_2023_12, no longer part of the sales_data partitioned table.

This is useful for reducing the active dataset size for queries.

-- Detach the December 2023 partition
ALTER TABLE sales_data DETACH PARTITION sales_2023_12;

-- The detached table still exists and contains its data
SELECT * FROM sales_2023_12;

-- Trying to query sales_data for Dec 2023 will now return nothing
SELECT * FROM sales_data WHERE sale_date = '2023-12-15';

Attaching Existing Tables

Sometimes you might have a large dataset in a regular table that you want to integrate into a partitioned table. Instead of inserting all data, you can attach that existing table as a new partition.

The table to be attached must be empty or contain only data that satisfies the partition's constraints. This is a very fast operation as it doesn't involve data movement.

Example: Attaching a Prepared Table

Imagine we have a standalone table, sales_2024_02_temp, containing February 2024 sales. We can quickly attach it to our sales_data partitioned table.

First, we create and populate the temporary table, then attach it.

-- Create a standalone table for February 2024 sales
CREATE TABLE sales_2024_02_temp (
  id SERIAL,
  sale_date DATE,
  amount DECIMAL(10, 2)
);
INSERT INTO sales_2024_02_temp (sale_date, amount) VALUES ('2024-02-10', 300.25);

-- Attach this table as a new partition
ALTER TABLE sales_data ATTACH PARTITION sales_2024_02_temp
FOR VALUES FROM ('2024-02-01') TO ('2024-03-01');

-- Now, sales_data can query the February data
SELECT * FROM sales_data WHERE sale_date = '2024-02-10';

Handling Undefined Data with DEFAULT

What happens if data comes in that doesn't fit any of your defined partition ranges? By default, it would cause an error. To prevent this, you can create a DEFAULT partition.

The default partition acts as a catch-all for any rows that don't match the criteria of other existing partitions. It's essential for robustness and preventing data loss.

Example: Creating a Default Partition

Let's add a default partition to our sales_data table. Then, we'll try inserting a sale from a future date (e.g., 2025) for which no explicit partition exists.

This data will automatically be routed to the sales_default partition.

-- Create a default partition
CREATE TABLE sales_default PARTITION OF sales_data DEFAULT;

-- Insert data that doesn't fit existing ranges (e.g., 2025)
INSERT INTO sales_data (sale_date, amount) VALUES ('2025-01-05', 450.99);

-- Verify data went to the default partition
SELECT tableoid::regclass, * FROM sales_data WHERE sale_date = '2025-01-05';

Partition Management Check

You've learned how to dynamically adjust your partitioned table structure.

Recap: Partition Management

In this lesson, you mastered key aspects of managing partitioned tables:

  • Adding new partitions: Use CREATE TABLE ... PARTITION OF ... to prepare for new data ranges.
  • Detaching partitions: The ALTER TABLE ... DETACH PARTITION ... command removes a partition from the set, turning it into an independent table for archiving or separate management.
  • Attaching partitions: Use ALTER TABLE ... ATTACH PARTITION ... to quickly integrate an existing regular table as a new partition.
  • Default partitions: Create a DEFAULT partition to catch any data that doesn't match other defined partition boundaries, ensuring data integrity.

These techniques empower you to maintain flexible, performant, and scalable database systems.

자주 묻는 질문

“파티션 테이블 관리” 강의는 무료인가요?

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

“파티션 테이블 관리”에서 뭘 배우나요?

파티션을 추가, 삭제, 변경하는 모범 사례와 기본 파티션을 처리하는 방법을 배웁니다. 브라우저에서 직접 실행하는 실습 코드로 Advanced PostgreSQL: Indexing, Partitioning, Replication을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

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

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

“파티션 테이블 관리” 강의는 얼마나 걸리나요?

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

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

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

이 강의의 모든 강의

  1. 분산을 위한 해시 파티셔닝
  2. 하위 파티셔닝 기법
  3. 파티션 테이블 관리
  4. 시간 기준 범위 파티셔닝
← Advanced PostgreSQL: Indexing, Partitioning, Replication(으)로 돌아가기