Partition types (range, list, hash) in PostgreSQL

Introduction

Partitioning helps split a big table into smaller parts. This makes data easier to manage and faster to search.

You have a large sales table and want to separate data by year.

You want to group customer data by country for quick access.

You want to spread data evenly across parts to balance load.

You want to delete old data easily by removing a partition.

You want to improve query speed by searching only relevant parts.

Syntax

PostgreSQL

CREATE TABLE table_name (
  column1 datatype,
  column2 datatype,
  ...
) PARTITION BY partition_type (column_name);

-- Then create partitions:
CREATE TABLE partition_name PARTITION OF table_name
  FOR VALUES partition_values;

partition_type can be RANGE, LIST, or HASH.

Each partition holds rows matching its defined values.

Examples

This creates a sales table partitioned by date ranges. One partition holds sales in 2023.

PostgreSQL

CREATE TABLE sales (
  id serial PRIMARY KEY,
  sale_date date,
  amount numeric
) PARTITION BY RANGE (sale_date);

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

This partitions customers by country. One partition holds customers from the USA.

PostgreSQL

CREATE TABLE customers (
  id serial PRIMARY KEY,
  name text,
  country text
) PARTITION BY LIST (country);

CREATE TABLE customers_usa PARTITION OF customers
  FOR VALUES IN ('USA');

This partitions logs by hashing user_id into 4 parts. This partition holds remainder 0.

PostgreSQL

CREATE TABLE logs (
  id serial PRIMARY KEY,
  event_time timestamp,
  user_id int
) PARTITION BY HASH (user_id);

CREATE TABLE logs_part1 PARTITION OF logs
  FOR VALUES WITH (MODULUS 4, REMAINDER 0);

Sample Program

This example creates an orders table partitioned by year. It inserts orders in 2023 and 2024, then selects all orders sorted by date.

PostgreSQL

CREATE TABLE orders (
  order_id serial PRIMARY KEY,
  order_date date,
  region text
) PARTITION BY RANGE (order_date);

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

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

INSERT INTO orders (order_date, region) VALUES
  ('2023-05-10', 'North'),
  ('2024-03-15', 'South');

SELECT * FROM orders ORDER BY order_date;

Important Notes

Range partitions split data by continuous ranges, like dates.

List partitions split data by specific values, like countries.

Hash partitions spread data evenly using a hash function, good for load balancing.

Partitioning improves query speed by scanning only relevant partitions.

Common mistake: forgetting to create partitions after defining the main table.

Summary

Partitioning divides big tables into smaller, manageable parts.

Use RANGE for continuous data ranges, LIST for specific values, HASH for even distribution.

Partitions help with faster queries and easier data management.

Practice

1. Which partition type in PostgreSQL is best suited for dividing a table based on continuous ranges of values, such as dates or numbers?

easy

A. HASH partitioning

B. LIST partitioning

C. RANGE partitioning

D. NONE partitioning

Solution

1. Step 1: Understand partition types

   RANGE partitions split data into continuous ranges, like dates or numeric intervals.

2. Step 2: Match partition type to use case

   Since the question asks about continuous ranges, RANGE partitioning fits best.

3. Final Answer:

   RANGE partitioning -> Option C

4. Quick Check:

   Continuous ranges = RANGE partitioning [OK]

Hint: Continuous values? Choose RANGE partitioning [OK]

Common Mistakes:

• Confusing LIST with RANGE for continuous data
• Thinking HASH is for ordered ranges
• Assuming NONE is a valid partition type

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

easy

A. CREATE TABLE sales (id INT, region TEXT) PARTITION BY LIST (region);

B. CREATE TABLE sales PARTITION BY LIST region (id INT, region TEXT);

C. CREATE TABLE sales (id INT, region TEXT) PARTITION BY RANGE (region);

D. CREATE TABLE sales (id INT, region TEXT) PARTITION BY HASH (region);

Solution

1. Step 1: Identify correct PARTITION BY syntax

   PostgreSQL syntax requires PARTITION BY followed by partition type and column in parentheses after table columns.

2. Step 2: Check each option

   CREATE TABLE sales (id INT, region TEXT) PARTITION BY LIST (region); uses correct syntax: columns first, then PARTITION BY LIST (region). Options A, B, C have syntax errors or wrong partition type.

3. Final Answer:

   CREATE TABLE sales (id INT, region TEXT) PARTITION BY LIST (region); -> Option A

4. Quick Check:

   Correct syntax = CREATE TABLE sales (id INT, region TEXT) PARTITION BY LIST (region); [OK]

Hint: PARTITION BY type (column) after columns [OK]

Common Mistakes:

• Placing PARTITION BY before column definitions
• Using wrong partition type for LIST
• Missing parentheses around partition column

3. Given the following partitioned table and inserts:

CREATE TABLE orders (
  order_id INT,
  order_date DATE
) PARTITION BY RANGE (order_date);

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

INSERT INTO orders VALUES (1, '2023-06-15');
INSERT INTO orders VALUES (2, '2022-12-31');

What will happen when the second insert is executed?

medium

A. The row is inserted into orders_2023 partition

B. The row is rejected with a constraint violation error

C. The row is inserted into a default partition automatically

D. The row is inserted into the parent table without partition

Solution

1. Step 1: Understand RANGE partition boundaries

   The orders_2023 partition accepts dates from 2023-01-01 up to but not including 2024-01-01.

2. Step 2: Check the inserted date '2022-12-31'

   This date is before the partition range, so no matching partition exists for it.

3. Step 3: Behavior on no matching partition

   PostgreSQL rejects inserts that don't fit any partition unless a default partition exists (none here).

4. Final Answer:

   The row is rejected with a constraint violation error -> Option B

5. Quick Check:

   Out-of-range insert = error [OK]

Hint: Out-of-range insert without default partition causes error [OK]

Common Mistakes:

• Assuming automatic default partition insertion
• Thinking parent table stores unmatched rows
• Ignoring partition range boundaries

4. Consider this partitioned table creation:

CREATE TABLE employees (
  emp_id INT,
  department TEXT
) PARTITION BY LIST (department);

CREATE TABLE employees_sales PARTITION OF employees FOR VALUES IN ('Sales');
CREATE TABLE employees_hr PARTITION OF employees FOR VALUES IN ('HR');

Which error will occur if you try to insert INSERT INTO employees VALUES (1, 'Marketing');?

medium

A. No partition found for value 'Marketing', insert fails

B. Syntax error due to missing partition

C. Row inserted into employees_sales partition by default

D. Row inserted into parent table without partition

Solution

1. Step 1: Check defined partitions

   Partitions exist only for 'Sales' and 'HR' departments.

2. Step 2: Check inserted value 'Marketing'

   'Marketing' is not listed in any partition's VALUES list.

3. Step 3: PostgreSQL behavior on unmatched LIST value

   Without a default partition, insert fails with no matching partition error.

4. Final Answer:

   No partition found for value 'Marketing', insert fails -> Option A

5. Quick Check:

   Unlisted LIST value = insert failure [OK]

Hint: LIST partition needs matching value or default partition [OK]

Common Mistakes:

• Assuming insert goes to any partition by default
• Expecting parent table to store unmatched rows
• Confusing syntax error with runtime insert error

5. You want to evenly distribute a large table's rows across 4 partitions to improve query performance without caring about specific value ranges. Which partition type and setup is best in PostgreSQL?

hard

A. Use no partitioning and rely on indexes.

B. Use LIST partitioning with 4 specific values.

C. Use RANGE partitioning on a numeric column with 4 ranges.

D. Use HASH partitioning with 4 partitions.

Solution

1. Step 1: Understand partitioning goals

   The goal is even distribution across 4 partitions without caring about value ranges.

2. Step 2: Match partition type to goal

   HASH partitioning evenly distributes rows based on a hash function, ideal for this case.

3. Step 3: Evaluate other options

   RANGE and LIST require specific ranges or values, not suitable for even spread without criteria. No partitioning misses distribution benefits.

4. Final Answer:

   Use HASH partitioning with 4 partitions. -> Option D

5. Quick Check:

   Even distribution = HASH partitioning [OK]

Hint: Even spread without ranges? Choose HASH partitioning [OK]

Common Mistakes:

• Using RANGE or LIST when no value grouping needed
• Thinking indexes replace partitioning benefits
• Confusing HASH with LIST partitioning