Partition pruning during query execution
Recorded source states and original language descriptions. Missing version evidence stays unknown.
The source snapshot records transitions for PostgreSQL 8.1–18. The historical matrix records independent cells for 7.4–18. Neither records support for PostgreSQL 19 or 20; newer versions remain unknown. These source claims are distinct from runtime measurements.
Partitioning & Inheritance
Description
Queries on partitioned tables can eliminate partitions during query execution time, instead of only at query planning time. This allows PostgreSQL to use information that becomes available during query execution to further prune the number of partitions it needs to use, leading to improved query performance.
Selected version: PostgreSQL 18
Yes
Compare versions
Original documentation links
Recorded legacy identifiers: 332
Complete source facts and provenance
yaml · center · 1dd22bf9a7f3ec325b894e2836fda535a25529f246a94dd41d6abbfe9997f7fd
{
"Key": "partition-pruning-during-query-execution",
"SourceKind": "yaml",
"SourceDatabase": "center",
"SourceTable": "featurematrix.yaml",
"SourceKey": "Partition pruning during query execution",
"SourceHash": "1dd22bf9a7f3ec325b894e2836fda535a25529f246a94dd41d6abbfe9997f7fd",
"Name": "Partition pruning during query execution",
"NameLocale": "en",
"GroupKey": "partitioning-inheritance",
"GroupName": "Partitioning \u0026 Inheritance",
"GroupLocale": "en",
"Ordinal": 6,
"GroupOrder": 7,
"Facts": {
"feature": {
"description": "Queries on partitioned tables can eliminate partitions during query execution time, instead of only at query planning time. This allows PostgreSQL to use information that becomes available during query execution to further prune the number of partitions it needs to use, leading to improved query performance.",
"name": "Partition pruning during query execution",
"versions": {
"11": "Yes"
}
},
"group": "Partitioning \u0026 Inheritance",
"versions": {
"max": 18,
"min": 8.1
}
},
"Cells": [
{
"Version": "10",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "11",
"State": "yes",
"EvidenceKind": "yaml-transition",
"TransitionVersion": "11",
"Supported": true,
"Original": "Yes"
},
{
"Version": "12",
"State": "yes",
"EvidenceKind": "yaml-transition",
"TransitionVersion": "11",
"Supported": true,
"Original": "Yes"
},
{
"Version": "13",
"State": "yes",
"EvidenceKind": "yaml-transition",
"TransitionVersion": "11",
"Supported": true,
"Original": "Yes"
},
{
"Version": "14",
"State": "yes",
"EvidenceKind": "yaml-transition",
"TransitionVersion": "11",
"Supported": true,
"Original": "Yes"
},
{
"Version": "15",
"State": "yes",
"EvidenceKind": "yaml-transition",
"TransitionVersion": "11",
"Supported": true,
"Original": "Yes"
},
{
"Version": "16",
"State": "yes",
"EvidenceKind": "yaml-transition",
"TransitionVersion": "11",
"Supported": true,
"Original": "Yes"
},
{
"Version": "17",
"State": "yes",
"EvidenceKind": "yaml-transition",
"TransitionVersion": "11",
"Supported": true,
"Original": "Yes"
},
{
"Version": "18",
"State": "yes",
"EvidenceKind": "yaml-transition",
"TransitionVersion": "11",
"Supported": true,
"Original": "Yes"
},
{
"Version": "8.1",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "8.2",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "8.3",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "8.4",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "9.0",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "9.1",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "9.2",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "9.3",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "9.4",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "9.5",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
},
{
"Version": "9.6",
"State": "no",
"EvidenceKind": "yaml-default-no",
"TransitionVersion": "",
"Supported": false,
"Original": "No"
}
],
"Texts": [
{
"Locale": "en",
"Title": "Partition pruning during query execution",
"BodyHTML": "\u003cp\u003eQueries on partitioned tables can eliminate partitions during query execution time, instead of only at query planning time. This allows PostgreSQL to use information that becomes available during query execution to further prune the number of partitions it needs to use, leading to improved query performance.\u003c/p\u003e\n",
"SourceHash": "1dd22bf9a7f3ec325b894e2836fda535a25529f246a94dd41d6abbfe9997f7fd",
"ContentHash": "cae3cb31d80d11ba92ee33f9fe43939c165ae431e34cc5109dabd57a88de0bf5",
"Payload": {
"description": "Queries on partitioned tables can eliminate partitions during query execution time, instead of only at query planning time. This allows PostgreSQL to use information that becomes available during query execution to further prune the number of partitions it needs to use, leading to improved query performance.",
"name": "Partition pruning during query execution",
"versions": {
"11": "Yes"
}
}
},
{
"Locale": "zh-Hans",
"Title": "查询执行期间的分区剪枝",
"BodyHTML": "\u003cp\u003e对分区表的查询可以在查询执行期间消除分区，而不仅仅是在查询计划时。这使 PostgreSQL 能够利用查询执行期间可用的信息进一步减少需要使用的分区数量，从而提高查询性能。\u003c/p\u003e\n",
"SourceHash": "071091951021357a5f492adb04caed6febf4d315ac2626ca027a48dd8ec01d50",
"ContentHash": "713e4296417e552254d450168e653c30e23fda3abfb17ae0f80b9cfad0958df4",
"Payload": {
"description": "对分区表的查询可以在查询执行期间消除分区，而不仅仅是在查询计划时。这使 PostgreSQL 能够利用查询执行期间可用的信息进一步减少需要使用的分区数量，从而提高查询性能。",
"name": "查询执行期间的分区剪枝"
}
}
],
"GroupTitles": {
"en": "Partitioning \u0026 Inheritance",
"zh-Hans": "分区和继承"
},
"LegacyIDs": [
"332"
]
}