Range partitioning by date in PostgreSQL - Step-by-Step Execution

Concept Flow - Range partitioning by date

Create main partitioned table

↓

Define partitions with date ranges

↓

Insert data into main table

↓

PostgreSQL routes data to correct partition

↓

Query data from main table

↓

Data fetched from relevant partitions

Create a main table partitioned by date ranges, define partitions for specific date intervals, insert data routed automatically, and query data efficiently.

Execution Sample

PostgreSQL

CREATE TABLE sales (
  id SERIAL PRIMARY KEY,
  sale_date DATE NOT NULL,
  amount NUMERIC
) PARTITION BY RANGE (sale_date);

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

Creates a sales table partitioned by sale_date with a partition for all sales in 2023.

Execution Table

Step	Action	Input Data	Partition Chosen	Result
1	Create main partitioned table	N/A	N/A	Table 'sales' created with RANGE partition on sale_date
2	Create partition for 2023	N/A	2023-01-01 to 2023-12-31	Partition 'sales_2023' created
3	Insert row with sale_date = '2023-05-10'	{id:1, sale_date:'2023-05-10', amount:100}	sales_2023	Row inserted into 'sales_2023'
4	Insert row with sale_date = '2022-12-31'	{id:2, sale_date:'2022-12-31', amount:50}	No matching partition	Error: no partition for this date
5	Query sales for 2023	sale_date BETWEEN '2023-01-01' AND '2023-12-31'	sales_2023	Returns rows from 'sales_2023' partition
6	Query sales for all dates	N/A	All partitions	Returns rows from all partitions
7	Insert row with sale_date = '2024-01-01'	{id:3, sale_date:'2024-01-01', amount:200}	No matching partition	Error: no partition for this date

💡 Execution stops when inserting data outside defined partitions or after all queries complete.

Variable Tracker

Variable	Start	After Step 3	After Step 4	After Step 7
sales table partitions	[]	[sales_2023]	[sales_2023]	[sales_2023]

Key Moments - 3 Insights

Why does inserting a row with sale_date '2022-12-31' cause an error?

Because there is no partition defined for dates before '2023-01-01', so PostgreSQL cannot find a partition to store that row (see execution_table step 4).

How does PostgreSQL decide which partition to insert data into?

It checks the sale_date value against the defined range partitions and routes the row to the matching partition automatically (see execution_table step 3).

What happens if you query the main table without specifying a date range?

PostgreSQL fetches data from all partitions transparently, combining results as if from a single table (see execution_table step 6).

Visual Quiz - 3 Questions

Look at the execution_table, at which step does an insert fail due to no matching partition?

A Step 3

B Step 5

C Step 4

D Step 6

💡 Hint

Check the 'Result' column for errors related to partition matching.

According to variable_tracker, how many partitions exist after step 3?

A 1

B 0

C 2

D 3

💡 Hint

Look at the 'After Step 3' column for 'sales table partitions'.

If you insert a row with sale_date '2024-01-01', what will happen according to the execution_table?

A Row inserted into a new partition

B Error: no partition for this date

C Row inserted into sales_2023

D Row inserted into main table without partition

💡 Hint

See step 7 in execution_table for inserting dates outside defined partitions.

Concept Snapshot

Range partitioning by date in PostgreSQL:
- Create main table with PARTITION BY RANGE on a date column.
- Define partitions with FOR VALUES FROM ... TO ... specifying date ranges.
- Inserts route automatically to matching partitions.
- Queries on main table access relevant partitions transparently.
- Inserts outside defined ranges cause errors.

Full Transcript

Range partitioning by date in PostgreSQL involves creating a main table partitioned by a date column using RANGE partitioning. You define partitions for specific date intervals. When you insert data, PostgreSQL automatically routes rows to the correct partition based on the date value. Queries on the main table fetch data from the relevant partitions without extra effort. If you try to insert data with a date outside the defined partitions, PostgreSQL raises an error because it cannot find a suitable partition. This method helps organize data by date ranges for better performance and management.

Practice

1. What is the main purpose of range partitioning by date in PostgreSQL?

easy

A. To create random partitions without any order

B. To split data into parts based on date ranges for better management

C. To encrypt date columns for security

D. To combine all data into a single large table

Solution

1. Step 1: Understand range partitioning concept

   Range partitioning divides data into segments based on continuous ranges, such as dates.

2. Step 2: Identify the purpose of date-based partitioning

   Using date ranges helps organize data by time periods, improving query speed and management.

3. Final Answer:

   To split data into parts based on date ranges for better management -> Option B

4. Quick Check:

   Range partitioning by date = split data by date ranges [OK]

Hint: Range partitioning splits data by continuous date intervals [OK]

Common Mistakes:

• Thinking partitioning combines data instead of splitting
• Confusing partitioning with encryption
• Assuming partitions are random, not range-based

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

easy

A. CREATE TABLE orders (id INT, order_date DATE) PARTITION BY RANGE (order_date);

B. CREATE TABLE orders PARTITION BY RANGE (order_date) (id INT, order_date DATE);

C. CREATE TABLE orders (id INT, order_date DATE) PARTITION BY LIST (order_date);

D. CREATE TABLE orders (id INT, order_date DATE) PARTITION BY HASH (order_date);

Solution

1. Step 1: Check correct partitioning clause placement

   In PostgreSQL, PARTITION BY RANGE (column) comes after table columns definition.

2. Step 2: Identify correct partition type for date ranges

   Range partitioning is used for continuous ranges like dates, so PARTITION BY RANGE is correct.

3. Final Answer:

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

4. Quick Check:

   Syntax: columns then PARTITION BY RANGE [OK]

Hint: Define columns first, then PARTITION BY RANGE (date_column) [OK]

Common Mistakes:

• Placing PARTITION BY before columns
• Using LIST or HASH instead of RANGE for dates
• Incorrect syntax order causing errors

3. Given the following partitioned table and partitions:

CREATE TABLE sales (id INT, sale_date DATE) PARTITION BY RANGE (sale_date);
CREATE TABLE sales_2023 PARTITION OF sales FOR VALUES FROM ('2023-01-01') TO ('2024-01-01');
CREATE TABLE sales_2024 PARTITION OF sales FOR VALUES FROM ('2024-01-01') TO ('2025-01-01');

What will be the result of this query?

SELECT tableoid::regclass, * FROM sales WHERE sale_date = '2023-06-15';

medium

A. Returns rows from sales_2024 partition with sale_date '2023-06-15'

B. Returns no rows because '2023-06-15' is not in any partition

C. Returns rows from both partitions

D. Returns rows from sales_2023 partition with sale_date '2023-06-15'

Solution

1. Step 1: Identify which partition contains '2023-06-15'

   The date '2023-06-15' falls between '2023-01-01' and '2024-01-01', so it belongs to sales_2023 partition.

2. Step 2: Understand query behavior on partitioned tables

   Query on partitioned table routes to matching partition(s) based on WHERE clause; here, only sales_2023 matches.

3. Final Answer:

   Returns rows from sales_2023 partition with sale_date '2023-06-15' -> Option D

4. Quick Check:

   Date in sales_2023 range = rows from sales_2023 [OK]

Hint: Check date range to find correct partition for query [OK]

Common Mistakes:

• Choosing wrong partition based on date
• Assuming query scans all partitions
• Ignoring partition boundaries

4. You try to create a partition for a range partitioned table by date with this command:

CREATE TABLE sales_2025 PARTITION OF sales FOR VALUES FROM ('2025-01-01') TO ('2024-12-31');

What is the problem with this statement?

medium

A. The TO date is earlier than the FROM date, causing a range error

B. Partition names cannot contain numbers

C. You must specify LIST partitioning, not RANGE

D. The sales table must be dropped before adding partitions

Solution

1. Step 1: Check the FROM and TO values in partition definition

   The TO value '2024-12-31' is before the FROM value '2025-01-01', which is invalid for range partitions.

2. Step 2: Understand partition range rules

   Range partitions require FROM value to be less than TO value to define a valid range.

3. Final Answer:

   The TO date is earlier than the FROM date, causing a range error -> Option A

4. Quick Check:

   FROM must be less than TO in range partitions [OK]

Hint: FROM date must be before TO date in range partitions [OK]

Common Mistakes:

• Swapping FROM and TO dates
• Thinking partition names cannot have numbers
• Confusing range with list partitioning

5. You have a large sales table partitioned by month using range partitioning on sale_date. You want to add a new partition for March 2024. Which of the following commands correctly adds this partition?

hard

A. CREATE TABLE sales_2024_03 PARTITION OF sales FOR VALUES FROM ('2024-03-01') TO ('2024-03-31');

B. CREATE TABLE sales_2024_03 PARTITION OF sales FOR VALUES FROM ('2024-02-28') TO ('2024-03-31');

C. CREATE TABLE sales_2024_03 PARTITION OF sales FOR VALUES FROM ('2024-03-01') TO ('2024-04-01');

D. CREATE TABLE sales_2024_03 PARTITION OF sales FOR VALUES FROM ('2024-03-01') TO ('2024-03-30');

Solution

1. Step 1: Understand range partition boundaries for months

   Range partitions use inclusive FROM and exclusive TO, so March 2024 is from '2024-03-01' up to but not including '2024-04-01'.

2. Step 2: Check each option's date range correctness

   CREATE TABLE sales_2024_03 PARTITION OF sales FOR VALUES FROM ('2024-03-01') TO ('2024-04-01'); correctly uses FROM '2024-03-01' TO '2024-04-01'. Options B, C, and D have incorrect boundaries that either overlap or exclude days.

3. Final Answer:

   CREATE TABLE sales_2024_03 PARTITION OF sales FOR VALUES FROM ('2024-03-01') TO ('2024-04-01'); -> Option C

4. Quick Check:

   Range partitions: FROM inclusive, TO exclusive [OK]

Hint: Use TO date as first day of next month for monthly partitions [OK]

Common Mistakes:

• Using TO date as last day of month (should be exclusive)
• Overlapping partition ranges
• Using incorrect FROM dates