Advanced PostgreSQL: Indexing, Partitioning, Replication · レッスン

パーティションテーブルの管理

パーティションの追加、削除、変更、およびデフォルトパーティションの扱いに関するベストプラクティスを学びます。

「パーティションテーブルの管理」はCoddyKit上の無料Advanced PostgreSQL: Indexing, Partitioning, Replicationレッスンです。これはレッスン3/4です。下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応の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時間対応のAIチューター）、Advanced PostgreSQL: Indexing, Partitioning, Replicationコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 Advanced PostgreSQL: Indexing, Partitioning, Replicationコースには全4レッスンが含まれています。

「パーティションテーブルの管理」で何を学びますか？

パーティションの追加、削除、変更、およびデフォルトパーティションの扱いに関するベストプラクティスを学びます。ブラウザで直接実行するハンズオンコードでAdvanced PostgreSQL: Indexing, Partitioning, Replicationを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

Advanced PostgreSQL: Indexing, Partitioning, Replicationを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのAdvanced PostgreSQL: Indexing, Partitioning, Replicationは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。これはレッスン3/4です。

「パーティションテーブルの管理」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このAdvanced PostgreSQL: Indexing, Partitioning, Replicationレッスンでコードを書いて実行できますか？

はい。すべてのAdvanced PostgreSQL: Indexing, Partitioning, Replicationレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

← Advanced PostgreSQL: Indexing, Partitioning, Replicationに戻る