Why partitioning is needed in PostgreSQL - See It in Action

Why Partitioning is Needed in PostgreSQL

📖 Scenario: You are managing a large database for an online store. The sales data is growing every day, and queries on this data are becoming slower. You want to organize the data better to improve performance and manageability.

🎯 Goal: Build a simple example to understand why partitioning a table in PostgreSQL helps manage large datasets efficiently.

📋 What You'll Learn

Create a main sales table with sample columns

Create a partition key variable for dividing data

Write SQL to create partitions based on the partition key

Add a final command to attach partitions to the main table

💡 Why This Matters

🌍 Real World

Large databases like sales records grow fast and become slow to query. Partitioning helps keep data manageable and queries fast.

💼 Career

Database administrators and developers use partitioning to optimize performance and maintainability of big data tables.

1

Create the main sales table

Create a table called sales with columns id (integer), sale_date (date), and amount (numeric). This will hold all sales records.

PostgreSQL

-- Create the sales table with id, sale_date, and amount columns
-- Your code here

Hint

Use CREATE TABLE with the specified columns and data types.

2

Define the partition key

Add a column called sale_year of type integer to the sales table. This will be used as the partition key to divide data by year.

PostgreSQL

CREATE TABLE sales (
    id INT,
    sale_date DATE,
    amount NUMERIC
);
-- Add sale_year column of type integer
-- Your code here

Hint

Add the sale_year column inside the table definition.

3

Create partitions by year

Write SQL commands to create two partitions of the sales table: sales_2023 for sale_year = 2023 and sales_2024 for sale_year = 2024. Use PARTITION OF sales syntax.

PostgreSQL

CREATE TABLE sales (
    id INT,
    sale_date DATE,
    amount NUMERIC,
    sale_year INT
);
-- Create sales_2023 partition for sale_year = 2023
-- Create sales_2024 partition for sale_year = 2024
-- Your code here

Hint

Use PARTITION BY LIST (sale_year) in the main table and create partitions with FOR VALUES IN (...).

4

Attach partitions to the main table

Add the final command to attach an existing table sales_archive as a partition of sales for sale_year = 2022. Use ATTACH PARTITION syntax.

PostgreSQL

CREATE TABLE sales (
    id INT,
    sale_date DATE,
    amount NUMERIC,
    sale_year INT
) PARTITION BY LIST (sale_year);

CREATE TABLE sales_2023 PARTITION OF sales FOR VALUES IN (2023);
CREATE TABLE sales_2024 PARTITION OF sales FOR VALUES IN (2024);
-- Attach sales_archive as partition for sale_year = 2022
-- Your code here

Hint

Use ALTER TABLE sales ATTACH PARTITION sales_archive FOR VALUES IN (2022); to attach the partition.

Practice

1. Why is partitioning used in PostgreSQL databases?

easy

A. To combine multiple small tables into one big table

B. To split large tables into smaller, manageable parts for faster queries

C. To encrypt data automatically for security

D. To create backups of the database

Solution

1. Step 1: Understand the purpose of partitioning

   Partitioning divides a large table into smaller pieces called partitions.

2. Step 2: Recognize the benefit of partitioning

   This division helps speed up queries and makes data easier to manage.

3. Final Answer:

   To split large tables into smaller, manageable parts for faster queries -> Option B

4. Quick Check:

   Partitioning = splitting big tables for speed [OK]

Hint: Partitioning breaks big tables into smaller parts [OK]

Common Mistakes:

• Thinking partitioning combines tables instead of splitting
• Confusing partitioning with encryption
• Assuming partitioning is for backups

2. Which of the following is the correct syntax to create a range partitioned table in PostgreSQL?

easy

A. CREATE TABLE sales (id INT, sale_date DATE) PARTITION BY RANGE (sale_date);

B. CREATE TABLE sales PARTITION BY RANGE (sale_date) (id INT, sale_date DATE);

C. CREATE PARTITIONED TABLE sales (id INT, sale_date DATE) BY RANGE (sale_date);

D. CREATE TABLE sales (id INT, sale_date DATE) PARTITION ON RANGE (sale_date);

Solution

1. Step 1: Recall PostgreSQL partition syntax

   The correct syntax places PARTITION BY RANGE after the column definitions.

2. Step 2: Match syntax with options

   CREATE TABLE sales (id INT, sale_date DATE) PARTITION BY RANGE (sale_date); correctly uses: CREATE TABLE ... (columns) PARTITION BY RANGE (column);

3. Final Answer:

   CREATE TABLE sales (id INT, sale_date DATE) PARTITION BY RANGE (sale_date); -> Option A

4. Quick Check:

   Partition syntax = columns then PARTITION BY [OK]

Hint: PARTITION BY RANGE comes after columns in CREATE TABLE [OK]

Common Mistakes:

• Placing PARTITION BY before columns
• Using PARTITION ON instead of PARTITION BY
• Using CREATE PARTITIONED TABLE which is invalid

3. Given a table orders partitioned by range on order_date, what will the query below return?

SELECT count(*) FROM orders WHERE order_date < '2023-01-01';

medium

A. Count of all orders before 2023-01-01 from all relevant partitions

B. Count of orders only from the first partition

C. Syntax error due to partitioning

D. Count of all orders ignoring the date filter

Solution

1. Step 1: Understand partition pruning in PostgreSQL

   PostgreSQL automatically checks only partitions that can contain rows matching the WHERE condition.

2. Step 2: Analyze the query effect

   The query counts rows with order_date before 2023-01-01 across all relevant partitions.

3. Final Answer:

   Count of all orders before 2023-01-01 from all relevant partitions -> Option A

4. Quick Check:

   Partition pruning returns matching rows only [OK]

Hint: Partition pruning counts only matching partitions [OK]

Common Mistakes:

• Thinking query counts only first partition
• Assuming syntax error due to partitioning
• Ignoring WHERE clause and counting all rows

4. You created a partitioned table but your queries are slow. Which of the following is a likely cause?

medium

A. You forgot to create partitions for the table

B. You used too many partitions

C. You used the wrong data type for the partition key

D. You did not create indexes on the partitions

Solution

1. Step 1: Identify common performance issues with partitioning

   Indexes on partitions speed up queries; missing them slows queries.

2. Step 2: Evaluate options

   You did not create indexes on the partitions correctly points out missing indexes as a cause of slow queries.

3. Final Answer:

   You did not create indexes on the partitions -> Option D

4. Quick Check:

   Missing indexes = slow queries [OK]

Hint: Create indexes on partitions for faster queries [OK]

Common Mistakes:

• Assuming missing partitions cause slow queries (usually error instead)
• Thinking wrong data type always slows queries
• Believing too many partitions always slow queries

5. You have a large logs table with millions of rows. You want to improve query speed for recent logs and easily drop old logs. Which partitioning strategy is best?

hard

A. No partitioning, just add indexes

B. Hash partitioning by log message content

C. Range partitioning by log date, creating monthly partitions

D. List partitioning by log severity levels

Solution

1. Step 1: Understand the data and goals

   Logs are time-based; queries focus on recent data and dropping old data is needed.

2. Step 2: Choose partitioning strategy

   Range partitioning by date with monthly partitions allows fast queries on recent logs and easy removal of old partitions.

3. Final Answer:

   Range partitioning by log date, creating monthly partitions -> Option C

4. Quick Check:

   Time-based data = range partitioning [OK]

Hint: Use range partitions by date for time-based data [OK]

Common Mistakes:

• Choosing hash partitioning for time-based queries
• Using list partitioning on severity which doesn't help date queries
• Skipping partitioning and relying only on indexes