0Pricing
PostgreSQL Performance & Query Optimization · Leçon

Élagage des partitions lors de la planification et de l’exécution

Lisez la sortie de EXPLAIN pour confirmer que l’élagage statique et l’élagage à l’exécution éliminent les partitions inutiles de vos requêtes.

Élagage des partitions lors de la planification et de l’exécution est une leçon PostgreSQL Performance & Query Optimization gratuite sur CoddyKit. Ceci est la leçon 2 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage PostgreSQL Performance & Query Optimization, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours PostgreSQL Performance & Query Optimization comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

Why Partition Pruning Matters

You partitioned a huge table so PostgreSQL can skip partitions that cannot contain matching rows. That skipping is called partition pruning.

Without pruning, a query that touches one month of data could still scan every partition for every month. The whole performance benefit of partitioning depends on the planner (and sometimes the executor) recognising which partitions are relevant.

  • Plan-time pruning happens when the planner already knows the filter values.
  • Execution-time pruning happens when the values are only known once the query runs.

In this lesson you will learn to confirm both kinds by reading EXPLAIN output.

Our Example Table

Throughout the lesson we use a range-partitioned events table, partitioned by month on created_at. Each child partition holds one month of rows.

This is the classic time-series layout where pruning pays off the most: queries usually target a narrow date range, so most partitions should be skipped entirely.

CREATE TABLE events (
    id          bigint        NOT NULL,
    created_at  timestamptz   NOT NULL,
    user_id     bigint        NOT NULL,
    payload     jsonb
) PARTITION BY RANGE (created_at);

CREATE TABLE events_2024_01 PARTITION OF events
    FOR VALUES FROM ('2024-01-01') TO ('2024-02-01');
CREATE TABLE events_2024_02 PARTITION OF events
    FOR VALUES FROM ('2024-02-01') TO ('2024-03-01');
CREATE TABLE events_2024_03 PARTITION OF events
    FOR VALUES FROM ('2024-03-01') TO ('2024-04-01');

Static Pruning at Plan Time

When the filter compares the partition key to a constant, the planner can decide which partitions to touch before execution. This is static (plan-time) pruning.

Run EXPLAIN on a query restricted to one month. The plan should reference only the matching partition(s); the others never appear.

The setting enable_partition_pruning (on by default) controls this behaviour.

EXPLAIN
SELECT count(*)
FROM events
WHERE created_at >= '2024-02-10'
  AND created_at <  '2024-02-20';

Reading the Pruned Plan

Here is the shape of the plan for that single-month query. Notice only events_2024_02 is scanned. events_2024_01 and events_2024_03 are absent from the plan entirely.

  • The Append (or Seq Scan with one child) lists only surviving partitions.
  • Pruned partitions leave no trace in the plan output.

This is the clearest confirmation of static pruning: count the partitions in the plan and compare against how many exist.

Aggregate
  ->  Seq Scan on events_2024_02 events
        Filter: ((created_at >= '2024-02-10'::timestamptz)
             AND (created_at <  '2024-02-20'::timestamptz))

When the Plan Still Lists Every Partition

If your EXPLAIN shows an Append over all partitions, static pruning did not apply. Common causes:

  • The filter does not reference the partition key (e.g. filtering on user_id only).
  • A function wraps the key, e.g. date(created_at) = '2024-02-10', hiding the relationship from the planner.
  • The value is not a constant at plan time (parameter or join column) — that needs execution-time pruning.

Keep the partition key bare on one side of the comparison so the planner can match it to partition bounds.

-- This DEFEATS static pruning: function wraps the key
EXPLAIN SELECT count(*) FROM events
WHERE date(created_at) = '2024-02-15';

-- This ENABLES it: bare key compared to constants
EXPLAIN SELECT count(*) FROM events
WHERE created_at >= '2024-02-15'
  AND created_at <  '2024-02-16';

Why Parameters Need a Different Approach

With a prepared statement or a value supplied at run time, the planner may not know the constant when it builds the plan. A generic plan must stay valid for any parameter value, so it cannot statically prune.

Instead PostgreSQL defers the decision: it keeps all partitions in the plan but adds the ability to skip them while the query executes. This is execution-time (runtime) pruning.

PREPARE month_count(timestamptz, timestamptz) AS
  SELECT count(*) FROM events
  WHERE created_at >= $1 AND created_at < $2;

EXPLAIN EXECUTE month_count('2024-03-01', '2024-04-01');

Spotting Execution-Time Pruning in the Plan

Runtime pruning advertises itself in EXPLAIN with two key markers under an Append node:

  • Subplans Removed: N — partitions discarded before scanning.
  • For parameterised plans, a line like Filter or initplan parameters that drive the pruning.

If you see Subplans Removed, the executor pruned partitions at run time. If you see neither that nor a reduced partition list, no pruning occurred.

Aggregate
  ->  Append
        Subplans Removed: 2
        ->  Seq Scan on events_2024_03 events_1
              Filter: ((created_at >= $1) AND (created_at < $2))

Runtime Pruning from Nested Loop Joins

Execution-time pruning is not only for parameters. It also kicks in when the partition key is compared to a value produced by the outer side of a join (a Nested Loop), or by a subquery.

Each outer row supplies a key value, and for each one the executor prunes down to the relevant partition. This is extremely valuable for selective lookups against a partitioned fact table.

EXPLAIN (ANALYZE, COSTS OFF)
SELECT e.*
FROM date_filter df
JOIN events e
  ON e.created_at >= df.start_ts
 AND e.created_at <  df.end_ts;

Use EXPLAIN ANALYZE to Confirm It Actually Ran

Plain EXPLAIN shows what could be pruned. To prove pruning happened during a real run — especially runtime pruning — use EXPLAIN ANALYZE.

  • Subplans Removed: N appears with the actual number removed at execution.
  • Surviving partitions show actual rows; pruned ones show (never executed) if they remain as subnodes.

Reading actual time and actual rows per partition tells you exactly which children did work.

EXPLAIN (ANALYZE, BUFFERS)
EXECUTE month_count('2024-03-01', '2024-04-01');

Pruning Is Not the Same as Constraint Exclusion

Older PostgreSQL relied on constraint_exclusion for inheritance-based partitioning. Modern declarative partitioning uses partition pruning, which is faster and supports runtime pruning.

  • enable_partition_pruning = on drives the new mechanism (plan and execution time).
  • constraint_exclusion only ever worked at plan time and only with CHECK constraints.

For declarative partitions, leave enable_partition_pruning on and do not depend on constraint_exclusion.

SHOW enable_partition_pruning;   -- expect: on
SHOW constraint_exclusion;        -- 'partition' (legacy default)

A Practical Checklist

When verifying pruning on a real query, work through this list:

  • Is the partition key in the predicate, bare and SARGable? No wrapping functions, no implicit casts that block matching.
  • Static case: run EXPLAIN — do pruned partitions disappear from the plan?
  • Runtime case: look for Subplans Removed: N under Append.
  • Confirm with EXPLAIN ANALYZE that only the expected partitions did work.
  • Check the setting if nothing prunes: enable_partition_pruning must be on.

Quick Check

A prepared statement filters a range-partitioned table on its partition key, using a bound parameter. You run EXPLAIN ANALYZE EXECUTE and want to confirm pruning happened.

Recap

You can now confirm partition pruning from EXPLAIN output:

  • Static pruning happens at plan time when the partition key is compared to constants; pruned partitions simply vanish from the plan.
  • Execution-time pruning handles parameters and join-driven values; look for Subplans Removed: N under Append.
  • Keep the partition key bare and SARGable — wrapping it in a function blocks pruning.
  • Use EXPLAIN ANALYZE to prove which partitions actually did work, and verify enable_partition_pruning is on when nothing prunes.

Reading these markers turns partitioning from a hopeful design into a verified performance win.

Questions Fréquemment Posées

La leçon « Élagage des partitions lors de la planification et de l’exécution » est-elle gratuite ?

Oui — le texte complet de « Élagage des partitions lors de la planification et de l’exécution » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours PostgreSQL Performance & Query Optimization, passe à CoddyKit PRO. Le cours PostgreSQL Performance & Query Optimization comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Élagage des partitions lors de la planification et de l’exécution » ?

Lisez la sortie de EXPLAIN pour confirmer que l’élagage statique et l’élagage à l’exécution éliminent les partitions inutiles de vos requêtes. Tu pratiques PostgreSQL Performance & Query Optimization avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer PostgreSQL Performance & Query Optimization ?

Aucune expérience préalable n'est requise. PostgreSQL Performance & Query Optimization sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 2 sur 4.

Combien de temps prend la leçon « Élagage des partitions lors de la planification et de l’exécution » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon PostgreSQL Performance & Query Optimization ?

Oui. Chaque leçon PostgreSQL Performance & Query Optimization inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

  1. Choisir une clé et une stratégie de partitionnement
  2. Élagage des partitions lors de la planification et de l’exécution
  3. Automatiser la création et la conservation des partitions
  4. Migrer une table volumineuse vers des partitions en ligne
← Retour à PostgreSQL Performance & Query Optimization