Search results

CockroachDB v21.1 is a required Regular Release.

RESTORE will re-validate indexes when incremental backups are created from an older version (v20.2.2 and earlier or v20.1.4 and earlier), but restored by a newer version (v21.1.0+). These earlier releases may have included incomplete data for indexes that were in the process of being created.

RESTORE will re-validate indexes when incremental backups are created from an older version (v20.2.2 and earlier or v20.1.4 and earlier), but restored by a newer version (v21.1.0+). These earlier releases may have included incomplete data for indexes that were in the process of being created.

New CockroachCloud clusters will now run CockroachDB v21.1.9.

During an upgrade of a CockroachDB cluster from v21.1.x → v21.2.0, backups will fail until the upgrade is finalized. After the upgrade is complete and finalized, backups will continue as normal.

Previously, in v21.1.x and earlier, CockroachDB could incorrectly read the data of a unique secondary index that used to be a primary index created via ALTER PRIMARY KEY. This has been fixed. #71589

Fixed a bug present since v21.1 that allowed values to be inserted into an ARRAY-type column that did not conform to the inner-type of the array. For example, it was possible to insert ARRAY['foo'] into a column of type CHAR(1)[]. This could cause incorrect results when querying the table. The INSERT now errors, which is expected. #102811

Fixed a bug where some secondary indexes would incorrectly be treated internally as primary indexes, which could cause some schema change operations to fail. The bug could occur if ALTER PRIMARY KEY was used on v21.1 or earlier, and the cluster was upgraded. #106428

Fixed a bug where some secondary indexes would incorrectly be treated internally as primary indexes, which could cause some schema change operations to fail. The bug could occur if ALTER TABLE ... ALTER PRIMARY KEY was used on CockroachDB v21.1 or earlier, and the cluster was upgraded. #106426

Fixed a bug that could cause new connections to fail with the following error after upgrading: ERROR: invalid value for parameter "vectorize": "unknown(1)" SQLSTATE: 22023 HINT: Available values: off,on,experimental_always. To encounter this bug, the cluster must have: Run on version v21.1 at some point in the past. Run SET CLUSTER SETTING sql.defaults.vectorize = 'on'; while running v21.1. Not set sql.defaults.vectorize after upgrading past v21.1 4. Subsequently upgraded to v24.2. To detect this bug, run the following query: If the command returns 1 instead of on, run the following statement before upgrading. 1 is now allowed as a value for this setting, and is equivalent to on. [#133371]#133371#133368