-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
internal/sqlsmith: TestRandTableInserts failed #112011
Comments
internal/sqlsmith.TestRandTableInserts failed with artifacts on master @ 76a8d1077d3d29bcf020a48972efd1f77aa892c2:
Parameters: |
internal/sqlsmith.TestRandTableInserts failed with artifacts on master @ 76a8d1077d3d29bcf020a48972efd1f77aa892c2:
Parameters: |
internal/sqlsmith.TestRandTableInserts failed with artifacts on master @ 330500d0433bae42bc7c0d6842a427aab3b27f03:
Parameters: |
internal/sqlsmith.TestRandTableInserts failed with artifacts on master @ 330500d0433bae42bc7c0d6842a427aab3b27f03:
Parameters: |
This looks similar to #112010, but I'm not sure if it's an exact duplicate because the error message is slightly different. Assigning to @DrewKimball for now. |
Most comparisons are disallowed for the REFCURSOR data type. For example, the following is not allowed in postgres: ``` SELECT 'foo'::REFCURSOR = 'bar'::REFCURSOR; ``` However, postgres does allow using `IS [NOT] DISTINCT FROM NULL` and `IS [NOT] NULL` with a refcursor-typed expression os the left operand. There are a few places where CRDB internally expects this comparison to be valid as well, so disallowing these comparisons has caused test failures. This patch removes the refcursor-specific check for invalid comparisons during type checking, and relies on execution-time checks as is done for other comparisons. This means that `IsNull` and `IsNotNull` expressions can now be executed. In addition, the `IS DISTINCT FROM NULL` comparison is now supported only for the case of type `REFCURSOR` as the left operand, and `UNKNOWN` (NULL) as the right operand. Fixes cockroachdb#112010 Fixes cockroachdb#112011 Release note: None
Most comparisons are disallowed for the REFCURSOR data type. For example, the following is not allowed in postgres: ``` SELECT 'foo'::REFCURSOR = 'bar'::REFCURSOR; ``` However, postgres does allow using `IS [NOT] DISTINCT FROM NULL` and `IS [NOT] NULL` with a refcursor-typed expression os the left operand. There are a few places where CRDB internally expects this comparison to be valid as well, so disallowing these comparisons has caused test failures. This patch removes the refcursor-specific check for invalid comparisons during type checking, and relies on execution-time checks as is done for other comparisons. This means that `IsNull` and `IsNotNull` expressions can now be executed. In addition, the `IS DISTINCT FROM NULL` comparison is now supported only for the case of type `REFCURSOR` as the left operand, and `UNKNOWN` (NULL) as the right operand. Fixes cockroachdb#112010 Fixes cockroachdb#112011 Release note: None
110901: ui: decouple SQL execution requests on databases page r=zachlite a=zachlite Previously, SQL execution requests for database details and span stats were done in the same HTTP request. The consequence of this coupling was that no information could be displayed until span stats were collected. Since span stats are much slower to collect than database details, this resulted in the potential for a very bad user experience. This commit separates span stats and database details into distinct HTTP requests, and updates the DatabasesPage component so that database details and span stats (and their associated network and query errors) can all be displayed independently. Here is a screenshot of a simulated span stats error, and a simulated index recommendations error. Notice how the columns `Tables` and `Regions/Nodes` can still be displayed. ![Screenshot 2023-09-15 at 9 49 19 AM](https://github.com/cockroachdb/cockroach/assets/5423191/0a6c353b-43b0-471a-8024-72ce10fe5a1f) Epic: none Release note (ui change): Added progressive loading functionality to the databases page. 112070: sql: allow refcursor comparison with NULL values r=DrewKimball a=DrewKimball Most comparisons are disallowed for the REFCURSOR data type. For example, the following is not allowed in postgres: ``` SELECT 'foo'::REFCURSOR = 'bar'::REFCURSOR; ``` However, postgres does allow using `IS [NOT] DISTINCT FROM NULL` and `IS [NOT] NULL` with a refcursor-typed expression os the left operand. There are a few places where CRDB internally expects this comparison to be valid as well, so disallowing these comparisons has caused test failures. This patch removes the refcursor-specific check for invalid comparisons during type checking, and relies on execution-time checks as is done for other comparisons. This means that `IsNull` and `IsNotNull` expressions can now be executed. In addition, the `IS DISTINCT FROM NULL` comparison is now supported only for the case of type `REFCURSOR` as the left operand, and `UNKNOWN` (NULL) as the right operand. Fixes #112010 Fixes #112011 Release note: None Co-authored-by: Zach Lite <[email protected]> Co-authored-by: Drew Kimball <[email protected]>
internal/sqlsmith.TestRandTableInserts failed with artifacts on master @ 76a8d1077d3d29bcf020a48972efd1f77aa892c2:
Parameters:
TAGS=bazel,gss
,stress=true
Help
See also: How To Investigate a Go Test Failure (internal)
This test on roachdash | Improve this report!
Jira issue: CRDB-32188
The text was updated successfully, but these errors were encountered: