Why Database Partition Pruning Fails Without Partition Elimination
from Database Tech with Fexingo: SQL, NoSQL, and Data Storage Conversations Hosted by Fexingo
Partition pruning is supposed to speed up queries by skipping irrelevant partitions, but it breaks silently when queries don't match the partition function exactly. Lucas and Luna dig into a real case from a logistics company: a 32-terabyte PostgreSQL time-partitioned table where a date-casting mismatch forced full-table scans on every query. They explain how partition elimination happens under the hood, why timestamp vs timestamptz type mismatches kill it, and what a proper partition-aware query plan looks like vs a sequential scan. They also cover how to detect missing partition pruning with EXPLAIN ANALYZE and pg_stats, and why the same problem appears in MySQL, BigQuery, and Snowflake. If you think partition pruning is automatic, this episode will save you a lot of wait time at 2 AM. #PartitionPruning #PartitionElimination #PostgreSQL #DatabasePerformance #QueryOptimization #DataPartitioning #TimeSeriesData #EXPLAINANALYZE #SequentialScan #DatabaseIndexing #BigQuery #Snowflake #MySQL #TypeCasting #QueryPlans #Technology #FexingoBusiness #BusinessPodcast Keep every episode free: buymeacoffee.com/fexingo
Embed this episode
No transcript yet.