-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
opt: internal error: estimated row count must be non-zero #85499
Comments
Hello, I am Blathers. I am here to help you get the issue triaged. Hoot - a bug! Though bugs are the bane of my existence, rest assured the wretched thing will get the best of care here. I have CC'd a few people who may be able to assist you:
If we have not gotten back to your issue within a few business days, you can try the following:
🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is otan. |
Thanks for the report! I confirmed that the bug is present on 22.1.5 and 21.2.14, but not on 21.1.19. Moving to backlog, but cc @rytaft since you've fixed a handful issues like this. |
88494: opt: fix error due to estimated row count must be non-zero r=rytaft a=rytaft This commit fixes an error in the statistics code that was caused by integer overflow when calculating the distinct count. Fixes #85499 Release note (bug fix): Fixed a rare internal error that could occur during planning when a predicate included values close to the maximum or minimum int64 value. The error, "estimated row count must be non-zero", has now been fixed. Co-authored-by: Rebecca Taft <becca@cockroachlabs.com>
This commit fixes an error in the statistics code that was caused by integer overflow when calculating the distinct count. Fixes #85499 Release note (bug fix): Fixed a rare internal error that could occur during planning when a predicate included values close to the maximum or minimum int64 value. The error, "estimated row count must be non-zero", has now been fixed.
This commit fixes an error in the statistics code that was caused by integer overflow when calculating the distinct count. Fixes cockroachdb#85499 Release note (bug fix): Fixed a rare internal error that could occur during planning when a predicate included values close to the maximum or minimum int64 value. The error, "estimated row count must be non-zero", has now been fixed.
This commit fixes an error in the statistics code that was caused by integer overflow when calculating the distinct count. Fixes cockroachdb#85499 Release note (bug fix): Fixed a rare internal error that could occur during planning when a predicate included values close to the maximum or minimum int64 value. The error, "estimated row count must be non-zero", has now been fixed.
This commit fixes an error in the statistics code that was caused by integer overflow when calculating the distinct count. Fixes cockroachdb#85499 Release note (bug fix): Fixed a rare internal error that could occur during planning when a predicate included values close to the maximum or minimum int64 value. The error, "estimated row count must be non-zero", has now been fixed.
Describe the problem
Unexpected internal error.
To Reproduce
Expected behavior
No error.
Additional data / screenshots
Environment:
cockroach sql
]Additional context
Jira issue: CRDB-18271
The text was updated successfully, but these errors were encountered: