PostgreSQL Tutorial: Reasons Partition Pruning Not Work

July 3, 2024

Summary: in this tutorial, you will learn the major reasons why the partition pruning not work in PostgreSQL.

Table of Contents


Partition pruning is a performance optimization feature in PostgreSQL that helps in improving query performance by allowing the query planner and executor to skip scanning partitions that are not relevant to the query. However, there are some cases where partition pruning might not work as expected. Understanding these scenarios can help in diagnosing and fixing related issues.

Reasons partition pruning may not work

Dynamic partition pruning limitations

Dynamic partition pruning happens during query execution time, but its effectiveness can be limited if the query’s join conditions or filter criteria do not allow for clear identification of irrelevant partitions early on.

Use of non-immutable functions in WHERE clause

When the WHERE clause involves non-immutable functions, PostgreSQL might not be able to perform partition pruning at plan time since it cannot guarantee the function’s return value will remain constant.

SELECT * FROM partitioned_table
  WHERE to_char(date_column, 'YYYY-MM-DD') = '2024-04-15';

In the above query, to_char is a stable, not immutable, function, possibly affecting pruning.

Lack of statistics or outdated statistics

PostgreSQL relies on table statistics for making informed decisions about partition pruning. If the statistics are not up-to-date or missing, it might lead to inefficient pruning decisions.

To update statistics, you can:

ANALYZE partitioned_table;

Misconfigured partitioning key or strategy

Incorrect configuration of partition keys or choosing a suboptimal partitioning strategy (e.g., range vs. list partitioning) based on the query patterns can also impact pruning efficiency.

The influence of OR conditions and parameterized queries

Complex OR conditions or parameterized queries, especially those built dynamically without literals, may impede effective partition pruning since the planner may find it challenging to deduce the exact partitions involved.

Ensuring Effective Partition Pruning

  • Use immutable functions in partition keys: Ensure your partition keys and any functions used on them in queries are immutable.
  • Keep statistics updated: Regularly update the table statistics using the ANALYZE command.
  • Simplify query conditions: Simplify your query conditions and avoid using non-immutable functions on partition keys within WHERE clauses.
  • Review partitioning strategy: Make sure the partitioning strategy aligns with the most common access patterns of your queries.


By understanding these points, you can diagnose why partition pruning might not be working as expected in your PostgreSQL database and take appropriate steps to optimize your partitioned tables for better performance.