Software update: CockroachDB 2.0.2

Spread the love

The team behind CockroachDB has released version 2.0.2. This is an open source database that is ideal for cloud environments and offers various options for dealing with problems, thanks to the scattered design. For more information we refer to this page where the most frequently asked questions are answered. The list of changes is as follows:

What’s New in v2.0.2
General Changes

  • The header of new log files generated by cockroach start will now include the cluster ID once it has been determined. # 24982
  • The cluster ID is now reported with tag [config] in the first log file, not only when log files are rotated. # 24982
  • Stopped spamming the server logs with “error closing gzip response writer” messages. # 25108

SQL Language Changes

  • Added more ways to specify an index name for statements that require one (e.g., DROP INDEX, ALTER INDEX … RENAME, etc.), improving PostgreSQL compatibility. # 24817
  • Clarified the error message produced upon accessing a virtual schema with no database prefix (e.g. when database is not set). # 24809
  • STORED is no longer a reserved keyword and can be used as an unrestricted name for databases, tables and columns. # 24864
  • Errors detected by SHOW SYNTAX are now tracked internally like other SQL errors. # 24900
  • IMPORT now supports hex-encoded byte literals for BYTES columns. # 25063
  • Collated strings can now be used in WHERE clauses on indexed columns. # 25175
  • The Level and Type columns or EXPLAIN (VERBOSE) results are now hidden; if they are needed, they can be SELECTed explicitly. # 25206

Admin UI Changes

  • Added RocksDB compactions / flushes to storage graphs. # 25457

Bug Fixes

  • It is once again available in selected stars (e.g., SELECT mydb.kv. * FROM kv) for compatibility with CockroachDB v1.x. # 24842
  • Fixed a scenario in which could deadlock while starting up. # 24831
  • Ranges in partitioned tables are now properly split to respect their configured maximum size. # 24912
  • Some child or schedule change errors that were stuck in a permanent loop now correctly fail. # 25015
  • When adding a column, CockroachDB now verifications that the column is referenced by no more than one foreign key. Existing tables with a column that is used by multiple foreign key constraints should be changed at least one foreign key per column. # 25079
  • CockroachDB now properly reports an error when using the internal-only functions final_variance () and final_stddev () instead of causing a crash. # 25218
  • The constraint_schema column in information_schema.constraint_column_usage now displays the constraint’s schema instead of its catalog. # 25220
  • Fix a panic caused by some queries containing OFFSET and ORDER BY. # 25238
  • START; RELEASE SAVEPOINT now returns an error instead of causing a crash. # 25251
  • Fixed a rare segfault returned from C ++. # 25361
  • Fixed a bug with IS DISTINCT NOT returning NULL values ​​that pass the condition in some cases. # 25339
  • Restarting a CockroachDB server on Windows no longer fails due to file system locks in the store directory. # 25439
  • Prevented the consistency checker from deadlocking. This would have been the case as a steady number of replicas for consistency checking on one or more nodes. # 25474
  • Fixed problems with IMPORT sometimes failing after node decommissioning. # 25307
  • Fixed a bug causing PREPARE to hang when the CREATE TABLE statement. # 24874

Build Changes

  • Build metadata, like the commit SHA and build time, is properly injected into the binary when using Go 1.10 and building from a symlink. # 25062

Doc Updates

  • Improved the documentation of the now (), current_time (), current_date (), current_timestamp (), clock_timestamp (), statement_timestamp (), cluster_logical_timestamp (), and age () built-in functions. # 25383 # 25145

Facebook Notice for EU! You need to login to view and post FB Comments!
You might also like