What's New in v19.2.0-beta.20191014

This version of CockroachDB is no longer supported. For more details, see the Release Support Policy.

October 14, 2019


A denial-of-service (DoS) vulnerability is present in CockroachDB v19.2.0 - v19.2.11 due to a bug in protobuf. This is resolved in CockroachDB v19.2.12 and later releases. When upgrading is not an option, users should audit their network configuration to verify that the CockroachDB HTTP port is not available to untrusted clients. We recommend blocking the HTTP port behind a firewall.

For more information, including other affected versions, see Technical Advisory 58932.

Get future release notes emailed to you:


Docker image

$ docker pull cockroachdb/cockroach-unstable:v19.2.0-beta.20191014

SQL language changes

  • The new SHOW RANGE ... FOR ROW statement identifies the range containing a specific row of a table or secondary index. This is particularly useful for validating the location of a specific piece of data when using partitions to control data location for improved performance or GDPR compliance. Note that this new statement is experimental and its interface and output are subject to change. #40954
  • The SHOW PARTITIONS statement now displays inherited as well as explicitly set zone configurations for partitions. Also, it is now possible to retrieve full zone configurations via the full_config_sql column in the crdb_internal.zones table, and the new zone_id and subzone_id columns in the crdb_internal.partitions table point to partitions' corresponding zone configurations in crdb_internal.zones. #40493

Command-line changes

  • When vmodule is set to exec_logs=2 to log queries executed by a node, CockroachDB-generated statements are no longer logged alongside client-generated statements. To log CockroachDB-generated statements as well, you must now use exec_logs=3. #41149

Bug fixes

  • Fixed a bug that would cause queries combining SQL mutation statements in sub-queries inside UNION to return invalid results or to modify the wrong rows if the transaction is forced to retry. #41307
  • Fixed a bug that prevented changes to the kv.bulk_io_write.concurrent_addsstable_requests cluster setting from taking effect. #41195
  • Fixed a memory leak that affected secondary logging (SQL audit logs, statement execution, and RocksDB logging). #41231
  • Fixed a bug where zone configuration changes on tables with existing index zone configurations would not take effect unless the num_replicas field was also set. #41261
  • Fixed a bug where zone configuration changes on secondary indexes wouldn't perform setting verification, such as constraints with lease preferences or setting only one of min_range_size and max_range size. #41216
  • Fixed a rare data corruption bug in RocksDB caused by newer Linux kernels' handling of i_generation on certain filesystems. #41346

Performance improvements

  • Stabilized performance of IMPORT and RESTORE by changing the default value of the rocksdb.ingest_backpressure.pending_compaction_threshold cluster setting from 64 GiB to 2 GiB. #41263

Doc updates


This release includes 57 merged PRs by 23 authors.

YesYes NoNo