Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Plan Cache Should Not Differentiate Precision for Decimal Fields in Execution Plans #58576

Open
shaoxiqian opened this issue Dec 27, 2024 · 0 comments
Labels
type/enhancement The issue or PR belongs to an enhancement.

Comments

@shaoxiqian
Copy link
Contributor

Enhancement

During the process of simulating customer workloads, it was discovered that for decimal fields, differences in precision—whether for the integer part or the fractional part—result in different execution plans, causing cache misses. Both float and double types have the same issue.Let's take decimal as an example."
mysql> show create table t; +-------+-----------------------------------------------------------------------------------------------------------------+ | Table | Create Table | +-------+-----------------------------------------------------------------------------------------------------------------+ | t | CREATE TABLE t(adecimal(10,2) DEFAULT NULL ) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 COLLATE=utf8mb4_bin | +-------+-----------------------------------------------------------------------------------------------------------------+ 1 row in set (0.00 sec)

example1
Image

example2
Image

@shaoxiqian shaoxiqian added the type/enhancement The issue or PR belongs to an enhancement. label Dec 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

No branches or pull requests

1 participant