Partition pruning behavior in PostgreSQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is partition pruning in PostgreSQL?

Partition pruning is a technique where PostgreSQL skips scanning partitions that cannot contain any matching rows for a query, improving query performance.

intermediate

When does PostgreSQL perform partition pruning?

PostgreSQL performs partition pruning during query planning and execution phases to avoid scanning irrelevant partitions based on query conditions.

intermediate

What types of partition pruning does PostgreSQL support?

PostgreSQL supports static pruning (at plan time) and dynamic pruning (at execution time) to exclude partitions based on query parameters.

advanced

How does dynamic partition pruning differ from static pruning?

Static pruning happens during query planning using constant values, while dynamic pruning happens during execution using parameter values or runtime information.

beginner

Why is partition pruning important for large partitioned tables?

Partition pruning reduces the amount of data scanned by skipping irrelevant partitions, which speeds up queries and reduces resource usage on large partitioned tables.

What does partition pruning help improve in PostgreSQL?

A Query performance by skipping irrelevant partitions

B Data insertion speed

C Backup compression

D Index creation time

Partition pruning improves query performance by avoiding scanning partitions that cannot contain matching rows.

When does static partition pruning occur?

A During query planning

B During query execution

C During data insertion

D During index creation

Static pruning happens during query planning using constant query values.

Dynamic partition pruning uses which of the following to prune partitions?

A Constant values only

B Index metadata

C Table statistics only

D Runtime parameters or execution-time info

Dynamic pruning uses runtime parameters or execution-time information to prune partitions.

Which PostgreSQL feature helps reduce scanned data on large partitioned tables?

A Replication

B Partition pruning

C Vacuuming

D Triggers

Partition pruning reduces scanned data by skipping irrelevant partitions.

Partition pruning is most effective when queries include conditions on:

A Random columns

B Non-indexed columns

C Partition key columns

D System columns

Pruning works best when queries filter on partition key columns.

Explain how partition pruning works in PostgreSQL and why it improves query performance.

Think about how skipping parts of data helps queries run faster.

Describe the difference between static and dynamic partition pruning in PostgreSQL.

Consider when the pruning decision happens and what information it uses.

Practice

1. What is the main purpose of partition pruning in PostgreSQL?

easy

A. To merge all partitions into one table

B. To create new partitions automatically

C. To skip scanning partitions that cannot contain matching rows

D. To backup partitions separately

Solution

1. Step 1: Understand partition pruning concept

   Partition pruning means the database avoids scanning partitions that do not match the query filter.

2. Step 2: Identify the main benefit

   This skipping reduces query time by focusing only on relevant partitions.

3. Final Answer:

   To skip scanning partitions that cannot contain matching rows -> Option C

4. Quick Check:

   Partition pruning = skip irrelevant partitions [OK]

Hint: Partition pruning skips irrelevant partitions to speed queries [OK]

Common Mistakes:

• Thinking pruning merges partitions
• Assuming pruning creates partitions
• Confusing pruning with backup

2. Which of the following WHERE clauses will enable partition pruning on a table partitioned by column region?

easy

A. WHERE region = 'US'

B. WHERE UPPER(region) = 'US'

C. WHERE LENGTH(region) > 2

D. WHERE region LIKE '%US%'

Solution

1. Step 1: Identify pruning conditions

   Partition pruning works best with simple direct comparisons on the partition key.

2. Step 2: Analyze each option

   WHERE region = 'US' uses a direct equality on region, enabling pruning. Options A, B, and D use functions or patterns, preventing pruning.

3. Final Answer:

   WHERE region = 'US' -> Option A

4. Quick Check:

   Simple equality on partition key enables pruning [OK]

Hint: Use simple column = value filters on partition keys [OK]

Common Mistakes:

• Using functions on partition keys disables pruning
• Using LIKE patterns disables pruning
• Assuming any WHERE clause prunes partitions

3. Given a table sales partitioned by year with partitions for 2021 and 2022, what will the query below scan?

SELECT * FROM sales WHERE year = 2021;

medium

A. Only the 2021 partition

B. Both 2021 and 2022 partitions

C. No partitions, query returns empty

D. All partitions plus a full table scan

Solution

1. Step 1: Understand partition pruning with equality filter

   The query filters on year = 2021, which matches exactly one partition.

2. Step 2: Determine scanned partitions

   PostgreSQL will prune and scan only the 2021 partition, skipping 2022.

3. Final Answer:

   Only the 2021 partition -> Option A

4. Quick Check:

   Filter on partition key = value scans matching partition only [OK]

Hint: Equality on partition key scans only matching partition [OK]

Common Mistakes:

• Assuming all partitions scan regardless of filter
• Thinking query returns empty if filter matches a partition
• Believing full table scan always happens

4. You wrote this query on a partitioned table orders partitioned by order_date:

SELECT * FROM orders WHERE EXTRACT(YEAR FROM order_date) = 2023;

Why might partition pruning NOT occur?

medium

A. Partition pruning only works with numeric columns

B. Using a function on the partition key disables pruning

C. The query syntax is invalid

D. Partition pruning requires an index on order_date

Solution

1. Step 1: Identify pruning limitation

   Partition pruning requires direct use of the partition key in filters without wrapping functions.

2. Step 2: Analyze the query

   The query uses EXTRACT(YEAR FROM order_date), a function on the partition key, preventing pruning.

3. Final Answer:

   Using a function on the partition key disables pruning -> Option B

4. Quick Check:

   Functions on partition keys disable pruning [OK]

Hint: Avoid functions on partition keys for pruning [OK]

Common Mistakes:

• Thinking pruning needs indexes
• Believing pruning works with any filter
• Assuming query syntax error causes pruning failure

5. A table events is range partitioned by event_date with monthly partitions. You want to query events in March 2023. Which query will maximize partition pruning?

hard

A. SELECT * FROM events WHERE event_date BETWEEN '2023-02-28' AND '2023-03-31';

B. SELECT * FROM events WHERE EXTRACT(MONTH FROM event_date) = 3 AND EXTRACT(YEAR FROM event_date) = 2023;

C. SELECT * FROM events WHERE TO_CHAR(event_date, 'YYYY-MM') = '2023-03';

D. SELECT * FROM events WHERE event_date >= '2023-03-01' AND event_date < '2023-04-01';

Solution

1. Step 1: Understand pruning with range partitions

   Range partitions work best with direct range conditions on the partition key.

2. Step 2: Evaluate each query

   SELECT * FROM events WHERE event_date >= '2023-03-01' AND event_date < '2023-04-01'; uses a direct range filter on event_date, enabling pruning. Options B and C use functions, disabling pruning. SELECT * FROM events WHERE event_date BETWEEN '2023-02-28' AND '2023-03-31'; includes dates outside March, scanning extra partitions.

3. Final Answer:

   SELECT * FROM events WHERE event_date >= '2023-03-01' AND event_date < '2023-04-01'; -> Option D

4. Quick Check:

   Direct range filters maximize pruning [OK]

Hint: Use direct range filters on partition keys for pruning [OK]

Common Mistakes:

• Using functions disables pruning
• Including extra dates scans more partitions
• Assuming BETWEEN always prunes perfectly