-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
sql: non-nullable column with no value #74727
Comments
There's been a few different bugs that can cause this, so I'll reduce it down and determine which. Then I'll try to backport some changes to randgen that prevent creating schemas that can trigger this bug so we don't get repeated reports like this. |
It's the result of a |
See #75161. Closing this issue. |
74737: spanconfigsqltranslator: introduce a pts table reader r=adityamaru a=adityamaru This change introduces a `ProtectedTimestampTableReader` that provides a txn scoped, in-memory view of the system table that stores protected timestamp records. The `SQLTranslator` will use this table reader to generate SpanConfigs and SystemSpanConfigs in a follow up PR. Informs: #73727 Release note: None 75125: *: replace "testdata" with sed scripts r=rickystewart a=otan Not a proper audit, but 80% of the way there. Refs: #71928 See individual commits for details 75161: randgen: do not create computed columns with bad volatilities r=mgartner a=mgartner Some cast to STRING types has been given an incorrect volatility. For example, REGCLASS->STRING casts are immutable when they should be stable (see #74286 and #74553 for more details). Creating computed column expressions with such a cast can cause logical correctness bugs and internal errors. The volatilities cannot be fixed without causing backward incompatibility. This commit prevents `randgen` from creating computed columns with these casts so that sqlsmith and TLP do not repetitively find these known volatility bugs. Informs #74727 Release note: None 75165: kv: fix GenerateForcedRetryableError to return a bumped epoch r=lidorcarmel a=lidorcarmel This is needed for PR #74563, where we change how txn is reset. Without this change GenerateForcedRetryableError returns an error with an inner txn that has an epoch 0. With this change the epoch is copied from the original txn. Release note: None Co-authored-by: Aditya Maru <adityamaru@gmail.com> Co-authored-by: Oliver Tan <otan@cockroachlabs.com> Co-authored-by: Marcus Gartner <marcus@cockroachlabs.com> Co-authored-by: Lidor Carmel <lidor@cockroachlabs.com>
roachtest.sqlsmith/setup=rand-tables/setting=no-ddl failed with artifacts on release-21.2 @ b4a27f3634e3e41dc3966214cf05ff6870c055c5:
Reproduce
See: roachtest README
Same failure on other branches
This test on roachdash | Improve this report!
The text was updated successfully, but these errors were encountered: