Search results

Get future release notes emailed to you:

CockroachDB has a new role VIEWACTIVITYREDACTED introduced in v21.2.5 that is similar to VIEWACTIVITY but restricts the use of statement diagnostics bundles. It is possible for a user to have both roles (VIEWACTIVITY and VIEWACTIVITYREDACTED), but VIEWACTIVITYREDACTED takes precedence. #74715

New CockroachDB Dedicated clusters will now run v21.2.3.

Fixed a bug that caused internal errors when using user-defined types in views that have subqueries. This bug was present when using views since v21.2. #106956

Fixed a bug that caused internal errors in queries with set operations, like UNION, when corresponding columns on either side of the set operation were not the same. This error only occurred with a limited set of types. This bug is present in v20.2.6+, v21.1.0+, and v21.2.0+. #75294

Table statistics collection in CockroachDB could previously run into no bytes in account to release errors in some edge cases (when the SQL memory budget, configured via --max-sql-memory flag, was close to being exhausted). The bug has been present since v21.2 and is now fixed. #136165

Fixed a bug that caused internal errors when using user-defined types in views and user-defined functions that have subqueries. This bug was present when using views since version v21.2. It was present when using user-defined functions since v23.1. #106955

Table statistics collection in CockroachDB could previously run into no bytes in account to release errors in some edge cases (when the SQL memory budget, configured via --max-sql-memory flag, was close to being exhausted). The bug had been present since v21.2 and is now fixed. #136164

Table statistics collection in CockroachDB could previously run into no bytes in account to release errors in some edge cases (when the SQL memory budget, configured via --max-sql-memory flag, was close to being exhausted). The bug has been present since v21.2 and is now fixed. #136166

Table statistics collection in CockroachDB could previously run into no bytes in account to release errors in some edge cases (when the SQL memory budget, configured via --max-sql-memory flag, was close to being exhausted). The bug has been present since v21.2 and is now fixed. #135970