Sampling-Based Query Re-Optimization
Not on the map. Why?
Abstract (arXiv)
Despite of decades of work, query optimizers still make mistakes on "difficult" queries because of bad cardinality estimates, often due to the interaction of multiple predicates and correlations in the data. In this paper, we propose a low-cost post-processing step that can take a plan produced by the optimizer, detect when it is likely to have made such a mistake, and take steps to fix it. Specifically, our solution is a sampling-based iterative procedure that requires almost no changes to the original query optimizer or query evaluation mechanism of the system. We show that this indeed imposes low overhead and catches cases where three widely used optimizers (PostgreSQL and two commercial systems) make large errors.
Key facts. Cited by 4 papers in the map (data through 7 Oct 2026). First posted on arXiv 21 Jan 2016.
Builds on
No reference list yet.
Built on by
Citing papers per year: 2021: 1; 2022: 0; 2023: 1; 2024: 1; 2025: 1.
4 papers.
- 2021A Survey on Advancing the DBMS Query Optimizer: Cardinality Estimation, Cost Model, and Plan Enumerationcited by 14
- 2023Kepler: Robust Learning for Faster Parametric Query Optimizationcited by 3
- 2024Budget-aware Query Tuning: An AutoML Perspectivecited by 1
- 2025Access Paths for Efficient Ordering with Large Language Modelscited by 1
- 2025Access Paths for Efficient Ordering with Large Language Models30 Aug 2025
- 2024Budget-aware Query Tuning: An AutoML Perspective29 Mar 2024
- 2023Kepler: Robust Learning for Faster Parametric Query Optimization11 Jun 2023
- 2021A Survey on Advancing the DBMS Query Optimizer: Cardinality Estimation, Cost Model, and Plan Enumeration5 Jan 2021