Why Database Partition Pruning Fails Without Careful Design

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

Why Database Partition Pruning Fails Without Careful Design

Listen for free

View show details

Episode 44 of Database Tech with Fexingo: Lucas and Luna dig into a subtle performance killer in partitioned databases — partition pruning that silently doesn't prune. They walk through how a real-world e-commerce system ran full-table scans on 200 partitions because the WHERE clause used a function-wrapped partition key. They explain how databases like PostgreSQL and MySQL handle partition elimination, why DATE() on a timestamp column defeats it, and the one index trick that can backfire. Listeners learn how to audit their own queries for accidental full scans, and why a seemingly clean schema can hide a 100x performance gap. This episode is for engineers who think their partitioned tables are fast — but haven't checked the query plan lately. #DatabasePartitioning #PartitionPruning #SQLPerformance #QueryOptimization #PostgreSQL #MySQL #DatabaseDesign #TechPodcast #DatabaseTechWithFexingo #DataEngineering #PerformanceTuning #Indexing #DatabaseInternals #FexingoBusiness #BusinessPodcast #Technology #SoftwareEngineering #BackendDev Keep every episode free: buymeacoffee.com/fexingo

No reviews yet