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
roachtest: sqlsmith/setup=rand-tables/setting=default failed #109974
Comments
Reduced: CREATE TABLE t1 (
g1 GEOGRAPHY
);
CREATE TABLE t2 (
k2 INT PRIMARY KEY,
g2 GEOGRAPHY,
INVERTED INDEX (k2, g2) NOT VISIBLE
);
EXPLAIN
DELETE FROM t2 USING t1 WHERE st_intersects(t2.g2, t1.g1); Full stacktrace:
Looks like a bug with index recommendations. |
Looks like this was introduced in #108576, so it's not yet been released. |
Nevermind, this PR was backported. I'll figure out which releases this affects. |
This was not backported to v23.1.9-rc branch, so we're safe there. It was backported before the v23.1.10-rc branch was cut, so we'll need to backport the fix to that branch. We'll also want to backport the fix to v22.2. |
110116: indexrec: fix internal error with inverted indexes r=mgartner a=mgartner A bug was introduced in #108576 in code that compares index columns of an existing index and a hypothetical index. Prior to this commit, this logic only checked that the hypothetical index column was an inverted column (the last explicitly indexed column in an inverted index) before fetching the inverted source column ordinal for both the hypothetical and existing index column. When the existing index column was not an inverted column, and internal error would occur. This commit fixes the bug by checking that both the hypothetical and existing index columns are inverted columns before fetching the source column ordinals. There is no release note because this bug does not exist in any releases. Fixes #109974 Release note: None Co-authored-by: Marcus Gartner <marcus@cockroachlabs.com>
A bug was introduced in #108576 in code that compares index columns of an existing index and a hypothetical index. Prior to this commit, this logic only checked that the hypothetical index column was an inverted column (the last explicitly indexed column in an inverted index) before fetching the inverted source column ordinal for both the hypothetical and existing index column. When the existing index column was not an inverted column, and internal error would occur. This commit fixes the bug by checking that both the hypothetical and existing index columns are inverted columns before fetching the source column ordinals. There is no release note because this bug does not exist in any releases. Fixes #109974 Release note: None
A bug was introduced in #108576 in code that compares index columns of an existing index and a hypothetical index. Prior to this commit, this logic only checked that the hypothetical index column was an inverted column (the last explicitly indexed column in an inverted index) before fetching the inverted source column ordinal for both the hypothetical and existing index column. When the existing index column was not an inverted column, and internal error would occur. This commit fixes the bug by checking that both the hypothetical and existing index columns are inverted columns before fetching the source column ordinals. There is no release note because this bug does not exist in any releases. Fixes #109974 Release note: None
A bug was introduced in cockroachdb#108576 in code that compares index columns of an existing index and a hypothetical index. Prior to this commit, this logic only checked that the hypothetical index column was an inverted column (the last explicitly indexed column in an inverted index) before fetching the inverted source column ordinal for both the hypothetical and existing index column. When the existing index column was not an inverted column, and internal error would occur. This commit fixes the bug by checking that both the hypothetical and existing index columns are inverted columns before fetching the source column ordinals. There is no release note because this bug does not exist in any releases. Fixes cockroachdb#109974 Release note: None
I'm going to open this issue, to track that the backports to 22.2 and release-23.1.10-rc are still open/unmerged. |
they just merged -- closing issue then :) |
roachtest.sqlsmith/setup=rand-tables/setting=default failed with artifacts on release-23.1.10-rc @ 58ac87a9b24e1cfb446143dafe04808ea186637f:
Parameters:
ROACHTEST_arch=amd64
,ROACHTEST_cloud=gce
,ROACHTEST_cpu=4
,ROACHTEST_encrypted=false
,ROACHTEST_ssd=0
Help
See: roachtest README
See: How To Investigate (internal)
See: Grafana
This test on roachdash | Improve this report!
Jira issue: CRDB-31236
The text was updated successfully, but these errors were encountered: