SQL language changes
- -- The `extract()` [built-in function](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) now supports millennium, century, decade, isoyear, isodow, and julian for `DATE`, `TIMESTAMP`, and `TIMESTAMPTZ`. The `date_trunct()` function now supports millennium, century, and decade for `DATE`, `TIMESTAMP`, and `TIMESTAMPTZ`. [#41784][#41784] {% comment %}doc{% endcomment %} -- `extract()` now supports a string constant as element argument. [#41429][#41429] -- Added support for the `JOIN LATERAL` syntax. [#40945][#40945] {% comment %}doc{% endcomment %} -- Added support for `WITH RECURSIVE` with `UNION ALL`. [#41368][#41368] {% comment %}doc{% endcomment %} -- Added support for `bit_and()` and `bit_or()` aggregate functions. [#41334][#41334] {% comment %}doc{% endcomment %} -- `NULL` values are now allowed to be among tuples when being compared against a tuple. [#40298][#40298] -- Added syntax-only support for `ORDER BY ... NULLS FIRST | LAST`. [#41544][#41544] {% comment %}doc{% endcomment %} -- Comments can now be associated to indexes with `COMMENT ON INDEX` and can be checked with `SHOW INDEXES FROM ... WITH COMMENT`. [#41555][#41555] {% comment %}doc{% endcomment %} -- `SELECT` and `HAVING` can now refer to ungrouped columns when the grouped columns contain the primary key of the table containing the ungrouped columns. [#41732][#41732] {% comment %}doc{% endcomment %} -- Dropping a unique index that was created via `CREATE UNIQUE INDEX` statement no longer requires the `CASCADE` option. [#42001][#42001] {% comment %}doc{% endcomment %} -- Added the `pg_prepared_statements` table. [#42018][#42018] - -Command-line changes
- -- The new `--storage-engine` flag for [`cockroach start`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start), and equivalent `COCKROACH_STORAGE_ENGINE` environment variable, specify the type of storage engine a node should use. Options are `rocksdb` (default) and `pebble`. [#41453][#41453] {% comment %}doc{% endcomment %} -- Enhanced the error message produced by [`cockroach init`](https://www.cockroachlabs.com/docs/v20.1/cockroach-init) when it encounters an already-initialized cluster to recommend adding `--join` to the `cockroach start` commands. [#42318][#42318] - -Bug fixes
- -- The Admin UI no longer mixes unit sizes in timeseries graph tooltips. [#40970][#40970] -- The `pg_collation_for()` function now correctly quotes its output. [#41545][#41545] -- Fixed an internal error when subqueries are used in arguments to commands like `SET`. [#41581][#41581] -- CockroachDB now properly emits the cluster ID, once known, to all secondary log files (SQL audit logging, statement execution logging, and RocksDB events) and properly removes excess secondary log files. [#40993][#40993] -- Other callers to `acquireNodeLease` will not get erroneously cancelled just because the context of the first caller was cancelled. [#41785][#41785] -- Vectorized execution no longer errors when adding an ordinality column to an expression with a limit. For example, `SELECT * FROM (SELECT * FROM foo LIMIT 1) WITH ORDINALITY` no longer throws an index out of range error. [#41782][#41782] -- Fixed a bug causing rare crashes when using built-in functions. [#41970][#41970] -- The `date_trunc()` function now correctly considers timezones for `TIMESTAMPTZ` and `DATE` types. [#42006][#42006] -- Fixed a bug causing `CREATE TABLE AS` statements to fail with the message "unexpected concurrency for a flow that was forced to be planned locally". [#42013][#42013] -- Fixed a bug where `SHOW ZONE CONFIGURATION` and `crdb_internal.zones` would show results for resources the user does not have permission to view. [#42066][#42066], [#42080][#42080] -- Fixed a bug during planning for some queries that could cause an infinite loop and prevent the query from being cancelled. [#42082][#42082] -- Fixed a bug that caused jobs for dropping tables to report an inaccurate status. [#42121][#42121] -- Fixed a bug where rapid network disconnections could lead to cluster unavailability. [#41533][#41533] -- Fixed a stack overflow that could occur with certain patterns of queries. [#41984][#41984] -- Fixed some casts from `OID` to `TEXT`. [#41928][#41928] -- Fixed a bug where some cluster setting changes were not reflected during currently running `IMPORT`s. [#42268][#42268] -- Fixed bugs where: `Performance improvements
- -- Improved performance for some join queries due to improved filter inference during query planning. [#41250][#41250] -- Improved statistics estimation during query planning for columns with many `NULL` values. [#41520][#41520] -- The `cockroach debug check-store` command is now faster. [#41805][#41805] -- Improved the low-level performance of short range reverse scans. [#42092][#42092] -- Individual response messages in a response batch no longer each contain information about transaction state changes. [#42139][#42139] -- `BACKUP` work is now more evenly spread across clusters that have non-uniform leaseholder distributions. [#42274][#42274] - -Contributors
- -This release includes 376 merged PRs by 48 authors. We would like to thank the following contributors from the CockroachDB community: - -- Aayush Shah (first-time contributor) -- Andrea Sosso (first-time contributor) -- Arber Avdullahu (first-time contributor) -- Elliot Courant -- George Papadrosou -- Roga Pria Sembada (first-time contributor) -- Salvatore Tomaselli (first-time contributor) -- lzhfromustc (first-time contributor) -- sumeerbhola (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -In addition to security updates and various enhancements and bug fixes, this v20.1 alpha release includes some major highlights: - -- **Cluster backup:** You can now use CockroachDB's [Enterprise `BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) feature to back up an entire cluster's data, including configuration and system information such as user privileges, zone configurations, and cluster settings. At this time, you can restore individual databases and tables from a cluster backup. In a future release, you'll be able to restore an entire cluster as well. -- **Fresher follower reads:** [Follower reads](https://www.cockroachlabs.com/docs/v20.1/follower-reads) are now available for reads at least 4.8 seconds in the past, a much shorter window than the previous 48 seconds. -- **Import from Avro format**: You can now use the [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import) and [`IMPORT INTO`](https://www.cockroachlabs.com/docs/v20.1/import-into) statements to bulk import SQL data from Avro files. This makes it easier to migrate from systems like Spanner that export data in the Avro format. -- **Vectorized execution for `TIMESTAMPTZ`**: [Vectorized execution](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) now supports the `TIMESTAMPTZ` data type in addition to several other previously [supported data types](https://www.cockroachlabs.com/docs/v20.1/data-types). -- **CockroachDB backend for Django**: Developers using the Django framework can now leverage the `django-cockroachdb` adapter to [run their Python apps on CockroachDB](https://www.cockroachlabs.com/docs/v20.1/build-a-python-app-with-cockroachdb-django). - -Security updates
- -- The authentication code for new SQL connections has been simplified to always use the HBA configuration defined per `server.host_based_authentication.configuration`. The format of this file generally follows that of [`pg_hba.conf`](https://www.postgresql.org/docs/current/auth-pg-hba-conf.html). This behavior remains equivalent to previous CockroachDB versions, and this change is only discussed here for clarity: - - Upon each configuration change, CockroachDB automatically inserts the entry `host all root all cert` as a first rule, to ensure the root user can always log in with a valid client certificate. - - If the configuration is set to empty or found to be invalid in the cluster setting, the following default configuration is automatically used: - - ~~~ - host all root all cert - host all all all cert-password - ~~~ - - At any moment the current configuration on each node can be inspected using the `/debug/hba_conf` URL on the HTTP endpoint. The list of valid [authentication](https://www.cockroachlabs.com/docs/v20.1/authentication) methods is currently: - - - `cert`, for certificate-based authentication over an SSL connection - exclusively - - `cert-password`, which allows either cert-based or password-based - authentication over an SSL connection - - `password` for password-based authentication over an SSL connection - - `gss` for Kerberos-based authentication over an SSL connection, - enabled when running a CCL binary and an Enterprise license - - In effect, CockroachDB treats all the `host` rules as `hostssl` and behaves as per a default of `hostnossl all all all reject`. - - It is not currently possible to define authentication rules over non-SSL connections. As of this writing, non-SSL connections are only possible when running with `--insecure`, and on insecure nodes all the authentication logic is entirely disabled. [#43726][#43726] - -- CockroachDB now supports the [authentication](https://www.cockroachlabs.com/docs/v20.1/authentication) methods `'trust'` and `'reject'` in the [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) `server.host_based_authentication.configuration`. They are used to unconditionally allow and deny matching connection attempts. [#43731][#43731] -- Users [`GRANT`ing](https://www.cockroachlabs.com/docs/v20.1/grant) and [`REVOKE`ing](https://www.cockroachlabs.com/docs/v20.1/revoke) admin roles must be members of the admin role with `ADMIN OPTION`. This check was previously bypassed. [#41218][#41218] -- Fixed a bug in the parsing logic for `server.host_based_authentication.configuration`, where both single-character strings, and quoted strings containing spaces and separated by commas were not properly parsed. This would cause rules for usernames consisting of a single character or usernames containing spaces to apply improperly. [#43713][#43713] - -General changes
- -- Added system tables `system.protected_ts_meta` and `system.protected_ts_records` to support the implementation of [protected timestamps](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20191009_gc_protected_timestamps.md), a subsystem used to ensure that data required for long-running jobs is not garbage collected. [#42829][#42829] - -Enterprise edition changes
- -- Shortened the default interval for the `kv.closed_timestamp.target_duration` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) from `30s` to `3s`, which allows for follower reads at 4.8 seconds in the past rather than the previous 48 seconds. [#43147][#43147] -- CockroachDB now supports [importing](https://www.cockroachlabs.com/docs/v20.1/import) Avro data. [#43104][#43104] -- Importing data into CockroachDB from external HTTP servers is now more resilient to connection interruption. [#43374][#43374] [#43558][#43558] -- Added `BACKUP TOSQL language changes
- -- CockroachDB now provides a link to the relevant GitHub issue when clients attempt to use certain features that are not yet implemented. [#42847][#42847] -- [Vectorized queries](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) that execute only on supported types (even if those types form part of a table with unsupported types) are now run through the vectorized engine. This would previously fall back to the row-by-row execution engine. [#42616][#42616] -- CockroachDB now allows stored columns in [secondary indexes](https://www.cockroachlabs.com/docs/v20.1/indexes) to respect the [column family](https://www.cockroachlabs.com/docs/v20.1/column-families) table definitions that they are based on. [#42073][#42073] -- The error message reported when a client specifies a bulk I/O operation that uses an incompatible SQL function or operator now avoids the confusing and inaccurate term "backfill". This error is also now reported with code `22C01`. [#42941][#42941] -- The `CURRENT_TIME` [function](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) was added, which can be used with precision, e.g., `SELECT CURRENT_TIME, CURRENT_TIME(3)`. [#42928][#42928] -- `CREATE TABLE pg_temp.abc(a int)` now creates a temporary table. See [temp tables RFC](https://github.com/cockroachdb/cockroach/blob/master/docs/RFCS/20191009_temp_tables.md) (guide-level explanation) for more details about the search path semantics. [#41977][#41977] -- A new boolean column `'is_inverted'` has been added to `crdb_internal.table_indexes` virtual table which indicates whether the [index](https://www.cockroachlabs.com/docs/v20.1/indexes) is inverted or not. [#43102][#43102] -- The output of [`EXPLAIN`](https://www.cockroachlabs.com/docs/v20.1/explain) now shows [joins](https://www.cockroachlabs.com/docs/v20.1/joins) where there are no equality columns as "cross" instead of "hash". Cross joins can be very expensive and should be avoided. [#43061][#43061] -- The error code for [backups](https://www.cockroachlabs.com/docs/v20.1/backup), which would overwrite files, changed from class 58 (`"system"`) to class 42 (`"Syntax or Access Rule Violation"`). [#43221][#43221] -- CockroachDB now allows the usage of `TIMETZ` throughout the cluster. [#43023][#43023] -- Column types are now be displayed in the box for the input synchronizer in the flow diagram obtained via [`EXPLAIN (DISTSQL, TYPES)`](https://www.cockroachlabs.com/docs/v20.1/explain). [#43193][#43193] -- CockroachDB now supports [interval types](https://www.cockroachlabs.com/docs/v20.1/interval) with precision (e.g., `INTERVAL(5)`, `INTERVAL SECOND(5)`), and storing intervals with duration fields (e.g., `INTERVAL x TO y`). [#43130][#43130] -- When a session that has created temporary tables exits gracefully, the tables and temporary schema are now deleted automatically. [#42742][#42742] -- [Foreign key](https://www.cockroachlabs.com/docs/v20.1/foreign-key) checks that do not involve cascades are now performed after the mutation is complete, allowing self-referential foreign keys, or referential cycles. The execution plans for foreign key checks are now driven by the [optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer), which can make better planning decisions. In particular, if there is a suitable duplicated index, the one in the current locality will be used for foreign key checks. [#43263][#43263] -- Better estimates for the number of rows needed by [`SELECT`](https://www.cockroachlabs.com/docs/v20.1/select-clause) and [`DISTINCT`](https://www.cockroachlabs.com/docs/v20.1/select-clause#select-distinct-rows) operations may now result in faster queries when the results of these queries are limited (e.g., `SELECT DISTINCT * FROM t LIMIT 10`). [#42895][#42895] -- `MINUTE TO SECOND` is now parsed as `MM:SS` instead of `HH:MM`. Additionally, [interval syntax](https://www.cockroachlabs.com/docs/v20.1/interval), such as `INTERVAL "01:02.123"`, is now parsed correctly as `MM:SS.fff`. This matches Postgres behavior. [#43292][#43292] -- Previously, CockroachDB returned error code `42830` and `23503` for duplicate [foreign key](https://www.cockroachlabs.com/docs/v20.1/foreign-key) names. It now returns `42710`, which matches Postgres. [#43210][#43210] -- Clients can now retrieve system user information from the `pg_authid` virtual table, which is Postgres-compatible. [#43437][#43437] -- The [optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer) can now derive constant [computed columns](https://www.cockroachlabs.com/docs/v20.1/computed-columns) during [index](https://www.cockroachlabs.com/docs/v20.1/indexes) selection. This enables more efficient `HASH` indexes. [#43450][#43450] -- [Vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) now supports the [`TIMESTAMPTZ`](https://www.cockroachlabs.com/docs/v20.1/timestamp) data type. [#43514][#43514] -- CockroachDB now provides more descriptive error messages and an error hint when an unsupported rule is provided via `server.host_based_authentication.configuration`. [#43711][#43711] [#43710][#43710] -- Added an experimental prototype for altering the [primary key](https://www.cockroachlabs.com/docs/v20.1/primary-key) of a table. [#42462][#42462] - -Command-line changes
- -- Added a `nodelocal` command that can be used to upload file: `cockroach nodelocal upload location/of/file destination/of/file`. [#42966][#42966] -- The `table` format, used to display the results of CLI shell queries, has been updated. [#43728][#43728] -- Telemetry is now recorded for whenever the command [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) is used. [#43795][#43795] - -Admin UI changes
- -- Added page search and pagination to the [Statements page](https://www.cockroachlabs.com/docs/v20.1/admin-ui-statements-page). [#41641][#41641] -- A graph of changefeed restarts due to retryable errors is now included in the [Admin UI](https://www.cockroachlabs.com/docs/v20.1/admin-ui-debug-pages). [#43213][#43213] - -Bug fixes
- -- Fixed a bug that caused some jobs to be left indefinitely in a pending state and never run. [#42880][#42880] -- Fixed the row count estimate during query planning for some queries with multiple predicates where the selectivity of one predicate was calculated using a histogram. [#42916][#42916] -- CockroachDB now more reliably produces an error message when a client mistakenly uses a directory name instead of a file name with `nodelocal://` in bulk I/O operations. [#42542][#42542] -- Fixed a bug where an error would occur when trying to export data using a `nodelocal://` URL. CockroachDB now properly handles cases where the system's temporary directory lives on a different filesystem from the external I/O directory. [#42542][#42542] -- CockroachDB now avoids using `$TMPDIR` (often set `/tmp`) during bulk I/O operations. This prevents errors occurring when the `$TMPDIR` disk capacity is small compared to the configured external I/O directory. [#42542][#42542] -- Temporary files created during certain bulk I/O operations are now properly deleted when an error occurs. This prevents left-over temporary files being retained in the system and leaking disk usage over time. [#42542][#42542] -- Empty [arrays](https://www.cockroachlabs.com/docs/v20.1/array) are now correctly encoded and decoded over the binary protocol. [#42949][#42949] -- CockroachDB now ensures that databases being [restored](https://www.cockroachlabs.com/docs/v20.1/restore) are dropped if the `RESTORE` is canceled or fails. [#42946][#42946] -- Fixed a bug with some existing caching issues surrounding [role](https://www.cockroachlabs.com/docs/v20.1/authorization#create-and-manage-roles) memberships, where users could see out-of-date role membership information. [#42998][#42998] -- Fixed a bug where scanning an [index](https://www.cockroachlabs.com/docs/v20.1/indexes) of an unsupported type with the vectorized engine would lead to an internal error. [#42999][#42999] -- Fixed a bug where comparisons between [`DATE`](https://www.cockroachlabs.com/docs/v20.1/date) and [`TIMESTAMP`](https://www.cockroachlabs.com/docs/v20.1/timestamp) vs. [`TIMESTAMPTZ`](https://www.cockroachlabs.com/docs/v20.1/timestamp) broke because CockroachDB tried to normalize the `TIMESTAMPTZ` to UTC. CockroachDB now converts the `DATE` and `TIMESTAMP` to the `context` timezone and compares the `TIMESTAMPTZ` without altering its timezone. [#42927][#42927] -- Previously, CockroachDB did not handle `date` casts from `timestamp`/`timestamptz` with time attached to it for times before the unix epoch correctly. For example, `'1969-12-30 01:00:00'::timestamp` would round to `'1969-12-31'` instead of `'1969-12-30'`. This fix addresses that change. [#42952][#42952] -- Fixed a bug where `current_timestamp` did not correctly account for `SET TIME ZONE` in the background when storing results, and stored the timestamp as `UTC` instead. [#43012][#43012] -- The range rebalancing logic now considers stores with very close diversity scores equal (all other things being the same) and does not attempt to rebalance. [#43041][#43041] -- The range rebalancing logic now considers the new store being added when looking for target in case of rebalance. [#43041][#43041] -- Previously, gracefully terminating a node with `SIGINT` printed an error banner to the console. This was misleading, since the node responded to the signal correctly and terminated cleanly. This patch converts the error banner to a less-alarming informational message. [#42848][#42848] -- Fixed a bug that could lead to follower reads or [CDC](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) updates that did not reflect the full set of data at the timestamp. This bug was never observed in practice and should rarely cause issues, one of the necessary ingredients being an aggressive closed timestamp interval. [#42939][#42939] -- Fixed a bug where a well-timed write could slip in on the right-hand side of a [range merge](https://www.cockroachlabs.com/docs/v20.1/range-merges). This would allow it to improperly synchronize with reads on the post-merged range. [#43138][#43138] -- Previously, the [optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer) could panic in a specific situation where it would prune all the columns of multiple scans of the same CTE and then try to define different required physical properties for each scan. This seems to have been a possible bug since the addition of multi-use CTEs in v19.2, but is hard to trigger without the not-yet-released `LimitHint` physical property. This patch makes all CTE scans uniquely identifiable, even after column pruning. [#43161][#43161] -- Some incorrect issue links referenced to by error hints have been corrected. [#43232][#43232] -- CockroachDB no longer fails on an expression of the form `NOT(a && b)`. [#43242][#43242] -- Improved support for `OID` column types in tables. [#42973][#42973] -- [`EXPLAIN`](https://www.cockroachlabs.com/docs/v20.1/explain) can now be used with statements that use [`AS OF SYSTEM TIME`](https://www.cockroachlabs.com/docs/v20.1/as-of-system-time). [#43296][#43296] -- Fixed an internal error that could be returned when performing `MIN`/`MAX` aggregation over a [`STRING`](https://www.cockroachlabs.com/docs/v20.1/string) column that contains `NULL` values when executed via the vectorized engine. Only the previous v20.1 alpha releases were affected. [#43429][#43429] -- Fixed an internal error that could occur when `CASE` operator operating on distinct although compatible types was executed via the vectorized engine. For example, a query similar to `SELECT CASE WHEN false THEN 0:::INT2 ELSE 1:::INT8 END` previously would error out. [#43557][#43557] -- CockroachDB now ensures that a transaction running into multiple intents from an abandoned conflicting transaction cleans them up more efficiently. [#43563][#43563] -- CockroachDB now writes less metadata about aborted transactions to disk. [#42765][#42765] -- The concept of lax constant functional dependencies was [previously removed](https://github.com/cockroachdb/cockroach/pull/43532). There was a left-over case when a key is downgraded: if there was a strong empty key, the result is a lax empty key (which is no longer a concept). This change fixes this by removing the key altogether in this case. [#43722][#43722] -- It is now possible to perform [`ALTER COLUMN SET/DROP NULL`](https://www.cockroachlabs.com/docs/v20.1/alter-column) on multiple (different) columns of the same table inside a single transaction. [#43644][#43644] -- CockroachDB now properly rejects [`ALTER COLUMN DROP NOT NULL`](https://www.cockroachlabs.com/docs/v20.1/alter-column) on a column that is part of the primary key. [#43644][#43644] -- When the fourth column of a rule in the setting `server.host_based_authentication.configuration` is an IP address without a mask length (e.g., `1.2.3.4` instead of `1.2.0.0/16`), CockroachDB now properly interprets the fifth column as an IP netmask, as per https://www.postgresql.org/docs/current/auth-pg-hba-conf.html. [#43779][#43779] -- CockroachDB no longer tries to issue HTTP requests as part of an [import](https://www.cockroachlabs.com/docs/v20.1/import) once the import job has been canceled. [#43789][#43789] - -Performance improvements
- -- When resumed, paused [imports](https://www.cockroachlabs.com/docs/v20.1/import) now continue from their internally recorded progress instead of starting over. [#42476][#42476] [#43053][#43053] -- Adjusted the [optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer)'s cost of [lookup join](https://www.cockroachlabs.com/docs/v20.1/joins) when the lookup columns aren't a key in the table. This will cause some queries to switch to using a hash or merge join instead of a lookup join, improving performance in most cases. [#43003][#43003] -- Removed an unused field from Raft command `protobuf`, resulting in a 16% reduction in the overhead of each Raft proposal. [#43042][#43042] -- Range splits are now less disruptive to foreground reads. [#43048][#43048] -- CockroachDB now uses better execution plans when a `VALUES` clause is used as the right-hand side of `IN` or `ANY`. [#43154][#43154] -- The [optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer) can now infer additional filter conditions in some cases based on transitive equalities between columns. [#43194][#43194] -- Improved the estimated row count for some [lookup joins](https://www.cockroachlabs.com/docs/v20.1/joins) during planning, which can lead to a better plan. [#43325][#43325] -- The [optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer) now generates better execution plans in some cases where there is an `ORDER BY` expression that simplifies to a simple variable reference. [#43465][#43465] - -Build changes
- -- Go 1.13.5 is now required to build CockroachDB from source. [#43289][#43289] - -Doc Updates
- -- Added a [Django app development tutorial](https://www.cockroachlabs.com/docs/v20.1/build-a-python-app-with-cockroachdb-django). [#6359](https://github.com/cockroachdb/docs/pull/6359) [#6365](https://github.com/cockroachdb/docs/pull/6365) -- Updated the [Hibernate app development tutorial](https://www.cockroachlabs.com/docs/v20.1/build-a-java-app-with-cockroachdb-hibernate) with client-side retry logic. [#5760](https://github.com/cockroachdb/docs/pull/5760) -- Documented how to [use keyset pagination to iterate through query results](https://www.cockroachlabs.com/docs/v20.1/selection-queries#paginate-through-limited-results). [#6114](https://github.com/cockroachdb/docs/pull/6114) -- Improved the [GSSAPI authentication](https://www.cockroachlabs.com/docs/v20.1/gssapi_authentication) instructions for configuring Active Directory and MIT and for configuring the client. [#6115](https://github.com/cockroachdb/docs/pull/6115) -- Expanded the [Kubernetes tutorial](https://www.cockroachlabs.com/docs/v20.1/orchestrate-cockroachdb-with-kubernetes#step-2-start-cockroachdb) to show how to use a custom CA instead of Kubernetes built-in CA when using manual configs. [#6232](https://github.com/cockroachdb/docs/pull/6232) -- Updated the [Kubernetes tutorial](https://www.cockroachlabs.com/docs/v20.1/orchestrate-cockroachdb-with-kubernetes) for compatibility with Helm 3.0. [#6121](https://github.com/cockroachdb/docs/pull/6121) -- Added language-specific connection strings to the instructions on [connecting to a CockroachCloud cluster](https://www.cockroachlabs.com/docs/cockroachcloud/connect-to-your-cluster). [#6077](https://github.com/cockroachdb/docs/pull/6077) -- Added Docker as a download option on the full [release notes list](https://www.cockroachlabs.com/docs/releases#docker). [#5792](https://github.com/cockroachdb/docs/issues/5792) -- Updated the [`IMPORT` documentation](https://www.cockroachlabs.com/docs/v20.1/import) with an example usage of `DELIMITED` with escaping, a note about `DEFAULT` values, and an explanation of the `strict_quotes` option. [#6244](https://github.com/cockroachdb/docs/pull/6244) -- Added an FAQ on [why Cockroach Labs changed the license for CockroachDB](https://www.cockroachlabs.com/docs/v20.1/frequently-asked-questions#why-did-cockroach-labs-change-the-license-for-cockroachdb). [#6154](https://github.com/cockroachdb/docs/pull/6154) -- Corrected the description of the [possible result of clock skew outside the configured clock offset bounds](https://www.cockroachlabs.com/docs/v20.1/operational-faqs#what-happens-when-node-clocks-are-not-properly-synchronized). [#6329](https://github.com/cockroachdb/docs/pull/6329) -- Expanded the [data types overview](https://www.cockroachlabs.com/docs/v20.1/data-types) to indicate whether or not a type supports [vectorized execution](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution). [#6327](https://github.com/cockroachdb/docs/pull/6327) - -Contributors
- -This release includes 279 merged PRs by 47 authors. We would like to thank the following contributors from the CockroachDB community: - -- Akshay Shah (first-time contributor) -- Andrii Vorobiov -- Antoine Grondin -- Jason Brown (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -Security updates
- -- CockroachDB previously allowed non-authenticated access to privileged HTTP endpoints like `/_admin/v1/events`, which operate using `root` user permissions and can thus access (and sometimes modify) any and all data in the cluster. This security vulnerability has been patched by disallowing non-authenticated access to these endpoints and restricting access to admin users only. - - {{site.data.alerts.callout_info}} - Users who have built monitoring automation using these HTTP endpoints must modify their automation to work using an HTTP session token for an admin user. - {{site.data.alerts.end}} - -- Some Admin UI screens (e.g., Jobs) were previously incorrectly displayed using `root` user permissions, regardless of the logged-in user's credentials. This enabled insufficiently privileged users to access privileged information. This security vulnerability has been patched by using the credentials of the logged-in user to display all Admin UI screens. - -- Privileged HTTP endpoints and certain Admin UI screens require an admin user. However, `root` is disallowed from logging in via HTTP and it is not possible to create additional admin accounts without an Enterprise license. This is further discussed [here](https://github.com/cockroachdb/cockroach/issues/43870) and will be addressed in an upcoming patch revision. - - {{site.data.alerts.callout_info}} - Users without an Enterprise license can create an additional admin user using a temporary evaluation license, until an alternative is available. A user created this way will persist beyond the license expiry. - {{site.data.alerts.end}} - -- Some Admin UI screens currently display an error or a blank page when viewed by a non-admin user (e.g., Table Details). This is a known limitation mistakenly introduced by the changes described above. This situation is discussed further [here](https://github.com/cockroachdb/cockroach/issues/44033) and will be addressed in an upcoming patch revision. The list of UI pages affected includes but is not limited to: - - - Job details - - Database details - - Table details - - Zone configurations - - {{site.data.alerts.callout_info}} - Users can access these Admin UI screens using an admin user until a fix is available. - {{site.data.alerts.end}} - -The list of HTTP endpoints affected by the first change above includes: - -| HTTP Endpoint | Description | Sensitive information revealed | Special (see below) | -|--------------------------------------------------------|-----------------------------------|----------------------------------------------------|---------------------| -| `/_admin/v1/data_distribution` | Database-table-node mapping | Database and table names | | -| `/_admin/v1/databases/{database}/tables/{table}/stats` | Table stats histograms | Stored table data via PK values | | -| `/_admin/v1/drain` | API to shut down a node | Can cause DoS on cluster | | -| `/_admin/v1/enqueue_range` | Force range rebalancing | Can cause DoS on cluster | | -| `/_admin/v1/events` | Event log | Usernames, stored object names, privilege mappings | | -| `/_admin/v1/nontablestats` | Non-table statistics | Stored table data via PK values | | -| `/_admin/v1/rangelog` | Range log | Stored table data via PK values | | -| `/_admin/v1/settings` | Cluster settings | Organization name | | -| `/_status/allocator/node/{node_id}` | Rebalance simulator | Can cause DoS on cluster | yes | -| `/_status/allocator/range/{range_id}` | Rebalance simulatoor | Can cause DoS on cluster | yes | -| `/_status/certificates/{node_id}` | Node and user certificates | Credentials | | -| `/_status/details/{node_id}` | Node details | Internal IP addresses | | -| `/_status/enginestats/{node_id}` | Storage statistics | Operational details | | -| `/_status/files/{node_id}` | Retrieve heap and goroutine dumps | Operational details | yes | -| `/_status/gossip/{node_id}` | Gossip details | Internal IP addresses | yes | -| `/_status/hotranges` | Ranges with active requests | Stored table data via PK values | | -| `/_status/local_sessions` | SQL sessions | Cleartext SQL queries | yes | -| `/_status/logfiles/{node_id}` | List of log files | Operational details | yes | -| `/_status/logfiles/{node_id}/{file}` | Server logs + entries | Many: names, application data, credentials, etc. | yes | -| `/_status/logs/{node_id}` | Log entries | Many: names, application data, credentials, etc. | yes | -| `/_status/profile/{node_id}` | Profiling data | Operational details | | -| `/_status/raft` | Raft details | Stored table data via PK values | | -| `/_status/range/{range_id}` | Range details | Stored table data via PK values | | -| `/_status/ranges/{node_id}` | Range details | Stored table data via PK values | | -| `/_status/sessions` | SQL sessions | Cleartext SQL queries | yes | -| `/_status/span` | Statistics per key span | Whether certain table rows exist | | -| `/_status/stacks/{node_id}` | Stack traces | Application data, stored table data | | -| `/_status/stores/{node_id}` | Store details | Operational details | | - -{{site.data.alerts.callout_info}} -"Special" endpoints are subject to the [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) `server.remote_debugging.mode`. Unless the setting was customized, clients are only able to connect from the same machine as the node. -{{site.data.alerts.end}} - -Backward-incompatible changes
- -- The combination of the [`CHANGEFEED`](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) options `format=experimental_avro`, `envelope=key_only`, and `updated` is now rejected. This is because the use of `key_only` prevents any rows with updated fields from being emitted, which renders the `updated` option meaningless. [#41793][#41793] {% comment %}doc{% endcomment %} - -General changes
- -- Client usernames can now be defined to start with a digit; in particular, all-digit usernames are now permitted. [#42464][#42464] {% comment %}doc{% endcomment %} -- Changed the default value of the `--max-sql-memory` limit from 128mb to 25% of system memory. [#42480][#42480] {% comment %}doc{% endcomment %} -- Nodes that have been terminated as the result of a failed consistency check now refuse to restart, making it more likely that the operator notices that there is a persistent issue in a timely manner. [#42401][#42401] -- CockroachDB will now advertise some previously-hidden cluster settings, such as `enterprise.license`, in reports such as the one generated by [`SHOW ALL CLUSTER SETTINGS`](https://www.cockroachlabs.com/docs/v20.1/show-cluster-setting). Only the names are listed; the values are still redacted out. The values can be accessed/modified using the specific statements `SET`/[`SHOW CLUSTER SETTING`](https://www.cockroachlabs.com/docs/v20.1/show-cluster-setting) (singular). [#42520][#42520] {% comment %}doc{% endcomment %} -- It is now possible to easily identify cluster settings for which tuning effects are known and documented, via the new column `public` in the output of [`SHOW ALL CLUSTER SETTINGS`](https://www.cockroachlabs.com/docs/v20.1/show-cluster-setting) and the virtual table `crdb_internal.cluster_settings`. [#42520][#42520] {% comment %}doc{% endcomment %} - -Enterprise edition changes
- -- [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) now supports the restoration of empty databases. [#42005][#42005] {% comment %}doc{% endcomment %} - -SQL language changes
- -- Filters of the form `x = D` (as in `SELECT * FROM t WHERE x = D AND f(x)`), where `D` is a constant and `x` is a column name, will now cause `D` to be inlined for `x` in other filters. [#42151][#42151] {% comment %}doc{% endcomment %} -- The ID of the current session is now available via a `session_id` variable. Session IDs are also now shown in [`SHOW QUERIES`](https://www.cockroachlabs.com/docs/v20.1/show-queries) results. [#41622][#41622] {% comment %}doc{% endcomment %} -- The [`extract()` function](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) now returns values of type float and includes fractional parts in the values for element 'second', 'millisecond', 'julian', and 'epoch'. This improves compatibility with PostgreSQL's `extract()` which returns values of type double precision. [#42131][#42131] {% comment %}doc{% endcomment %} -- `pg_index.indoption` now correctly conveys ascending/descending order and nulls the first/last positioning of columns in an index. [#42343][#42343] {% comment %}doc{% endcomment %} -- Updated pgwire to send `ParameterStatus` messages when certain server parameters are changed for the given session over pgwire. [#42376][#42376] -- Added the ability to run the `avg()` function over intervals. [#42457][#42457] {% comment %}doc{% endcomment %} -- It is now supported to specify selection target aliases as `GROUP BY` columns. Note that the `FROM` columns take precedence over the aliases, which are only used if there are no columns with those names in the current scope. [#42447][#42447] {% comment %}doc{% endcomment %} -- Updated the error message hint when a client attempts to add a sequence-based column to an existing table (which is an unimplemented feature) to refer to Github issue [#42508](https://github.com/cockroachdb/cockroach/issues/42508). [#42509][#42509] -- CockroachDB now returns a more accurate error message, hint, and error code when an error is encountered while adding a new column. [#42509][#42509] -- `EXPLAIN (VERBOSE)` now indicates if auto-commit will be used for mutations. [#42500][#42500] {% comment %}doc{% endcomment %} -- Mutations in CTEs not at the top level are no longer allowed. This restriction is also implemented by Postgres. [#41033][#41033] {% comment %}doc{% endcomment %} -- `WITH` expressions are now hoisted to the top level in a query when possible. [#41033][#41033] -- Made the [`date_trunc` function](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) follow Postgres more closely by truncating to Monday when used with `week`. Previously, it truncated to Sunday. [#42622][#42622] {% comment %}doc{% endcomment %} -- Introduce precision support for [`TIMESTAMP` and `TIMESTAMPTZ`](https://www.cockroachlabs.com/docs/v20.1/timestamp), supporting precisions from 0 to 6 inclusive. Previous versions of `TIMESTAMP` and `TIMESTAMPTZ` defaulted to 6 units of precision. Note that if you downgrade while having a precision set, you will have full precision (6) again, but if you re-upgrade you will find your precisions truncated again. [#42580][#42580] {% comment %}doc{% endcomment %} -- [`CREATE/ALTER SEQUENCE`](https://www.cockroachlabs.com/docs/v20.1/alter-sequence) now support the `OWNED BY` syntax. [#40992][#40992] {% comment %}doc{% endcomment %} -- Changed [`extract()`](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) on a `TIMESTAMPTZ` to match the environment's location in which `extract()` is executed. Previously, it would always perform the operation as if it was in UTC. Furthermore, `timezone`, `timezone_hour` and `timezone_minute` are added to the `extract()` command. [#42632][#42632] {% comment %}doc{% endcomment %} -- [`CHANGEFEED`](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) now supports a `WITH diff` option, which instructs it to include a `before` field in each publication. [#41793][#41793] {% comment %}doc{% endcomment %} -- The fields in the Avro format for [`CHANGEFEED`](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) records have been re-ordered to allow for optimized parsing. This is a backwards compatible change. [#41793][#41793] {% comment %}doc{% endcomment %} -- Users can now use the [`current_timestamp()` function](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) with a given precision from 0-6, e.g., `SELECT current_timestamp(4)`. [#42633][#42633] {% comment %}doc{% endcomment %} -- When executed via the [vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution), make each buffering operator use at most `sql.distsql.temp_storage.workmem` memory (which is 64MB by default). Previously, all buffering operators (like hash and merge joins, sorts) could use arbitrary amounts of memory which could lead to OOM panics. [#42468][#42468] {% comment %}doc{% endcomment %} -- Added a new statement `SHOW PUBLIC CLUSTER SETTINGS` (abbreviated as `SHOW CLUSTER SETTINGS`), which can be used to list only the public cluster settings that are supported for tuning and configuration. [#42520][#42520] {% comment %}doc{% endcomment %} -- Added the `kv.allocator.min_lease_transfer_interval` cluster setting, which allows the minimum interval between lease transfers initiated from each node to be configured. [#42724][#42724] {% comment %}doc{% endcomment %} -- Made string to interval conversion more strict. For example, strings such as `'{{'` and `'{1,2}'` were previously interpreted as the 00:00 interval. They are now rejected. [#42739][#42739] -- Some columns in `pg_type` (`typinput`, `typoutput`, `typreceive`, `typsend`, `typmodin`, `typmodout`, `typanalyze`) were incorrectly typed as `OID` instead of `REGPROC`. This issue has been resolved. [#42782][#42782] -- Users can now use the `cast()` function to cast strings to `int[]` or `decimal[]`, when appropriate. [#42704][#42704] {% comment %}doc{% endcomment %} -- `SET TIME ZONE` now accepts inputs beginning with `GMT` and `UTC`, such as `GMT+5` and `UTC-3:59`. This was previously unsupported. [#42781][#42781] {% comment %}doc{% endcomment %} -- It is now possible to reference tables by table descriptor ID in mutations using `INSERT`/`UPSERT`/`UPDATE`/`DELETE`, in a similar way to what is already allowed in `SELECT` statements. For example: `INSERT INTO [53 AS foo] VALUES (1, 2, 3)`. [#42683][#42683] {% comment %}doc{% endcomment %} -- Added new support for precision for `TIME` types (e.g., `TIME(3)` will truncate to milliseconds). Previously this would raise syntax errors. [#42668][#42668] {% comment %}doc{% endcomment %} - -Command-line changes
- -- Users can now use `cockroach demo` to shut down and restart nodes. This is available in `cockroach demo` only as `demoAdmin UI changes
- -- Fixed typo that breaks [statements page](https://www.cockroachlabs.com/docs/v20.1/admin-ui-statements-page) loading. [#42577][#42577] -- Certain web UI pages (like the list of databases or tables) now restrict their content to match the privileges of the logged-in user. [#42563][#42563] {% comment %}doc{% endcomment %} -- The event log now presents all cluster settings changes, unredacted, when an admin user uses the page. [#42563][#42563] {% comment %}doc{% endcomment %} -- Customization of the UI by users is now only properly saved if the user has write privilege to `system.ui` (i.e., is an admin user). Also, all authenticated users share the same customizations. This is a known limitation and should be lifted in a future version. [#42563][#42563] {% comment %}doc{% endcomment %} -- Access to table statistics are temporarily blocked from access by non-admin users until further notice, for security reasons. [#42563][#42563] {% comment %}doc{% endcomment %} -- Certain debug pages have been blocked from non-admin users for security reasons. [#42563][#42563] {% comment %}doc{% endcomment %} -- The cluster settings page now lists public and reserved settings in two separate tables. [#42520][#42520] {% comment %}doc{% endcomment %} -- Added a new range selector that supports custom time/date ranges. [#41327][#41327] {% comment %}doc{% endcomment %} - -Bug fixes
- -- Reduced the likelihood of out-of-memory errors during histogram collection. [#42357][#42357] -- Fixed a bug which could result in ranges becoming unavailable while a single node is unreachable. The symptoms of this would closely resemble that of a range that has lost a majority of replicas, i.e., the log files would likely include messages of the form "have been waiting [...] for proposing command", except that a majority will be available, though not reflected in the surviving replicas' range status. [#42251][#42251] -- Fixed a Makefile bug that would prevent building CockroachDB from sources in rare circumstances. [#42363][#42363] -- Fixed an out-of-memory error that could occur when collecting statistics on tables with a string index column. [#42372][#42372] -- Changed the return type of (date +- interval) and (interval + date) to be timestamp instead of timestamptz, to be in line with Postgres. Furthermore, this change fixed a bug where these calculations would be incorrect if the current timezone is not UTC. [#42324][#42324] -- Fixed a bug when using `experimental_save_rejected` for CSV [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import) that would cause the rejected row file to overwrite the original input file. [#42398][#42398] -- For tables with dropped indexes, the [`SHOW RANGE FOR ROW`](https://www.cockroachlabs.com/docs/v20.1/show-range-for-row) command sometimes returned incorrect results or an error. Fixed the underlying issue in the `crdb_internal.encode_key` built-in function. [#42456][#42456] -- Fixed a bug in scenarios where we have `UPDATE` cascades, and we are updating a table that has `CHECK` constraints, and the table is self-referencing or is involved in a reference cycle. In this case an `UPDATE` that cascades back in the original table was not validated with respect to the `CHECK` constraints. [#42231][#42231] -- The [movr workload](https://www.cockroachlabs.com/docs/v20.1/movr) now populates table columns with randomly generated data instead of nulls. [#42483][#42483] -- Fixed a bug where if a sequence is used by two columns of the same table, the dependency relation with the first column can be lost. [#40900][#40900] -- Fixed a bug where memory was leaking when counting rows during backup. [#42529][#42529] -- Fixed a bug where, if one were to cast the same type into two or more different precisions/widths from a table in the same `SELECT` query, they would only get the first precision specified. For example, `SELECT a::decimal(10, 3), a::decimal(10, 1) FROM t` would return both results as `a::decimal(10, 3)`. [#42574][#42574] -- CockroachDB will now be less likely hang in an inconvenient/inoperative state if it attempts to access an external HTTP server that blocks or is overloaded. A possible symptom of the bug is a node failing to shut down upon `cockroach quit`. This bug is present since at least version 2.0. [#42536][#42536] -- Stopped including tables that are being restored or imported as valid targets in backups and changefeeds. [#42606][#42606] -- Fixed a bug that would produce a spurious failure with the error message "incompatible `COALESCE` expressions" when adding or validating `MATCH FULL` foreign key constraints involving composite keys with columns of differing types. [#42528][#42528] -- When a custom `nullif` is provided during `IMPORT`, always treat it as a null value. [#42635][#42635] -- Changefeeds now emit backfill row updates for a dropped column when the table descriptor drops that column. [#42053][#42053] -- It's now possible to transfer range leases to lagging replicas. [#42379][#42379] -- Long running transactions which attempt to `TRUNCATE` can now be pushed and will commit in cases where they previously could fail or retry forever. [#42650][#42650] -- Fixed multiple existing bugs: a panic on performing cascade updates on tables with multiple column families; a bug where a self referential foreign key constraint with a `SET DEFAULT` would not be maintained on a cascading update; a bug where multiple self-referential foreign key constraints would cause all the rows in the referenced constraint columns to be set to _NULL_ or a default value on a cascading update. [#42624][#42624] -- Fixed a case where we incorrectly determined that a query (or part of a query) which contains an `IS NULL` constraint on a unique index column returns at most one row, possibly ignoring a `LIMIT 1` clause. [#42760][#42760] -- Fixed a bug with incorrect handling of top _K_ sort by the vectorized engine when _K_ is greater than 1024. [#42831][#42831] -- `ALTER INDEX IF EXISTS` no longer fails when using an unqualified index name that does not match any existing index. Now it is a no-op. [#42797][#42797] -- Prevent internal error in some cases when a _NULL_ literal is passed to the `OVERLAPS` operator. [#42877][#42877] -- CockroachDB now prevents a number of panics from the SQL layer caused by an invalid range split. These would usually manifest with messages mentioning encoding errors (including "found null on not null column", but also possibly various others). [#42833][#42833] -- The result column names for the JSON functions `json{b}_array_elements`, `json{b}_array_elements_text`, `json{b}_each`, `json{b}_each_text` were fixed to be compatible with Postgres. [#41861][#41861] -- Fixed a bug where selecting columns by forcing an `INTERLEAVING` index would error instead of returning the correct results. [#42798][#42798] -- Fixed a bug where attempting to parse `0000-01-01 00:00` when involving `time` did not work, as `pgdate` does not understand `0000` as a year. [#42762][#42762] - -Performance improvements
- -- Transactions are now able to refresh their read timestamp even after the partial success of a batch. [#35140][#35140] -- Some retryable errors are now avoided by declining to restart transactions on some false conflicts. [#42236][#42236] -- CockroachDB now detects the case when the right-hand side of an `ANY` expression is a _NULL_ array (and determine that the expression is always false). [#42698][#42698] -- CockroachDB now generates better plans in many cases where the query has `LEFT` / `RIGHT JOIN`s and also has a `LIMIT`. [#42718][#42718] - -Build changes
- -- Go version 1.12.10+ is now required to build CockroachDB successfully. [#42474][#42474] {% comment %}doc{% endcomment %} -- `make buildshort` is now able to produce valid CCL binaries with all enterprise features (minus UI). [#42541][#42541] {% comment %}doc{% endcomment %} - -Contributors
- -This release includes 195 merged PRs by 44 authors. -We would like to thank the following contributors from the CockroachDB community: - -- Adam Pantel (first-time contributor, CockroachDB team member) -- Ananthakrishnan (first-time contributor) -- Andrii Vorobiov (first-time contributor) -- George Papadrosou -- Jaewan Park -- Roga Pria Sembada -- Ryan Kuo (first-time contributor) -- Vlad -- georgebuckerfield (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -In addition to various updates, enhancements, and bug fixes, this first v20.1 beta release includes the following major highlights: - -- **Online primary key changes**: You can now change a table’s primary key using the `ALTER TABLE ... ALTER PRIMARY KEY` statement. Changing a table’s primary key rewrites its primary and some secondary indexes behind-the-scenes and can take a while, but the table remains online with no interruption to data access. For now, this feature is considered experimental and is behind a [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings). To try it out, run `SET experimental_enable_primary_key_changes = true`. The syntax is `ALTER TABLE table_name ALTER PRIMARY KEY USING COLUMNS (x, y)`. -- **Full cluster restore**: You can now use CockroachDB's [Enterprise `RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) feature to restore a full cluster `BACKUP` to a new cluster, including all configuration and system information such as [user privileges](https://www.cockroachlabs.com/docs/v20.1/authorization#privileges), [zone configurations](https://www.cockroachlabs.com/docs/v20.1/configure-replication-zones), and [cluster settings](https://www.cockroachlabs.com/docs/v20.1/cluster-settings). Restoring a cluster backup to an existing cluster is not supported. -- **Encrypted backup files**: You can now use an encryption key to encrypt data in [Enterprise `BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) files, and to decrypt the data upon [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore). - -Backward-incompatible changes
- -- [`cockroach init`](https://www.cockroachlabs.com/docs/v20.1/cockroach-init) now waits for server readiness and thus no longer fails when a mistaken server address is provided. [#43904][#43904] {% comment %}doc{% endcomment %} -- The `cockroach user` CLI command has been removed. It was previously deprecated in CockroachDB 19.2. Note that a 19.2 client (supporting `cockroach user`) can still operate user accounts in a 20.1 server. [#43903][#43903] {% comment %}doc{% endcomment %} -- CockroachDB now creates files without read permissions for the "others" group. Sites that automate file management (e.g., log collection) using multiple user accounts now must ensure that the CockroachDB server and the management tools running on the same system are part of a shared unix group. [#44043][#44043] {% comment %}doc{% endcomment %} -- Previously, intervals cast to integers and floats would rely on a year being 365 days. To match `extract('epoch' from interval)` behavior in PostgreSQL/CockroachDB to 365.25 days, casting to integers and floats now values a year at 365.25 days in seconds instead of 365 days. [#43923][#43923] {% comment %}doc{% endcomment %} - -Security updates
- -- An admin user is now required to access statement details in the Admin UI and HTTP endpoint. Previously, any user could access these details, which could result in users accessing data that they didn't have privileges to see. [#44349][#44349] {% comment %}doc{% endcomment %} -- CockroachDB now properly rejects control characters in the value of the `server.host_based_authentication.configuration` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings). Previously, these characters were accepted and would silently result in unintended rule matching. Deployments careful to strip control characters from their HBA configurations are not affected. [#43811][#43811] {% comment %}doc{% endcomment %} -- Connections using unix sockets are now subject to the HBA rules defined via the setting `server.host_based_authentication.configuration`, in a way compatible with PostgreSQL: incoming unix connections match `local` rules, whereas incoming TCP connections match `host` rules. The default HBA configuration used when the [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) is empty is now: - - ~~~ - host all root all cert - host all all all cert-password - local all all password - ~~~ - [#43848][#43848] -- Previously, when setting a user's password to enable password authentication for the user, it was not possible to revert this choice. The only way to disable password authentication was to either drop the user or add a specific per-user HBA rule. This has been fixed and the PostgreSQL-compatible [`ALTER USER WITH PASSWORD NULL`](https://www.cockroachlabs.com/docs/v20.1/alter-user) statement can now be used to clear the user's password. [#43892][#43892] {% comment %}doc{% endcomment %} -- A CockroachDB node process ([`start`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start)/[`start-single-node`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start-single-node)) now configures its umask to create all its files without unix permission bits for "others", so that data/log/etc files do not become world-readable by default in systems that do not otherwise customize umask to enforce log file visibility. The files produced by other `cockroach` commands (e.g., the [CLI commands](https://www.cockroachlabs.com/docs/v20.1/cockroach-commands)) do not force their umask. Note that after upgrading to this release, in sites where permissions matter, administrators should be careful to run `chmod -R o-rwx` in directories where files were created by a previous version. [#44043][#44043] {% comment %}doc{% endcomment %} -- The new command `cockroach auth-session login` (reserved for administrators) creates authentication tokens with an arbitrary expiration date. Operators should be careful to monitor `system.web_sessions` and enforce policy-mandated expirations by either using SQL queries or the new command `cockroach auth-session logout`. [#43872][#43872] {% comment %}doc{% endcomment %} -- The `root` user can now have a password, like any other member of the admin role. However, as in previous versions, the HBA configuration cannot be overridden to prevent `root` from logging in with a valid TLS client certificate. This special rule remains enforced in order to ensure that users cannot "lock themselves out" of administrating their cluster. [#43893][#43893] {% comment %}doc{% endcomment %} -- The `root` user remains special with regard to [authentication](https://www.cockroachlabs.com/docs/v20.1/authentication) when some system ranges are unavailable. In that case, password authentication will fail, subject to a timeout set to the minimum of 5 seconds and the configured value of `system.user_login.timeout`, because the password cannot be retrieved from a system table. However, certificate authentication remains available. [#43893][#43893] {% comment %}doc{% endcomment %} - -General changes
- -- `SHOW JOBS` and the Jobs page in the Admin UI now show the parameters used for connecting to external storage, with only the values of parameters classified as secrets redacted. [#44737][#44737] {% comment %}doc{% endcomment %} -- It's now possible to disable job execution on a node in emergency cases. To do so, place a `DISABLE_STARTING_BACKGROUND_JOBS` file in the node's first store directory. [#44786][#44786] {% comment %}doc{% endcomment %} -- A node no longer declares itself unready through the [`/health?ready=1`](https://www.cockroachlabs.com/docs/v20.1/monitoring-and-alerting#health-ready-1) endpoint while in the process of decommissioning. It continues to declare itself unready while draining. [#43889][#43889] {% comment %}doc{% endcomment %} -- CockroachDB will now report a timeout error when a client attempts to connect via SQL or the Admin UI and some system ranges are unavailable. The previous behavior was to wait indefinitely. The timeout is configurable via the [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) `server.user_login.timeout` and is set to 10 seconds by default. The value "0" means "indefinitely" and can be used to restore the pre-v20.1 behavior. This timeout does not apply to the `root` user, which is always able to login on unavailable clusters. [#44022][#44022] {% comment %}doc{% endcomment %} -- The `kv.allocator.range_rebalance_threshold` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings), which controls how far away from the mean a store's range count must be before it is considered for rebalance, is now subject to a 2-replica minimum. If, for example, the mean number of replicas per store is 5.6 and the setting is 5%, the store will not be considered for rebalance unless the number of replicas is lesser than 3 or greater than 8. Previously, the bounds would have been 5 and 6. [#44247][#44247] {% comment %}doc{% endcomment %} - -Enterprise edition changes
- -- Added the ability to restore a cluster backup to a new cluster, including all configuration and system information such as user privileges, zone configurations, and cluster settings. Restoring a cluster backup to an existing cluster is not supported. [#43828][#43828] -- Added support for encrypting `BACKUP`/`RESTORE` files via the `encryption_passphrase` option. [#44177][#44177] - -SQL language changes
- -- Foreign key checks for insertions performed by [`UPSERT`s](https://www.cockroachlabs.com/docs/v20.1/upsert) are now handled by the optimizer. [#43824][#43824] {% comment %}doc{% endcomment %} -- Added a rough estimation of execution progress to [`SHOW QUERIES`](https://www.cockroachlabs.com/docs/v20.1/show-queries). [#42518][#42518] {% comment %}doc{% endcomment %} -- Added `NOT NULL` columns as check constraints to `information_schema.table_constraints`, for PostgreSQL compatibility. [#44731][#44731] {% comment %}doc{% endcomment %} -- Added support for temporary view creation, if temporary tables are enabled. Temporary views disappear at the end of a connection. Views that depend on temporary tables are automatically temporary. [#44729][#44729] -- Added the `require_explicit_primary_keys` and `sql.defaults.require_explicit_primary_keys.enabled` [cluster settings](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) to control whether CockroachDB should error out when tables are created without explicit primary keys. [#44702][#44702] {% comment %}doc{% endcomment %} -- The `enable_primary_key_changes` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) has changed to `experimental_enable_primary_key_changes`. [#43818][#43818] -- Primary key columns are no longer required to be in column family `0`. [#43742][#43742] -- Primary key changes are now enabled on tables with multiple [column families](https://www.cockroachlabs.com/docs/v20.1/column-families). [#43821][#43821] -- The primary key of a table can now be altered to one that is [interleaved](https://www.cockroachlabs.com/docs/v20.1/interleave-in-parent) in another table. [#44038][#44038] -- Primary key changes can now be performed on interleaved children. [#44075][#44075] -- Primary key changes are now enabled on tables that have foreign key relationships. [#43830][#43830] -- Extract can now be called on an interval (e.g., `extract(day from interval '254 days')`). This follows the PostgreSQL implementation. Furthermore, this deprecates `extract_duration`, which will be removed at a later date. [#43293][#43293] {% comment %}doc{% endcomment %} -- CockroachDB previously did not support `AT TIME ZONE` parsing for anything other than precise location strings (e.g., `AT TIME ZONE 'Australia/Sydney'`). CockroachDB now supports parsing `AT TIME ZONE` with various other offset behaviors supported by `SET TIME ZONE` (e.g., `AT TIME ZONE '+3'`, `AT TIME ZONE 'GMT+4'`). [#43414][#43414] {% comment %}doc{% endcomment %} -- CockroachDB now supports `SET TIME ZONE` with colons (e.g., `+4:00`). [#43414][#43414] {% comment %}doc{% endcomment %} -- Previously, `SELECT interval '1-2 1' DAY TO HOUR` would fail. This is now permitted as per the SQL standard. [#43379][#43379] {% comment %}doc{% endcomment %} -- Previously, spaces added to intervals with qualifiers (e.g., `SELECT interval ' 1 ' YEAR`) would be evaluated as seconds. The qualifier is now used as the multiplier. [#43379][#43379] {% comment %}doc{% endcomment %} -- Previously, adding a decimal point to days (e.g., `SELECT interval '1.5 01:00:00'`) would return `1 day 01:00:00`, unlike PostgreSQL, which returns `1 day 13:00:00`. The behavior now matches PostgreSQL. [#43379][#43379] {% comment %}doc{% endcomment %} -- Previously, using the `Y-M constant` format for intervals (e.g., `SELECT INTERVAL '1-2 3'`) would always resolve the constant component (3) as seconds, even for items such as `SELECT INTERVAL '1-2 3' DAY`. The behavior has been corrected and now matches PostgreSQL. [#43379][#43379] {% comment %}doc{% endcomment %} -- Some tools generate SQL that includes the `fillfactor` storage parameter, e.g., `CREATE TABLE ... WITH (fillfactor=100)`. This syntax is now supported, but has no effect, since the parameter has no meaning in CockroachDB. [#43307][#43307] -- [`SHOW RANGES`](https://www.cockroachlabs.com/docs/v20.1/show-ranges) now shows locality information consistent with the range descriptor when node ID and store ID do not match. [#43807][#43807] {% comment %}doc{% endcomment %} -- Ranges are now considered under-replicated by the [`system.replication_stats` report](https://www.cockroachlabs.com/docs/v20.1/query-replication-reports#system-replication_stats) when one of the replicas is unresponsive (or the respective node is not running). [#43825][#43825] {% comment %}doc{% endcomment %} -- [`CREATE USER`](https://www.cockroachlabs.com/docs/v20.1/create-user) and [`ALTER USER`](https://www.cockroachlabs.com/docs/v20.1/alter-user) now accept the parameter `[WITH] PASSWORD NULL` to indicate the user's password should be removed, thus preventing them from using password authentication. This is compatible with PostgreSQL. [#43892][#43892] {% comment %}doc{% endcomment %} -- Previously, a panic could occur when a table had a default column and a constraint in the [`CREATE TABLE`](https://www.cockroachlabs.com/docs/v20.1/create-table) statement. This is now fixed. [#43959][#43959] -- Previously, [`DECIMAL`](https://www.cockroachlabs.com/docs/v20.1/decimal) types could not be sent over the network when the computation was performed by the [vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution). This has been fixed, and the vectorized engine now fully supports `DECIMAL` type. [#43311][#43311] {% comment %}doc{% endcomment %} -- Previously, there was a restriction that foreign keys could only reference one outbound column at any given point in time (e.g., in `CREATE TABLE test(a int)`, having two foreign keys on column `a` was not allowed). This restriction is now removed. [#43417][#43417] {% comment %}doc{% endcomment %} -- Invalid usages of `FOR UPDATE` [locking clauses](https://www.cockroachlabs.com/docs/v20.1/sql-grammar#for_locking_clause) are now rejected by the SQL optimizer. [#43887][#43887] -- Added `to_hex(string)` string functionality. [#44016][#44016] {% comment %}doc{% endcomment %} -- Previously, `to_hex(-1)` would return `-1` instead of the negative hex representation (`FFFFFFFFFFFFFFFF`). This is now fixed. [#44016][#44016] -- The new global default [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) `sql.defaults.temporary_tables.enabled` can be used to enable temporary tables. [#43816][#43816] -- An optimization has been added to scan over only 1 row when finding the MIN/MAX of a single aggregate group, as long as the correct index is present. [#43547][#43547] -- [`SHOW CREATE TABLE`](https://www.cockroachlabs.com/docs/v20.1/show-create) now also emits the `COMMENT` statements sufficient to populate the table's user-defined comments, if any, alongside the `CREATE` statement proper. [#43152][#43152] {% comment %}doc{% endcomment %} -- More invalid usages of `FOR UPDATE` [locking clauses](https://www.cockroachlabs.com/docs/v20.1/sql-grammar#for_locking_clause) are now rejected by the SQL optimizer. [#44015][#44015] -- Added the `timeofday` functionality supported by PostgreSQL, which returns the time on one of the nodes as a formatted string. [#44050][#44050] {% comment %}doc{% endcomment %} -- Added `localtime`, which by default returns the current time as the [`TIME`](https://www.cockroachlabs.com/docs/v20.1/time) data type (as opposed to `current_time`, which returns the [`TIMETZ`](https://www.cockroachlabs.com/docs/v20.1/time) data type). [#44042][#44042] {% comment %}doc{% endcomment %} -- Added `localtimestamp`, which by default returns the current timestamp as the [`TIMESTAMP`](https://www.cockroachlabs.com/docs/v20.1/timestamp) data type (as opposed to `current_timestamp`, which returns the [`TIMESTAMPTZ`](https://www.cockroachlabs.com/docs/v20.1/timestamp) data type). [#44042][#44042] -- Added support for having `D:H:M`, `D:M:S.fff`, or `D:H:M:S.fff` for interval parsing if the first element is a decimal or empty (e.g., `:04:05` and `1.0:04:05` would be `04:05:00` and `1 day 04:05:00` respectively). [#43924][#43924] {% comment %}doc{% endcomment %} -- Previously, floats were supported in `H:M:S` formats for interval parsing (e.g., `1.0:2.0:3.0`), which did not make sense. Floats are no longer allowed for the M field. [#43924][#43924] {% comment %}doc{% endcomment %} -- Previously, CockroachDB would return an internal error when using [`SET tracing`](https://www.cockroachlabs.com/docs/v20.1/set-vars#set-tracing) with any type other than string. Now it will return a regular query error. Additionally, boolean arguments are now supported in `SET tracing`, and `true` is mapped to `on` mode of tracing whereas `false` is mapped to `off`. [#44260][#44260] {% comment %}doc{% endcomment %} -- Indexes that reference, or are referenced by, a foreign key constraint can now be dropped if there is another suitable index for the constraint. [#43332][#43332] {% comment %}doc{% endcomment %} -- Added a `log` [builtin](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) for any base (e.g., `log(2.0, 4.0)`). [#41848][#41848] {% comment %}doc{% endcomment %} -- Non-admin users can now query [`SHOW JOBS`](https://www.cockroachlabs.com/docs/v20.1/show-jobs) and `crdb_internal.jobs` and see their own jobs. [#44345][#44345] {% comment %}doc{% endcomment %} -- [Vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) now supports `DISTINCT` on unordered input. [#42522][#42522] {% comment %}doc{% endcomment %} -- `pg_catalog` access method information is now more accurate. Added inverted index to the access methods listed in `pg_am` and set `pg_class.relam` to zero for sequences and views, which is more consistent with PostgreSQL. [#43715][#43715] -- An overload has been added to the `unnest` [builtin](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) function in order to support multiple array arguments. [#41557][#41557] -- Duplicate labels are allowed when declaring a tuple, but a "column reference is ambiguous" error is now returned if a duplicate label is accessed (e.g.,`SELECT ((1, '2') AS a, a);` is successful, but `SELECT (((1,2,3) AS a,b,a)).a;` returns an error). [#41557][#41557] -- Telemetry information is now collected for uses of secondary indexes that use [column families](https://www.cockroachlabs.com/docs/v20.1/column-families). [#44506][#44506] -- Telemetry information is now collected for uses of the [`SHOW RANGE ... FROM ROW`](https://www.cockroachlabs.com/docs/v20.1/show-range-for-row) command. [#44502][#44502] -- CockroachDB now supports `AT TIME ZONE` and the `timezone` [builtin](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) for `time` and `timetz` methods. [#44099][#44099] {% comment %}doc{% endcomment %} -- `AT TIME ZONE` now supports the POSIX standard. Offsets such as `UTC+3` and `+3` are interpreted to be timezones *west* of UTC instead of *east* of UTC (e.g., `America/New_York` is equivalent to `UTC+5` instead of `UTC-5`). [#44099][#44099] -- CockroachDB supports `timezone(timestamp(tz), str)`, but PostgreSQL supports the inverse `timezone(str, timestamp(tz))`. Both are now supported, and the former version will be deprecated at a later stage. - CockroachDB now supports `str AT TIME ZONE str`, removing the need for an explicit cast. [#44099][#44099] {% comment %}doc{% endcomment %} -- The [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) now supports `bool_and`/`bool_or` [builtin](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) aggregation functions. [#44164][#44164] {% comment %}doc{% endcomment %} -- Non-admin users can now use the `ZONECONFIG` privilege to create, edit, and delete zone configurations. [#43941][#43941] {% comment %}doc{% endcomment %} - -Command-line changes
- -- When running [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) with multiple nodes, each node now takes up to 128MB for SQL memory and 64MB for cache by default. Previously, each node would take up to 25% of total memory, which could cause OOM problems. These defaults can be modified via the `--max-sql-memory` and `--cache` flags. [#44478][#44478] {% comment %}doc{% endcomment %} -- Connections using unix sockets are now accepted even when the server is running in secure mode. Consult [`cockroach start --help`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start) for details about the `--socket` parameter. [#43848][#43848] {% comment %}doc{% endcomment %} -- The [`cockroach init`](https://www.cockroachlabs.com/docs/v20.1/cockroach-init) command now waits until the node at the provided server address is ready to accept initialization. This also waits for network readiness. This makes it easier to implement initialization scripts by removing the need for a loop. In addition, implementing such a loop is operationally unsafe and is not recommended. [#43904][#43904] {% comment %}doc{% endcomment %} -- The MovR dataset will now be split among all nodes in the demo cluster. [#43798][#43798] {% comment %}doc{% endcomment %} -- [`cockroach demo --with-load`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) can now round robin queries to all nodes in the demo cluster. [#43474][#43474] {% comment %}doc{% endcomment %} -- The SQLSmith workload now accepts an argument `error-sensitivity` which controls what types of errors the workload exits on. [#43925][#43925] -- [`cockroach gen haproxy`](https://www.cockroachlabs.com/docs/v20.1/cockroach-gen) now excludes decommissioned nodes. [#43908][#43908] {% comment %}doc{% endcomment %} -- The [`cockroach node decommission`](https://www.cockroachlabs.com/docs/v20.1/cockroach-node#node-decommission) and [`cockroach node recommission`](https://www.cockroachlabs.com/docs/v20.1/cockroach-node#node-recommission) commands now produce a warning on the standard error if one of the node(s) specified is already (d/r)ecommissioned. [#43915][#43915] {% comment %}doc{% endcomment %} -- The [`start`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start) and [`start-single-node`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start-single-node) commands no longer initiate a 1-minute hard shutdown countdown after a request to gracefully terminate. This means that graceful shutdowns are now free to take longer than one minute. It also means that deployments where a maximum shutdown time must be enforced must now use a service manager that is suitably configured to do so. [#44074][#44074] {% comment %}doc{% endcomment %} -- The new `cockroach auth-session login`, `cockroach auth-session list`, and `cockroach auth-session logout` commands are now provided to facilitate the management of web sessions. The command `auth-session login` also produces a HTTP cookie which can be used by non-interactive HTTP-based database management tools. It also can generate such a cookie for the `root` user, who would not otherwise be able to do so using a web browser. [#43872][#43872] {% comment %}doc{% endcomment %} - -Admin UI changes
- -- Decommissioned node history is now viewable on a dedicated page. This reduces the amount of information on the [Cluster Overview](https://www.cockroachlabs.com/docs/v20.1/admin-ui-cluster-overview-page) page. [#42817][#42817] {% comment %}doc{% endcomment %} -- Execution Latency graph is now renamed to "KV Execution Latency". [#43290][#43290] {% comment %}doc{% endcomment %} -- Redesigned the Cluster Overview page. [#43552][#43552] {% comment %}doc{% endcomment %} -- We previously introduced a fix on the Admin UI to prevent non-admin users from executing queries. However, this inadvertently caused certain pages requiring table details not to display. This issue has now been resolved. [#44167][#44167] -- Non-admin users can now use the [Jobs](https://www.cockroachlabs.com/docs/v20.1/admin-ui-jobs-page) page of the Admin UI to see their own jobs. [#44345][#44345] {% comment %}doc{% endcomment %} - -Bug fixes
- -- When running a query with the `LIKE` [operator](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) using custom `ESCAPE` symbols, patterns containing Unicode characters no longer result in an internal error. [#44633][#44633] -- Fixed a server crash caused by some queries with outer joins and negative limits. [#44590][#44590] -- When cleaning up [schema changes](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes), CockroachDB no longer repeatedly looks for non-existing jobs, which could cause high memory usage. [#44607][#44607] -- Calling `NULLIF` with one null argument no longer results in an internal error. [#44718][#44718] -- Fixed a "no indexes" internal error in some cases when GROUP BY is used on a virtual table. [#44692][#44692] -- Fixed invalid query results in some cases involving stored columns with `NULL` values. [#44728][#44728] -- Fixed invalid query results in some cases where part of a `WHERE` clause is incorrectly discarded. [#44668][#44668] -- Fixed bugs around [`cockroach dump`](https://www.cockroachlabs.com/docs/v20.1/cockroach-dump) and [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import)/[`EXPORT`](https://www.cockroachlabs.com/docs/v20.1/export) where columns of arrays or collated strings were not able to be roundtripped between `cockroach` and the dump. [#44464][#44464] -- `CASE` [operators](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) with an unknown `WHEN` type no longer return an error. [#44756][#44756] -- Fixed a type checking error where `BETWEEN` would sometimes allow boundary expressions of a different type. [#44775][#44775] -- Fixed a "cannot map variable" error in some rare cases involving joins. [#44788][#44788] -- Fixed a bug causing lost update transaction anomalies. [#44507][#44507] -- Fixed an occasional "concurrent map write" crash. [#44872][#44872] -- Fixed a bug where [`DROP INDEX`](https://www.cockroachlabs.com/docs/v20.1/drop-index) jobs waiting for garbage collection might deleted before the data was actually removed from disk. [#44831][#44831] -- CockroachDB no longer returns an internal error when executing a `substring()` function with non-INT8 start and length arguments via the vectorized engine. [#44887][#44887] -- Fixed incorrect deduplication of impure expressions (e.g., `gen_random_uuid`) in projections and default values. [#44890][#44890] -- [`TIMESTAMPTZ`](https://www.cockroachlabs.com/docs/v20.1/timestamp) operations now correctly take context timezone (set by `SET TIME ZONE`) into account. Previously, not doing so lead to bugs involving daylight saving in arithmetic. For example, with `America/Chicago`, evaluating `'2010-11-06 23:59:00-05'::timestamptz + '1 day'::interval` would return incorrect results as it assumed it was a fixed offset of `-5` instead. Also, text conversion from `TIMESTAMPTZ` TO `STRING` sometimes used the wrong timezone offset if the location of the session did not match the location when the `TIMESTAMPTZ` was parsed, and `to_json()` built-ins with `TIMESTAMPTZ` did not take session timezone into consideration. [#44812][#44812] -- Previously, when [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) was used with `vectorize=experimental_on`, CockroachDB could incorrectly report some values as NULL. This has now been fixed. [#43785][#43785] -- When casting a string to bytes, octal escapes greater than `377` will now generate an error, rather than silently wrapping around. [#43806][#43806] -- A job can be running but shown in a pending state. [#43814][#43814] -- On Linux machines, we now respect the available memory limit as dictated by the cgroup limits which apply to the `cockroach` process. [#43137][#43137] -- Previously, CockroachDB would return incorrect results for some aggregate functions when used as [window functions](https://www.cockroachlabs.com/docs/v20.1/window-functions) with non-default window frame. This is now fixed. Note that MIN, MAX, SUM, AVG, and "pure" window functions (i.e., non-aggregates) were not affected. [#39308][#39308] -- Previously, CockroachDB could return an internal error when running a query with a CAST operation (`:::`) in some cases when using the [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution). This is now fixed. [#43857][#43857] -- Previously, a query shutdown mechanism could fail to fully cleanup the infrastructure when the query was executed via the [vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) and the query plan contained wrapped row-by-row processors (in v19.2, this applies to Lookup joins and Index joins). This is now fixed. [#43579][#43579] -- Fixed a bug introduced in v19.2 that would allow foreign keys to use a unique index on the referenced columns that indexed more columns than were included in the columns used in the FK constraint, which allows potentially violating uniqueness in the referenced columns themselves. [#43793][#43793] -- [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) cleanup is now run exactly once. [#43933][#43933] -- A benign error previously logged at the `ERROR` level is now logged at the `INFO` level behind a `verbosity(2)` flag. This error might have been observed as "context canceled: readerCtx in Inbox stream handler". [#44020][#44020] -- A bug causing lost update transaction anomalies was fixed. [#42969][#42969] -- Previously, an internal error could occur when a query with an aggregate function MIN or MAX was executed via the [vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) when the input column was either INT2 or INT4 type. This is now fixed. [#43985][#43985] -- [CDC](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) is no longer susceptible to a bug where a resolved timestamp might be published before all events that precede it have been published in the presence of a Range merge. [#44035][#44035] -- [`cockroach debug zip`](https://www.cockroachlabs.com/docs/v20.1/cockroach-debug-zip) now emits the `goroutine` file in the proper sub-directory when the corresponding call fails with an error. [#44064][#44064] -- [`cockroach debug zip`](https://www.cockroachlabs.com/docs/v20.1/cockroach-debug-zip) is again able to operate correctly and continue to iterate over all nodes if one of the nodes does not deliver its goroutine dumps. It would previously prematurely and incorrectly stop with an incomplete dump; this was a regression introduced in v19.2. [#44064][#44064] -- The file generated by [`cockroach gen haproxy`](https://www.cockroachlabs.com/docs/v20.1/cockroach-gen) no longer gets an executable bit. The executable bit was previously placed in error. [#44043][#44043] -- Fixed internal error of the form "x FK cols, only y cols in index" in some cases when inserting into a table with foreign key references. [#44031][#44031] -- CockroachDB now ensures internal cleanup after [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/backup) is only run once. [#43960][#43960] -- Converted a panic in `golang.org/x/text/language/tags.go` when using collated strings to an error. [#44103][#44103] -- SQL mutation statements that target tables with no foreign key relationships now correctly read data as per the state of the database when the statement started execution. This is required for compatibility with PostgreSQL and to ensure deterministic behavior when certain operations are parallelized. Prior to this fix, a statement could incorrectly operate multiple times (i.e., the [Halloween Problem](https://wikipedia.org/wiki/Halloween_Problem)) on data that itself was writing, and potentially never terminate. This fix is limited to tables without FK relationships, and for certain operations on tables with FK relationships; in other cases, the fix is not active and the bug is still present. A full fix will be provided in a later release. [#42862][#42862] -- CockroachDB now properly supports using `--url` with query options (e.g., `application_name`) but without specifying `sslmode`. The default of `sslmode=disable` is assumed in that case. This applies to the [CLI commands](https://www.cockroachlabs.com/docs/v20.1/cockroach-commands) that use SQL, including (but not limited to) [`cockroach sql`](https://www.cockroachlabs.com/docs/v20.1/cockroach-sql), [`cockroach node`](https://www.cockroachlabs.com/docs/v20.1/cockroach-node), `cockroach auth-session`, and [`cockroach debug zip`](https://www.cockroachlabs.com/docs/v20.1/cockroach-debug-zip). [#44113][#44113] -- The GC process has been improved to paginate the key versions of a key to fix OOM crashes, which can occur when there are extremely large numbers of versions for a given key. [#43862][#43862] -- Removed [statistics](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer#table-statistics) information from backup jobs' payload information to avoid excessive memory utilization when issuing commands such as [`SHOW JOBS`](https://www.cockroachlabs.com/docs/v20.1/show-jobs). [#44180][#44180] -- Previously, CockroachDB could crash in special circumstances when using the [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) with the `vectorize=experimental_on` setting. This is now fixed. [#44144][#44144] -- Fixed planning bug related to FULL joins between single-row relations. [#44156][#44156] -- Fixed "CopyFrom requires empty destination" internal error. [#44114][#44114] -- Fix a bug where multiple nodes attempted to populate the results for [`CREATE TABLE ... AS`](https://www.cockroachlabs.com/docs/v20.1/create-table-as) leading to duplicate rows. [#43840][#43840] -- All admin users are now allowed to use [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup)/[`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) and [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import). [#44250][#44250] -- `to_english(-2^63)` previously errored. This is now fixed to return the correct result. [#44251][#44251] -- Fixed internal error when mixed types are used with `BETWEEN`. [#44216][#44216] -- Fixed an error that could occur in very specific scenarios involving mutations and foreign keys. [#44314][#44314] -- Previously, CockroachDB would return an internal error when a query with CASE operator that returns only NULL values was executed via the [vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution). This is now fixed. [#44346][#44346] -- Fixed a bug when cascade deleting thousands of rows across interleaved tables. [#44159][#44159] -- Fixed incorrect plans in very rare cases involving filters that aren't constant folded in the optimizer but that can be evaluated statically when running a given query. [#44307][#44307] -- Fixed an internal error that could happen in the planner when table statistics were collected manually using [`CREATE STATISTICS`](https://www.cockroachlabs.com/docs/v20.1/create-statistics) for different columns at different times. [#44430][#44430] -- Fixed "no output column equivalent to" and "column not in input" errors in some cases involving `DISTINCT ON` and `ORDER BY`. [#44543][#44543] -- Fixed possibly incorrect query results in various cornercases, especially when [`SELECT DISTINCT`](https://www.cockroachlabs.com/docs/v20.1/select-clause) is used. [#44386][#44386] -- Previously, CockroachDB would return an internal error when a `substring` function with a negative length was executed via the [vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution). This is now fixed (it now returns a regular query error). [#44627][#44627] - -Performance improvements
- -- Secondary indexes that store columns on tables with [column families](https://www.cockroachlabs.com/docs/v20.1/column-families) can now perform reads on only the needed columns in single row reads. [#43567][#43567] -- CockroachDB now uses better execution plans in some cases where there is an ordering on an expression that can be constant-folded to a simple column reference. [#43724][#43724] -- Histograms are now collected automatically for all boolean columns, resulting in better query plans in some cases. For tables that aren't being modified frequently, it might be necessary to run [`CREATE STATISTICS`](https://www.cockroachlabs.com/docs/v20.1/create-statistics) manually to see the benefit. [#44151][#44151] - -Build changes
- -- Building CockroachDB now requires Node.js version 12 or greater. [#44024][#44024] {% comment %}doc{% endcomment %} - -Doc updates
- -- Added a new [Technical Advisories](https://www.cockroachlabs.com/docs/advisories) section with information about major issues with CockroachDB that may impact security or stability in production environments. [#6492](https://github.com/cockroachdb/docs/pull/6492) -- Added a tutorial on [streaming an Enterprise changefeed from CockroachCloud to Snowflake](https://www.cockroachlabs.com/docs/cockroachcloud/stream-changefeed-to-snowflake-aws). [#6317](https://github.com/cockroachdb/docs/pull/6317) -- Documented the [`TIMETZ`](https://www.cockroachlabs.com/docs/v20.1/time) data type. [#6391](https://github.com/cockroachdb/docs/pull/6391) -- Fixed the [JavaScript code sample for connecting to a CockroachCloud cluster](https://www.cockroachlabs.com/docs/cockroachcloud/connect-to-your-cluster). [#6393](https://github.com/cockroachdb/docs/pull/6393) -- Clarified the behavior of default values when using [`IMPORT INTO`](https://www.cockroachlabs.com/docs/v20.1/import-into). [#6396](https://github.com/cockroachdb/docs/pull/6396) -- Clarified the behavior of [decommissioning](https://www.cockroachlabs.com/docs/v20.1/remove-nodes) in clusters of various sizes. [#6402](https://github.com/cockroachdb/docs/pull/6402) -- Documented [`LATERAL` joins](https://www.cockroachlabs.com/docs/v20.1/joins#lateral-joins) and [subqueries](https://www.cockroachlabs.com/docs/v20.1/subqueries#lateral-subqueries). [#6425](https://github.com/cockroachdb/docs/pull/6425) -- Improved the [Django "build an app" code sample](https://www.cockroachlabs.com/docs/v20.1/build-a-python-app-with-cockroachdb-django). [#6404](https://github.com/cockroachdb/docs/pull/6404), [#6412](https://github.com/cockroachdb/docs/pull/6412) -- Updated [Change Data Capture examples](https://www.cockroachlabs.com/docs/v20.1/change-data-capture#create-a-changefeed-connected-to-kafka) to show more than one table in a changefeed. [#6511](https://github.com/cockroachdb/docs/pull/6511) - -Contributors
- -This release includes 420 merged PRs by 68 authors. We would like to thank the following contributors from the CockroachDB community: - -- Andrii Vorobiov -- George Papadrosou -- Jaewan Park -- Jason Brown -- Y.Horie (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -In addition to various updates, enhancements, and bug fixes, this v20.1 beta release includes the ability to **log slow SQL queries**. By setting the `sql.log.slow_query.latency_threshold` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings), each node of your cluster will log queries that exceed the specified service latency to a new file called `cockroach-sql-slow.log`. - -Security updates
- -- Operators can now disable external HTTP access when performing certain operations (`BACKUP`, `IMPORT`, etc.). The external HTTP access, as well as custom HTTP endpoints, are disabled by providing an `--external-io-disable-http` flag. This flag provides a light-weight option to disable external HTTP access in environments where running a full-fledged proxy server may not be feasible. If running a proxy server is acceptable, operators may choose to start the `cockroach` binary while specifying the `HTTP(S)_PROXY` environment variable. [#44900][#44900] - -General changes
- -- Added a slow query log facility to CockroachDB, configurable by setting the `sql.log.slow_query.latency_threshold` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings). When used, each node of your cluster will record queries that exceed the specified service latency to a new file called `cockroach-sql-slow.log`. [#44816][#44816] -- New clusters will have a larger default range size of 512 MB, which will result in fewer ranges for the same amount of data. [#45209][#45209] - -Enterprise edition changes
- -- Row counts in `BACKUP` and `RESTORE` now include rows in system tables. [#44965][#44965] - -SQL language changes
- -- Disallowed changing the primary key of a table in the same transaction as its `CREATE TABLE` statement. [#44815][#44815] -- Introduced the ability to create views using `CREATE VIEW IF NOT EXISTS`, which does nothing if the view already existed. [#44913][#44913] -- If temporary table creation is enabled, users now have the ability to create temporary sequences as well. [#44806][#44806] -- Added built-in support of hash-sharded indexes with new `USING HASH WITH BUCKET_COUNT =Command-line changes
- -- Previously, `cockroach debug zip` would only print an informational message about a piece of data it was retrieving *after* the data was retrieved (or an error was observed). This patch changes it to print a message beforehand as well. This enables better troubleshooting of hanging queries. [#44342][#44342] -- `cockroach debug zip` now properly supports special characters in database and table names. [#44342][#44342] -- `cockroach debug zip` will now apply [the `--timeout` parameter](https://www.cockroachlabs.com/docs/v20.1/cockroach-node) to the SQL queries it performs (there was no timeout previously, causing `cockroach debug zip` to potentially hang). [#44342][#44342] -- `cockroach debug zip` is now able to tolerate more forms of cluster unavailability. Nonetheless, in case system ranges are unavailable, it is recommended to run `cockroach debug zip` towards each node address in turn to maximize the amount of useful data collected. [#44342][#44342] -- `cockroach debug zip` now includes secondary log files in the main log directory, for example the RocksDB logs. Log files in alternate log directories (e.g., `--sql-audit-dir`, if different from the main log directory) are not included. [#45200][#45200] - -Admin UI changes
- -- Changed Decommissioned Node History view to accommodate the case when there are no decommissioned nodes. [#44205][#44205] -- Changed styling of the Cluster Overview view. [#44212][#44212] -- Endpoint `/_status/registry/{node_id}` will now display status info about the jobs running on this `node_id`. [#45030][#45030] -- The "Log file list" endpoint now includes secondary log files in the main log directory, for example the RocksDB logs. Log files in alternate log directories (e.g., `--sql-audit-dir`, if different from the main log directory) are not included. [#45200][#45200] - -Bug fixes
- -- Fixed a bug where CockroachDB could return an internal error on the queries that return `INT` columns when the default integer size has been changed. [#44930][#44930] -- Fixed a bug where CockroachDB could crash when running `EXPLAIN (VEC)` in some edge cases. Now, an internal error is returned instead. [#44931][#44931] -- Fixed a bug where CockroachDB would return an internal error when the merge join operation was performed via the vectorized execution engine in a case when two sides of the join had comparable but different types in the equality columns (for example, `INT2` on the left and `INT4` on the right). [#44942][#44942] -- Fixed internal query errors in some cases involving negative limits. [#45009][#45009] -- Fixed a bug where the distinct operation in the row execution engine would fail to properly account for its memory usage, potentially leading to OOMs on large tables. [#45254][#45254] -- Correctly handle Avro byte datums when converting them to the expected string column families (such as `VARCHAR`, `CHAR`, etc.). [#45242][#45242] -- Fixed a potential error occurring when loading the movr dataset with a large number of rows in the promo codes column. [#45035][#45035] - -Performance improvements
- -- The [cost-based-optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer) now generates faster execution plans in some cases that involve `IN` / `NOT IN` with an empty tuple (or `= ANY` with an empty array). [#45170][#45170] - -Doc updates
- -- Added a [tutorial for developing and deploying a multi-region web application](https://www.cockroachlabs.com/docs/v20.1/multi-region-overview) with Flask, SQLAlchemy, CockroachCloud, and Google Cloud Platform. [#5732][#5732] -- Added a [Developer Guide](https://www.cockroachlabs.com/docs/v20.1/developer-guide-overview) that shows how to do common application development tasks in several languages: Go, Java, and Python. [#6362][#6362] -- Added [information about how to access the Admin UI on secure clusters](https://www.cockroachlabs.com/docs/v20.1/admin-ui-overview). [#6640][#6640] -- Overhauled the documentation on [authorization](https://www.cockroachlabs.com/docs/v20.1/authorization), [roles](https://www.cockroachlabs.com/docs/v20.1/create-role), and [grants](https://www.cockroachlabs.com/docs/v20.1/grant). [#6332][#6332] -- Added docs for [troubleshooting node liveness](https://www.cockroachlabs.com/docs/v20.1/cluster-setup-troubleshooting). [#6322][#6322] -- Added docs for online primary key changes with [`ALTER TABLE ... ALTER PRIMARY KEY`](https://www.cockroachlabs.com/docs/v20.1/alter-table). [#6513][#6513] -- Added a tutorial for using PonyORM with CockroachDB. [#6531][#6531] -- Added a [tutorial for using the jOOQ ORM with CockroachDB](https://www.cockroachlabs.com/docs/v20.1/build-a-java-app-with-cockroachdb-jooq). [#6684][#6684] - -Contributors
- -This release includes 122 merged PRs by 33 authors. -We would like to thank the following contributors from the CockroachDB community: - -- Andrii Vorobiov -- Artem Barger (first-time contributor) -- Jaewan Park -- abhishek20123g (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -In addition to various updates, enhancements, and bug fixes, this beta release includes the following major highlights: - -- **SELECT FOR UPDATE**: CockroachDB now supports [`SELECT FOR UPDATE`](https://www.cockroachlabs.com/docs/v20.1/select-for-update) for ordering transactions. Use `SELECT FOR UPDATE` to lock the rows returned by a [selection query](https://www.cockroachlabs.com/docs/v20.1/selection-queries), to control concurrent access to one or more rows of a table. -- **SQL savepoints**: CockroachDB now fully supports SQL [savepoints](https://www.cockroachlabs.com/docs/v20.1/savepoint). New syntax for savepoints includes `SAVEPOINTBackward-incompatible changes
- -- The [`GRANT`](https://www.cockroachlabs.com/docs/v20.1/grant) and [`REVOKE`](https://www.cockroachlabs.com/docs/v20.1/revoke) statements now require that the requesting user already have the target privileges themselves. For example, `GRANT SELECT ON t TO foo` requires that the requesting user already have the `SELECT` privilege on `t`. [#45697][#45697] {% comment %}doc{% endcomment %} -- During the upgrade process from 19.2 to 20.1, almost all schema changes will now be disallowed on 20.1 nodes until the upgrade has been finalized, as part of ensuring consistency while the cluster undergoes a significant, backward-incompatible change in how schema changes are executed. Attempting these schema changes will return an error to the client. [#45990][#45990] -- To ensure consistency for [schema changes](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes) throughout the upgrade process to 20.1, schema changes initiated in 19.2 now cannot be adopted, paused, or resumed from 20.1 nodes until an internal migration is run. [#46214][#46214] - -Security updates
- -Identity management changes
- -- All [role-based access control (RBAC) features](https://www.cockroachlabs.com/docs/v20.1/authorization#roles) (`CREATE ROLE`, [`ALTER ROLE`], `DROP ROLE`, `GRANT ROLE`, `REVOKE ROLE`) are now available to non-enterprise users. All RBAC features are now [BSL features](https://www.cockroachlabs.com/docs/v20.1/licensing-faqs). [#46042][#46042] -- [`USER`s](https://www.cockroachlabs.com/docs/v20.1/create-user) and [`ROLE`s](https://www.cockroachlabs.com/docs/v20.1/create-role) are now the same (which is PostgreSQL behavior). This means `CREATE`/`ALTER`/`DROP` `ROLE`/`USER` can be used interchangeably. [#44968][#44968] {% comment %}doc{% endcomment %} -- The validation rule for principal names was extended to support periods and thus allow domain name-like principals. For reference, the validation rule is currently the regular expression `^[p{Ll}0-9_][---p{Ll}0-9_.]*$`, and limited to a size of 63 UTF-8 bytes (larger usernames are rejected with an error); for comparison, PostgreSQL allows many more characters and truncates at 63 characters silently. [#45575][#45575] {% comment %}doc{% endcomment %} -- [Usernames](https://www.cockroachlabs.com/docs/v20.1/create-user) can now contain periods, for compatibility with certificate managers that require domain names to be used as usernames. [#45575][#45575] {% comment %}doc{% endcomment %} -- User and role principals can now be prevented from logging in using the `NOLOGIN` attribute, which can be set using the [`CREATE USER/ROLE`](https://www.cockroachlabs.com/docs/v20.1/create-user) or [`ALTER USER/ROLE`](https://www.cockroachlabs.com/docs/v20.1/alter-user). When using the [`CREATE ROLE`](https://www.cockroachlabs.com/docs/v20.1/create-user) syntax, `NOLOGIN` is enabled by default whereas when using [`CREATE USER`](https://www.cockroachlabs.com/docs/v20.1/create-role), it is not. [#45541][#45541] {% comment %}doc{% endcomment %} -- The `CREATEROLE` option can now be granted to users/roles using [`CREATE USER/ROLE`](https://www.cockroachlabs.com/docs/v20.1/create-user) or [`ALTER USER/ROLE`](https://www.cockroachlabs.com/docs/v20.1/alter-user). This delegates the permission to create additional roles. [#44232][#44232] {% comment %}doc{% endcomment %} -- Any [role](https://www.cockroachlabs.com/docs/v20.1/authorization#roles) created prior to v20.1 will be able to log into clusters started with `--insecure`, unless/until they are given the `NOLOGIN` attribute. For secure clusters, roles cannot log in by virtue of not having a password nor a client certificate. [#45541][#45541] {% comment %}doc{% endcomment %} - -Authentication changes
- -- CockroachDB now offers the ability to SQL client connection events (connection established and connection terminated) and SQL client authentication events (authentication method selection, authentication method application, authentication method result, and session termination) to a distinct `cockroach-auth.log` file in each node's main log directory. To enable SQL client connection logging, set the `server.auth_log.sql_connections.enabled` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings). To enable SQL client authentication event logging, set the new `server.auth_log.sql_sessions.enabled` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) cluster setting. Note that this feature is experimental; as such, the interface and output are subject to change. [#45193][#45193] {% comment %}doc{% endcomment %} -- The password field (used exclusively for password-based authentication) can now be configured to have an expiration date using the `VALID UNTIL` attribute, which can be set with [`ALTER USER/ROLE`](https://www.cockroachlabs.com/docs/v20.1/alter-user). Note that the attribute sets an expiration date for the password, not the user account. This is consistent with PostgreSQL. [#45541][#45541] {% comment %}doc{% endcomment %} -- Client and node certificates are now allowed to specify the principal in either the SubjectCommonName field or the SubjectAlternateNames field. Previously, the principal could only be specified in the SubjectCommonName field. This facilitates the use of Amazon Certificate Manager (ACM) and other Cloud-based certificate management tools. [#45819][#45819] - -Authorization changes
- -- Admin users can now [grant](https://www.cockroachlabs.com/docs/v20.1/grant) `ZONECONFIG` to non-admin users on specific SQL objects (databases/tables). When set, the user is authorized to modify that object's [zone configuration](https://www.cockroachlabs.com/docs/v20.1/configure-replication-zones) and decide data placement on specific nodes or groups thereof. [#45201][#45201] {% comment %}doc{% endcomment %} -- The [`GRANT`](https://www.cockroachlabs.com/docs/v20.1/grant) statement has been changed to be more like a capability-based system: it can only propagate privileges that the requesting user already has. Previously, it could be used to grant any other bit to any user, even to the requesting user. Note that the pseudo-privilege `ALL` includes `GRANT`, so `GRANT ALL`, in effect, preserves the previous behavior: it grants `GRANT` and every over privileges, so all privileges can be re-granted transitively. [#45697][#45697] {% comment %}doc{% endcomment %} -- It is now possible for operators to disable the use of implicit credentials when accessing external cloud storage services for various bulk operations (e.g, [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup), [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import), etc.). The use of implicit credentials can be disabled by using the `--external-io-disable-implicit-credentials` flag. [#45969][#45969] {% comment %}doc{% endcomment %} - -Security bug fixes
- -- All users can now *view* any comments on any object (bypassing other privileges), but modifying comments require write privilege on the target object. Previously, any user could modify any database/table/view/index comment via direct SQL updates to `system.comments`. This was unintended and a form of privilege escalation, and is now prevented. The privileges required for the [`COMMENT`](https://www.cockroachlabs.com/docs/v20.1/comment-on) statement, `pg_description`, `col_description()`, `obj_description()`, and `shobj_description()` are operating as in PostgreSQL and are unaffected by this change.[#45712][#45712] {% comment %}doc{% endcomment %} -- The `--external-io-dir=disabled` now applies to `nodelocal upload` requests. [#45858][#45858] {% comment %}doc{% endcomment %} -- The non-authenticated `/health` HTTP endpoint was previously exposing the private IP address of the node, which can be privileged information in some deployments. This has been corrected. Deployments using automation to retrieve a node build details and address details should use `/_status/details/local` instead and use a valid admin authentication cookie. [#45119][#45119] - -Enterprise edition changes
- -- [CDC](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) to cloud-storage sinks now supports optional `gzip` compression. [#45326][#45326] {% comment %}doc{% endcomment %} -- [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) can be re-run with the same destination path to automatically append an incremental backup to that path. [#45255][#45255] {% comment %}doc{% endcomment %} -- [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) now allows using `AS OF SYSTEM TIME` to pick a target backup from a larger list of incremental backups. [#45368][#45368] {% comment %}doc{% endcomment %} -- [Changefeeds](https://www.cockroachlabs.com/docs/v20.1/create-changefeed) now have new options to control the types of schema change events the changefeed should respond to (`schema_change_events`), and the behavior to take when such an event occurs (`schema_change_policy`). This functionality allows users to halt changefeeds upon schema changes or skip over the logical backfill that is performed by default. [#45652][#45652] {% comment %}doc{% endcomment %} -- Two new [`CHANGEFEED`](https://www.cockroachlabs.com/docs/v20.1/create-changefeed) options, `initial_scan` and `no_initial_scan`, have been added. The `initial_scan` can be used only if no cursor had been specified (indicating the desire to start the `CHANGEFEED` from `now()`). The new options allow clients to override this default behavior and create changefeeds from the present without an initial scan, or from a point in time with one. You cannot specify both options simultaneously. [#45663][#45663] {% comment %}doc{% endcomment %} -- [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) will no longer fail if the GC window for a table is exceeded while backing the table up. [#45859][#45859] {% comment %}doc{% endcomment %} -- Incremental [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) can quickly skip unchanged data, making frequent incremental backups 10-100x faster, depending on data size and frequency. [#46108][#46108] - -Storage changes
- -- Improved the ability of garbage collection to process ranges exhibiting abnormally large numbers of transaction records and/or abort span entries. [#45444][#45444] -- Improved a debug message that is printed when a range is unavailable (i.e., unable to accept writes). [#45580][#45580] -- The timing of garbage collection for historical data is defined by the `gc.ttlseconds` variable in the applicable [zone configuration](https://www.cockroachlabs.com/docs/v20.1/configure-replication-zones#replication-zone-variables). However, in practice, data is not garbage collected immediately after the TTL passes. The new `kv.gc_ttl.strict_enforcement` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) makes sure that `AS OF SYSTEM TIME` queries older than the TTL, but before GC has happened, return an error. [#45826][#45826] -- A bug in the range metrics collection would fail to correctly identify a range that had lost quorum, causing it to not be reported via the "unavailable ranges" metric. This is now fixed. [#45253][#45253] -- Range garbage collection will now trigger based on a large abort span, adding defense-in-depth against ranges growing large (and eventually unstable). [#45573][#45573] -- Fixed a bug that could cause requests to a quiesced range to hang in the KV [replication layer](https://www.cockroachlabs.com/docs/v20.1/architecture/replication-layer). This bug would cause the message "have been waiting ... for proposing" to appear. even though no loss of quorum occurred. [#46045][#46045] - -SQL changes
- -SQL language additions
- -- CockroachDB now supports string and byte array literals using the dollar-quoted notation, as documented [here](https://www.postgresql.org/docs/current/sql-syntax-lexical.html#SQL-SYNTAX-DOLLAR-QUOTING). [#44130][#44130] {% comment %}doc{% endcomment %} -- CockroachDB now supports expanding all columns of a tuple using the `.*` notation, for example: `SELECT (t).* FROM (SELECT (1,'b',2.3) AS t)`. This is a CockroachDB-specific extension. [#45609][#45609] {% comment %}doc{% endcomment %} -- CockroachDB now supports accessing the Nth column in a column with tuple type using the syntax `(...).@N`, for example: `SELECT (t).@2 FROM (SELECT (1,'b',2.3) AS t)`. This is a CockroachDB-specific extension. [#45609][#45609] {% comment %}doc{% endcomment %} -- Duplicate rows in the input to an [`INSERT..ON CONFLICT DO NOTHING`](https://www.cockroachlabs.com/docs/v20.1/insert) statement will now be ignored rather than triggering an error. [#45443][#45443] {% comment %}doc{% endcomment %} -- SQL [savepoints](https://www.cockroachlabs.com/docs/v20.1/savepoint) are now supported. `SAVEPOINTQuery planning changes
- -- CockroachDB previously allowed [`TIMESTAMP`/`TIMESTAMPTZ`](https://www.cockroachlabs.com/docs/v20.1/timestamp) and [`TIME`/`TIMETZ`](https://www.cockroachlabs.com/docs/v20.1/time) to be converted to `TIMESTAMP(0)`/`TIMESTAMPTZ(0)`, but this does not actually change any of the precision within it. CockroachDB now prohibits converting any precision of `TIMESTAMP`/`TIMESTAMPTZ`/`TIME`/`TIMETZ` to a lower precision value. [#45314][#45314] {% comment %}doc{% endcomment %} -- [Operators](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) on two [arrays](https://www.cockroachlabs.com/docs/v20.1/array) with different element types now fail at type-check time instead of evaluation time. [#45260][#45260] -- Improved the error message for the unsupported interaction between correlated subqueries and `WITH` clauses [#45227][#45227] -- [`UPSERT`](https://www.cockroachlabs.com/docs/v20.1/upsert) and [`INSERT..ON CONFLICT`](https://www.cockroachlabs.com/docs/v20.1/insert) statements now (occasionally) need to do an extra check to ensure that they never update the same row twice. This may adversely affect performance in cases where the [optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer) cannot statically prove the extra check is unnecessary. [#45372][#45372] -- The [optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer) now considers the likely number of rows an operator will need to provide, and might choose query plans based on this. In particular, the optimizer might prefer [lookup joins](https://www.cockroachlabs.com/docs/v20.1/joins) over alternatives in some situations where all rows of the join will probably not be needed. [#45604][#45604] -- [JSONB](https://www.cockroachlabs.com/docs/v20.1/jsonb) columns can now used in `GROUP BY` and `DISTINCT ON` clauses. [#45229][#45229] {% comment %}doc{% endcomment %} -- The [inverted index](https://www.cockroachlabs.com/docs/v20.1/inverted-indexes) implementation now supports indexing [array](https://www.cockroachlabs.com/docs/v20.1/array) columns. This permits accelerating containment queries (`@>` and `<@`) on array columns by adding an index to them. [#45157][#45157] {% comment %}doc{% endcomment %} -- [`EXPLAIN BUNDLE`](https://www.cockroachlabs.com/docs/v20.1/explain) can now be used to run a query and collect execution information in a support bundle, which can be downloaded via the Admin UI. [#45735][#45735] {% comment %}doc{% endcomment %} -- [`EXPLAIN BUNDLE`](https://www.cockroachlabs.com/docs/v20.1/explain) now works when the client driver prepares the statement. [#46111][#46111] -- Renamed `experimental_optimizer_foreign_keys` [session variable](https://www.cockroachlabs.com/docs/v20.1/set-vars) and `sql.defaults.optimizer_foreign_keys.enabled` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) to remove the experimental prefix. [#46174][#46174] -- Fixed the `"negative limit hint"` internal query error. [#45879][#45879] -- Fixed query errors in cases where a [CTE](https://www.cockroachlabs.com/docs/v20.1/common-table-expressions) was used inside a recursive CTE. [#45877][#45877] -- Fixed an internal error that could occur in the optimizer when a `WHERE` filter contained at least one [correlated subquery](https://www.cockroachlabs.com/docs/v20.1/subqueries#correlated-subqueries) and one non-correlated subquery. [#46153][#46153] -- Improvements in session settings reporting in the [`EXPLAIN (OPT,ENV)`](https://www.cockroachlabs.com/docs/v20.1/explain) output. [#46212][#46212] - -Execution changes
- -- The new `diagnostics.sql_stat_reset.interval` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) controls the rate at which SQL statement statistics are refreshed. Additionally, the setting `diagnostics.forced_stat_reset.interval` was renamed to `diagnostics.forced_sql_stat_reset_interval`. [#45082][#45082] {% comment %}doc{% endcomment %} -- [`UPDATE`](https://www.cockroachlabs.com/docs/v20.1/update) statements now acquire locks using the `FOR UPDATE` locking mode during their initial row scan, which improves performance for contended workloads. This behavior is configurable using the `enable_implicit_select_for_update` [session variable](https://www.cockroachlabs.com/docs/v20.1/set-vars) and the `sql.defaults.implicit_select_for_update.enabled` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings). [#45159][#45159] {% comment %}doc{% endcomment %} -- Hash joins and sorts are now run using the vectorized engine when `vectorize=auto` (default configuration). [#45582][#45582] {% comment %}doc{% endcomment %} -- CockroachDB now collects separate sets of metrics for usage of [`SAVEPOINT`](https://www.cockroachlabs.com/docs/v20.1/savepoint): one set for regular SQL savepoints and one set for uses dedicated to CockroachDB's client-side transaction retry protocol. [#45566][#45566] -- Vectorized distributed flows and disk spilling now support the [`INTERVAL`](https://www.cockroachlabs.com/docs/v20.1/interval) type. [#45776][#45776] {% comment %}doc{% endcomment %} -- Queries with [`MERGE` join](https://www.cockroachlabs.com/docs/v20.1/joins) can now run via the vectorized engine when `vectorize` is set to `auto`. [#45784][#45784] {% comment %}doc{% endcomment %} -- Hash aggregation is now supported in `vectorize=auto` mode. [#45832][#45832] {% comment %}doc{% endcomment %} -- Added telemetry reporting for usages of inverted and hash-sharded indexes. [#46060][#46060] -- The statement tag returned to the client upon success for [`CREATE USER`](https://www.cockroachlabs.com/docs/v20.1/create-user), [`ALTER USER`](https://www.cockroachlabs.com/docs/v20.1/alter-user), and [`DROP USER`](https://www.cockroachlabs.com/docs/v20.1/drop-user) now include the word "ROLE" instead of "USER", for compatibility with PostgreSQL. These three statements are now aliases for `CREATE ROLE`, `ALTER ROLE`, `DROP ROLE`. [#46042][#46042] -- `experimental_on` option for `vectorize` [session variable](https://www.cockroachlabs.com/docs/v20.1/set-vars) has been renamed to `on`. The only things that will not run with `auto`, but will run with `on`, are unordered [`DISTINCT`](https://www.cockroachlabs.com/docs/v20.1/select-clause#eliminate-duplicate-rows) and two [window functions](https://www.cockroachlabs.com/docs/v20.1/window-functions) (`percent_rank` and `cume_dist`). The two options are otherwise identical. [#46080][#46080] -- `NOTICE` commands can now be sent by CockroachDB servers using the Postgres client/server protocol. These notices will print when using the CockroachDB CLI. These notices can be disabled using the [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) `sql.notices.enabled = false`. [#45679][#45679] {% comment %}doc{% endcomment %} -- Fixed an internal error that could occur when `NULLIF` was called with one null argument. [#45354][#45354] -- Fix a bug where `EXPERIMENTAL SCRUB TABLE` on a timestamp/timestamptz key does not work. [#45410][#45410] -- Significantly reduced the amount of memory allocated while scanning tables with a large average row size. [#45323][#45323] -- Some vectorized execution plans that used [lookup joins](https://www.cockroachlabs.com/docs/v20.1/joins) with decimals would previously return incorrect results. This is now fixed. [#45536][#45536] -- Previously, drivers that did not truncate trailing zeroes for decimals in the binary format end up having inaccuracies of up to 10^4 during the decode step. Fixed the error by truncating the trailing zeroes as appropriate. This fixes known incorrect decoding cases with Postgres in Elixir. [#45613][#45613] -- Previously, an internal error could occur in CockroachDB when executing queries via the vectorized engine in queries that contained unordered synchronizers. This has been fixed. [#45690][#45690] -- Fixed a bug where the distinct operation on `ARRAY[NULL]` and `NULL` could sometimes return an incorrect result and omit some tuples. [#45229][#45229] -- Previously, CockroachDB could crash when computing [window functions](https://www.cockroachlabs.com/docs/v20.1/window-functions) with the `RANGE` mode of framing when one of the bounds was either `'offset PRECEDING'` or `'offset FOLLOWING'` and when there were `NULL` values in the single column from `ORDER BY` clause. Additionally, also in `RANGE` mode, bounds `'0 PRECEDING'` and `'0 FOLLOWING'` could be handled incorrectly. This is now fixed. [#44666][#44666] -- Verify column is now visible before accessing its datums. [#45801][#45801] -- Expected errors from the vectorized execution engine are no longer mistakenly annotated as unexpected errors. [#45673][#45673] -- Mixed type comparison or binary expressions that could have previously returned wrong results in the vectorized execution engine now fall back to using the row execution engine. [#45724][#45724] -- Fixed [decimal](https://www.cockroachlabs.com/docs/v20.1/decimal) rounding errors in the vectorized execution engine. [#45950][#45950] -- Fixed a bug where various [session variables](https://www.cockroachlabs.com/docs/v20.1/set-vars) whose value would display as "`on`" or "`off`" could not be set to the values "`on`" or "`off`", only `true` or `false`. [#46163][#46163] -- Fixed a bug that caused transactions that have performed [schema changes](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes) to deadlock after they restart. [#46170][#46170] - -Updates to schema change / DDL statements
- -- It is now possible to [create a table](https://www.cockroachlabs.com/docs/v20.1/create-table) and then add or alter a [primary key](https://www.cockroachlabs.com/docs/v20.1/primary-key) within the same transaction. [#46015][#46015] -- The [`ALTER TABLE .. ADD PRIMARY KEY ...`](https://www.cockroachlabs.com/docs/v20.1/alter-table) command can now be used when the target table has the default rowid [primary key](https://www.cockroachlabs.com/docs/v20.1/primary-key). [#45514][#45514] {% comment %}doc{% endcomment %} -- Fixed a bug where a table without a [primary key](https://www.cockroachlabs.com/docs/v20.1/primary-key) and a column named `rowid` would throw an error when being created. [#45507][#45507] -- The use of schema changes when a [primary key](https://www.cockroachlabs.com/docs/v20.1/primary-key) change is in progress is now disabled. This includes the following: (1) running a primary key change in a transaction and then starting another schema change in the same transaction, and (2) starting a primary key change on one connection and then starting a schema change on the same table on another connection while the initial primary key change is currently executing. [#45397][#45397] {% comment %}doc{% endcomment %} -- CockroachDB has now disabled [primary key](https://www.cockroachlabs.com/docs/v20.1/primary-key) changes when a concurrent schema change is executing on the same table, or if a schema change has been started on the same table in the current transaction. [#45513][#45513] {% comment %}doc{% endcomment %} -- You can now drop a [primary key](https://www.cockroachlabs.com/docs/v20.1/primary-key) as long as you add another primary key within the same [transaction](https://www.cockroachlabs.com/docs/v20.1/transactions). This feature is intended to be used when you do not want the existing primary key to be rewritten as a secondary index by [`ALTER PRIMARY KEY`](https://www.cockroachlabs.com/docs/v20.1/alter-primary-key). [#44511][#44511] {% comment %}doc{% endcomment %} -- The experimental variable gating around usages of online primary key changes is now removed. [#45753][#45753] {% comment %}doc{% endcomment %} -- Previously, when a [database was renamed](https://www.cockroachlabs.com/docs/v20.1/rename-database), any [table](https://www.cockroachlabs.com/docs/v20.1/create-table) referencing a [sequence](https://www.cockroachlabs.com/docs/v20.1/create-sequence) would be blocked from being able to rename the table. This is to block cases where if the table's reference to the sequence contains the database name, and the database name changes, we have no way of overwriting the table's reference to the sequence in the new database. However, if no database name is included in the sequence reference, we should continue to allow the database to rename, as is implemented with this change. [#45502][#45502] {% comment %}doc{% endcomment %} -- Previously, [renaming a database](https://www.cockroachlabs.com/docs/v20.1/rename-database) with dependent [views](https://www.cockroachlabs.com/docs/v20.1/views) returned a misleading error message that implies it was a dependent view on a dependent table. Now the error message generically says `cannot rename relation ... as it depends on relation ...` instead. [#45427][#45427] -- Long-running [transactions](https://www.cockroachlabs.com/docs/v20.1/transactions) which attempt to [`TRUNCATE`](https://www.cockroachlabs.com/docs/v20.1/truncate) can now be pushed and will commit in cases where they previously could fail or retry forever. [#44091][#44091] -- It is now possible to create [inverted indexes](https://www.cockroachlabs.com/docs/v20.1/inverted-indexes) on columns whose names are mixed-case. [#45621][#45621] - -Updates to Bulk I/O statements
- -- Improved error messages when [importing MySQL dump](https://www.cockroachlabs.com/docs/v20.1/migrate-from-mysql) data. [#45958][#45958] -- `nodelocal://` URIs now require a node ID be specified in the hostname field. The special node ID of `'self'` is equivalent to the old behavior of when the node ID was unspecified. [#45764][#45764] {% comment %}doc{% endcomment %} -- Fixed cases where target column specifications in [`IMPORT INTO`](https://www.cockroachlabs.com/docs/v20.1/import-into) were ignored. [#45747][#45747] -- `IMPORT` now correctly handles columns named with reserved keywords and/or other special characters. [#45944][#45944] -- Google storage client is now resilient to transient connection errors. [#46000][#46000] -- The creation of a database and table between incremental cluster backups is now allowed. [#46066][#46066] -- Better error reporting when importing data. [#46165][#46165] - -Changes to background job management
- -- Schema changes are now scheduled and run fully like other [jobs](https://www.cockroachlabs.com/docs/v20.1/show-jobs): they now can be [canceled](https://www.cockroachlabs.com/docs/v20.1/cancel-job), [paused](https://www.cockroachlabs.com/docs/v20.1/pause-job), and [resumed](https://www.cockroachlabs.com/docs/v20.1/resume-job). Some other UI differences come with this implementation change; notably, all schema changes now have an associated job, failed schema changes are now rolled back within the "Reverting" phase of the same job, and GC for dropped indexes and tables is deferred to a later job. [#45870][#45870] -- Non-running [`jobs`](https://www.cockroachlabs.com/docs/v20.1/show-jobs) are now considered for adoption in randomized order instead of in a determistic order by creation time, to avoid potential deadlocks when schema change jobs need to execute in a specific order. This is a preemptive change, not a bug fix, but it affects all jobs. [#45870][#45870] {% comment %}doc{% endcomment %} -- On new clusters, the internal `system.jobs` table now uses the default `zoneconfig` and `TTL` (25h). [#45767][#45767] {% comment %}doc{% endcomment %} -- The cleanup job spawned by [`ALTER .. PRIMARY KEY`](https://www.cockroachlabs.com/docs/v20.1/alter-primary-key) in some cases cannot be cancelled. [#45595][#45595] {% comment %}doc{% endcomment %} -- Introduced a temporary table cleanup job that runs once every periodically per cluster. It removes any temporary schemas and their related objects that did not get removed cleanly when the connection closed. This period can be changed by the [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) `sql.temp_object_cleaner.cleanup_interval`, which defaults to 30 minutes. [#45669][#45669] {% comment %}doc{% endcomment %} -- Previously, after deleting an index, table, or database, the relevant schema change job would change its running status to waiting for GC TTL. The schema change and the GC process are now decoupled into two jobs. [#45962][#45962] -- Fixed a bug where, in some rare cases, a job was not [cancellable](https://www.cockroachlabs.com/docs/v20.1/cancel-job) when in state "Reverting". [#45320][#45320] -- When considering if a job should be orphaned, CockroachDB use to take the conservative approach when a descriptor ID pointing to non-existent descriptor was found. This caused jobs to hang forever and be garbage collected. CockroachDB now disregards these IDs when considering if a job has still work to do. [#45353][#45353] -- Logs emitted from [jobs](https://www.cockroachlabs.com/docs/v20.1/show-jobs) are now tagged with the job ID to improve visibility and aid debugging. [#45728][#45728] -- [`IMPORT INTO`](https://www.cockroachlabs.com/docs/v20.1/import-into) jobs which are canceled or fail can no longer get stuck in an unrecoverable state if data from the previous state of the table had expired relative to the GC TTL. [#44739][#44739] -- [`CHANGEFEED`](https://www.cockroachlabs.com/docs/v20.1/create-changefeed) jobs that take a long time to perform backfills will no longer encounter failures due to garbage collection, so long as they begin before the data has expired. [#45778][#45778] - -Updates to APIs and introspection
- -- Telemetry reporting has been added for the commands [`SHOW INDEXES`](https://www.cockroachlabs.com/docs/v20.1/show-index), [`SHOW QUERIES`](https://www.cockroachlabs.com/docs/v20.1/show-queries), [`SHOW JOBS`](https://www.cockroachlabs.com/docs/v20.1/show-jobs), and [`SHOW CONSTRAINTS`](https://www.cockroachlabs.com/docs/v20.1/show-constraints). [#45897][#45897] -- [`SHOW USERS`](https://www.cockroachlabs.com/docs/v20.1/show-users) and [`SHOW ROLES`](https://www.cockroachlabs.com/docs/v20.1/show-roles) are now the same, as `USERS` is now an alias for `ROLES`. `SHOW USERS` and `SHOW ROLES` now match PostgreSQL `du` command. `SHOW ROLES` now displays three columns: `username`, `options`, and `member_of`. [#45827][#45827] -- HTTP endpoints now report status `403 (Forbidden)` instead of `500 (Internal server error)` when the authenticated user has insufficient privileges to use the endpoint. [#45325][#45325] {% comment %}doc{% endcomment %} -- The end point `/_status/job/{job_id}` will now display status info about a job. [#45094][#45094] {% comment %}doc{% endcomment %} -- The pprof endpoints now allow downloading the binary profiles. To do so, attach `?download=true` to the URL. [#45790][#45790] {% comment %}doc{% endcomment %} -- Improved the debuggability of C++-level issues by providing access to thread stack traces via a new `/debug/threads` endpoint, which is exposed on the Admin UI advanced debug page. Now include thread stack traces in the info collected by `debug zip`. Thread stack traces are currently only available on Linux. [#45321][#45321] {% comment %}doc{% endcomment %} -- Accesses to `/health` using a non-root authentication token no longer hang when a node is currently under load, or if a system range is unavailable. [#45119][#45119] -- Statement diagnostics traces now contain processor statistics. [#46132][#46132] - -Command-line changes
- -Changes to operational workflows
- -- Hostnames from the `cockroach start --join` flag can now be resolved as SRV record. This simplifies cluster deployment in Kubernetes. [#45815][#45815] {% comment %}doc{% endcomment %} -- The `--decommission` flag for [`cockroach quit`](https://www.cockroachlabs.com/docs/v20.1/cockroach-quit) is now deprecated. It will be removed altogether in a next stable release. Deployments should use [`cockroach node decommission`](https://www.cockroachlabs.com/docs/v20.1/cockroach-node) followed by either `cockroach quit` or an equivalent form of server shut down. [#45903][#45903] {% comment %}doc{% endcomment %} -- The `--socket` flag for [`cockroach start`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start) is now deprecated in favor of `--socket-dir`. CockroachDB now automatically chooses a name for the socket in the specified directory based on the configured port number. `--socket` will be removed in a later version. [#45931][#45931] {% comment %}doc{% endcomment %} -- Added the `--cert-principal-map` flag to [`cockroach start`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start), which specifies a comma-separated list of `cert-principal`:`db-principal` mappings that map the principals found in certificates to DB principals. This allows the usage of "node" and "root" certificates where the common name contains dots or a host name, which allows such certificates to be generated by certificate authorities that place restrictions on the contents of the common name field. [#45819][#45819] - -Configuration changes
- -- Added a new `default` option for the `--storage-engine` flag that respects the engine used last. [#45512][#45512] {% comment %}doc{% endcomment %} - -Usability improvements
- -- Some CLI [commands](https://www.cockroachlabs.com/docs/v20.1/cockroach-commands) now provide more details and/or a hint when they encounter an error. [#45575][#45575] {% comment %}doc{% endcomment %} -- CockroachDB now refuses to start if named time zones are not properly configured. It is possible to override this behavior for testing purposes, with the understanding that doing so will cause incorrect SQL results and other inconsistencies, using the environment variable `COCKROACH_INCONSISTENT_TIME_ZONES`. [#45640][#45640] {% comment %}doc{% endcomment %} -- The [`cockroach sql`](https://www.cockroachlabs.com/docs/v20.1/cockroach-sql) and [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) client commands now display out-of-band server notices at the end of execution. [#46144][#46144] [#46124][#46124] -- When some result rows have already been received from the server when an error is encountered, the [CockroachDB SQL shell](https://www.cockroachlabs.com/docs/v20.1/cockroach-sql) now presents both the result rows and the error in the output, regardless of the selected table formatter. Previously, only the error was reported with some formatters, or both with other formatters. [#45872][#45872] {% comment %}doc{% endcomment %} -- Added the flag `--disable-demo-license` to provide another option to disable [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) from attempting to acquire a demo license. [#46126][#46126] -- The parameter `--set` for [`cockroach sql`](https://www.cockroachlabs.com/docs/v20.1/cockroach-sql) and [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) is now able to override all client-side options, as advertised. [#46118][#46118] -- Fixed a bug that caused `cockroach demo -e` to display a `connection refused` error. [#46126][#46126] - -Change to troubleshooting facilities
- -- The [`cockroach debug zip`](https://www.cockroachlabs.com/docs/v20.1/cockroach-debug-zip) output now contains hex representation of marshaled jobs payload and progress as well table descriptors. This allows you to copy this string and unmarshal it when debugging. [#45721][#45721] {% comment %}doc{% endcomment %} -- CockroachDB will now dump the stacks of all goroutines upon receiving `SIGQUIT` prior to terminating. This feature is intended for use while troubleshooting misbehaving nodes. [#36378][#36378] {% comment %}doc{% endcomment %} - -Admin UI changes
- -- Removed mention of RocksDB from the Read Amplification, SSTables, Compactions/Flushes, and Compaction Queue graphs. [#45398][#45398] -- The display options are now saved separately for each authenticated user. **Note:** When upgrading to a version with this change, all current display customizations for admin users are lost. [#45127][#45127] {% comment %}doc{% endcomment %} -- Customizations of the Admin UI are again properly saved across sessions. [#45127][#45127] -- Refactored redux data flow in enqueue range. [#45667][#45667] -- Increased enqueue range timeout to an hour to prevent operations from timing out before completion. [#45667][#45667] -- The Admin UI now reports a clearer message when a non-admin user uses an admin-only feature. [#45122][#45122] -- Added the Statement Diagnostics History page. [#45799][#45799] -- You can now access the Activate Diagnostics dialog from the [Statements page](https://www.cockroachlabs.com/docs/v20.1/admin-ui-statements-page), through the **Activate** link. [#45799][#45799] {% comment %}doc{% endcomment %} -- Added a Release Notes subscription form on the [Cluster Overview page](https://www.cockroachlabs.com/docs/v20.1/admin-ui-cluster-overview-page). [#45143][#45143] -- The jobs status filter now includes "running", which was previously omitted by mistake. [#45937][#45937] - -Performance improvements
- -- [Importing an Avro file](https://www.cockroachlabs.com/docs/v20.1/migrate-from-avro) is now faster. [#45269][#45269] -- Improved the execution plans of [foreign key](https://www.cockroachlabs.com/docs/v20.1/foreign-key) checks for [`UPSERT`](https://www.cockroachlabs.com/docs/v20.1/upsert) and [`INSERT .. ON CONFLICT`](https://www.cockroachlabs.com/docs/v20.1/insert) in some cases (in particular multi-region). [#45520][#45520] -- [Importing](https://www.cockroachlabs.com/docs/v20.1/import) delimited data now has improved throughput. [#45543][#45543] -- Improved the selectivity estimation of some predicates containing `OR`, leading to better plan selection by the [optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer). [#45732][#45732] -- Improved cardinality estimation in the [optimizer](https://www.cockroachlabs.com/docs/v20.1/cost-based-optimizer) for relations with a small number of rows. This leads to the optimizer choosing a better query plan in some cases. [#45771][#45771] -- `crdb_internal.jobs` now loads less data into memory. [#45914][#45914] - -Doc updates
- -- Upgraded the search on the docs site. [#6692][#6692] -- Added docs for `--storage-engine` flag on [node start](https://www.cockroachlabs.com/docs/v20.1/cockroach-start), which can be `pebble`, `rocksdb`, or `default`, which makes the `--storage-engine` flag sticky for future runs when no engine is specified. [#6769][#6769] -- Added examples of `COMMENT ON TABLE` in `SHOW CREATE TABLE` output to [`COMMENT ON`](https://www.cockroachlabs.com/docs/v20.1/comment-on), [`SHOW TABLES`](https://www.cockroachlabs.com/docs/v20.1/show-tables), and [`SHOW CREATE`](https://www.cockroachlabs.com/docs/v20.1/show-create). [#6789][#6789] -- Added the "Duplicate Indexes" Youtube video to the [Duplicate Indexes Topology doc](https://www.cockroachlabs.com/docs/v20.1/topology-duplicate-indexes). [#6796][#6796] -- Updated the [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) doc to include new flags. [#6841][#6841] - -Contributors
- -This release includes 385 merged PRs by 42 authors. -We would like to thank the following contributors from the CockroachDB community: - -- Andrii Vorobiov -- Artem Barger -- Damien Hollis (first-time contributor) -- Jaewan Park -- Ziheng Liu (first-time contributor) -- pohzipohzi (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -Security updates
- -- The `admin` role is now required to use the new [`cockroach nodelocal upload`](https://www.cockroachlabs.com/docs/v20.1/cockroach-nodelocal-upload) functionality. [#46265][#46265] - -Enterprise edition changes
- -- Incremental [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) can now quickly skip unchanged data. This makes frequent incremental backups 10-100x faster depending on data size and frequency. [#46390][#46390] - -SQL language changes
- -- Added `get_bits()` and `set_bit()` [builtin functions](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) for bits. [#45957][#45957] -- Modified the `get_bits()` and `set_bit()` [builtin functions](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) to support [byte array](https://www.cockroachlabs.com/docs/v20.1/sql-constants#byte-array-literals). [#46380][#46380] -- Arrays can now be compared using the `<`, `<=`, `>`, and `>=` operations. [#46254][#46254] -- [`EXPLAIN BUNDLE`](https://www.cockroachlabs.com/docs/v20.1/explain) now contains distsql diagrams. [#46225][#46225] -- Previously, when creating a non-partitioned index on a partitioned table with the `sql_safe_updates` [session variable](https://www.cockroachlabs.com/docs/v20.1/set-vars) set to `true`, CockroachDB would error out. CockroachDB now sends a NOTICE stating that creating a non-partitioned index on a partitioned table is not performant. [#46223][#46223] -- Added new internal tables `crdb_internal.node_transactions` and `crdb_internal.cluster_transactions` that contain some metadata about active user transactions. [#46206][#46206] -- Added the column `txn_id` to the `crdb_internal.node_queries` and `crdb_internal.cluster_queries` tables. These fields represent the transaction ID of each query in each row. [#46206][#46206] -- Columns in the process of being added to or removed from a table are now always set to their default or computed value if another transaction concurrently [`INSERT`](https://www.cockroachlabs.com/docs/v20.1/insert)s, [`UPDATE`](https://www.cockroachlabs.com/docs/v20.1/update)s, or [`UPSERT`](https://www.cockroachlabs.com/docs/v20.1/upsert)s a row. This fixes an issue where a column being backfilled would not get properly set by concurrent transactions. [#46285][#46285] -- [`ROLLBACK TO SAVEPOINT`](https://www.cockroachlabs.com/docs/v20.1/rollback-transaction) (for either regular savepoints or "restart savepoints" defined with `cockroach_restart`) now causes a "feature not supported" error after a DDL statement in a HIGH PRIORITY transaction, in order to avoid a transaction deadlock. See issue [#46414][#46414] for details. [#46415][#46415] -- Added support for the `stddev_samp` aggregate [builtin function](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators), which is the same as `stddev` (according to PostgreSQL documentation, the latter is actually the historical alias of the former). [#46279][#46279] - -Command-line changes
- -- Ensured the correct error messages are shown to the user when using [`cockroach nodelocal upload`](https://www.cockroachlabs.com/docs/v20.1/cockroach-nodelocal-upload). [#46311][#46311] - -Bug fixes
- -- Fixed a crash when [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import)ing a table without a table definition. [#46193][#46193] -- Added support for queries with qualified stars that refer to tables in outer scopes. [#46233][#46233] -- Fixed an incorrect "no data source matches prefix" error in some cases involving subqueries that use views. [#46226][#46226] -- Previously, the `experimental_strftime` and `experimental_strptime` [builtin functions](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) used the non-POSIX standard `%f` for nanosecond display. However, as CockroachDB only supports up to microsecond precision and [Python's `strftime` has `%f` to microsecond](https://docs.python.org/3.9/library/datetime.html#strftime-strptime-behavior), we have similarly switched %f to use microsecond instead of nanosecond precision. [#46263][#46263] -- Added a check that detects invalid sequence numbers in the RocksDB write-ahead log and returns an error during node startup instead of applying the invalid log entries. [#46328][#46328] -- [Follower reads](https://www.cockroachlabs.com/docs/v20.1/follower-reads) that hit intents no longer have a chance of entering an infinite loop. This bug was present in earlier versions of the v20.1 release. [#46234][#46234] -- Fixed an internal error that could occur when an aggregate inside the right-hand side of a `LATERAL` [join](https://www.cockroachlabs.com/docs/v20.1/joins) was scoped at the level of the left-hand side. [#46227][#46227] -- Fixed an error that incorrectly occurred when an aggregate was used inside the `WHERE` or `ON` clause of a [subquery](https://www.cockroachlabs.com/docs/v20.1/subqueries) but was scoped at an outer level of the query. [#46227][#46227] -- Reverted performance improvements to incremental [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup)s until a potential correctness issue is addressed. [#46385][#46385] -- [CDC](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) no longer combines with long running transactions to trigger an assertion. Previously, this could crash a server if the right sequence of events occurred. This was typically rare, but was much more common when CDC was in use. [#46391][#46391] -- Fixed a race in the [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution). [#46360][#46360] -- Fixed a rare bug causing transactions that have performed schema changes to deadlock after they restart. [#46384][#46384] - -Doc updates
- -- Added docs for [`cockroach nodelocal upload`](https://www.cockroachlabs.com/docs/v20.1/cockroach-nodelocal-upload), which uploads a file to the external IO directory on a node's (the gateway node, by default) local file system. [#6871][#6871] -- Added [guidance](https://www.cockroachlabs.com/docs/v20.1/create-table#create-a-table-with-a-hash-sharded-primary-index) on using [hash-sharded indexes](https://www.cockroachlabs.com/docs/v20.1/indexes#hash-sharded-indexes). [#6820][#6820] -- Updated [production checklist](https://www.cockroachlabs.com/docs/v20.1/recommended-production-settings#azure) and [Azure deployment guides](https://www.cockroachlabs.com/docs/v20.1/deploy-cockroachdb-on-microsoft-azure) to recommend compute-optimize F-series VMs in Azure deployments. [#7005][#7005] - -Contributors
- -This release includes 46 merged PRs by 20 authors. -We would like to thank the following contributors from the CockroachDB community: - -- Amit Sadaphule (first-time contributor) -- Andrii Vorobiov -- Marcus Gartner (first-time contributor, CockroachDB team member) -- abhishek20123g - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -Security updates
- -- The new `--unencrypted-localhost-http` flag for [`cockroach start`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start) and [`cockroach start-single-node`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start-single-node) forces the HTTP listener to bind to `localhost` addresses only and disables the TLS protocol. In secure clusters, this makes the Admin UI reachable with an `http://` URL without requiring certificate or CA setup. [#46472][#46472] {% comment %}doc{% endcomment %} - -General changes
- -- Transactions reading a lot of data behave better when exceeding the memory limit set by the `kv.transaction.max_refresh_spans_bytes` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings). Such transactions now attempt to resolve the conflicts they run into instead of being forced to always retry. Increasing `kv.transaction.max_refresh_spans_bytes` should no longer be necessary for most workloads. [#46803][#46803] -- Before [upgrading from v19.2 to v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version), it is best practice to make sure there are no schema changes in progress. However, if any are still running when the upgrade is started, note that they will stop making progress during the upgrade and will run to completion once the upgrade has been finalized. [#47073][#47073] - -Enterprise edition changes
- -- The new `protect_data_from_gc_on_pause` [`CHANGEFEED` option](https://www.cockroachlabs.com/docs/v20.1/create-changefeed#options) ensures that the data needed to resume a `CHANGEFEED` is not garbage collected. [#46345][#46345] {% comment %}doc{% endcomment %} -- [`BACKUP`s](https://www.cockroachlabs.com/docs/v20.1/backup) and [`RESTORE`s](https://www.cockroachlabs.com/docs/v20.1/restore) now collect some [anonymous telemetry](https://www.cockroachlabs.com/docs/v20.1/diagnostics-reporting) on throughput and feature usage. [#46755][#46755] -- [`SHOW BACKUP`](https://www.cockroachlabs.com/docs/v20.1/show-backup) now shows whether a `BACKUP` is a cluster backup or not. [#46768][#46768] {% comment %}doc{% endcomment %} -- [`SHOW BACKUP`](https://www.cockroachlabs.com/docs/v20.1/show-backup) now shows the privileges assigned to tables and databases in a backup and, if the `WITH privileges` option is specified, lists which users and roles had which privileges. [#46853][#46853] {% comment %}doc{% endcomment %} -- [Incremental backups](https://www.cockroachlabs.com/docs/v20.1/backup#incremental-backups) and [restores](https://www.cockroachlabs.com/docs/v20.1/restore#restore-from-incremental-backups) using HTTP storage now require explicitly specifying incremental storage locations. [#46967][#46967] {% comment %}doc{% endcomment %} -- The new, appending [incremental backup syntax](https://www.cockroachlabs.com/docs/v20.1/backup#create-incremental-backups) does not allow converting a [cluster backup](https://www.cockroachlabs.com/docs/v20.1/backup#backup-a-cluster) to a specific table or database backup. [#46966][#46966] {% comment %}doc{% endcomment %} - -SQL language changes
- -- Outer columns (columns in a subquery that reference a higher scope) can now be used in the `SELECT` list of an aggregation or grouping expression without explicitly including them in the `GROUP BY` list, for improved Postgres compatibility. [#46417][#46417] {% comment %}doc{% endcomment %} -- Renamed the `EXPLAIN BUNDLE` statement to `EXPLAIN ANALYZE (DEBUG)`. [#46534][#46534] {% comment %}doc{% endcomment %} -- The `EXPLAIN ANALYZE (DEBUG)` statement now contains all the information available via `EXPLAIN (OPT,ENV)`. [#46441][#46441] {% comment %}doc{% endcomment %} -- The `length()`, `octet_length()` and `bit_length()` [built-in functions](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) are now supported on `BIT` and `VARBIT`. [#46524][#46524] {% comment %}doc{% endcomment %} -- The [`EXPLAIN ANALYZE`](https://www.cockroachlabs.com/docs/v20.1/explain-analyze) response now includes memory and disk usage details and omits allocation stats if they are zero. [#46316][#46316] {% comment %}doc{% endcomment %} -- The `CREATE TEMPORARY TABLE` statement now supports the `ON COMMIT` syntax. [#46594][#46594] {% comment %}doc{% endcomment %} -- The [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import) statement now records additional [anonymous telemetry](https://www.cockroachlabs.com/docs/v20.1/diagnostics-reporting) about its performance and reliability. [#46763][#46763] -- `CREATE INDEX CONCURRENTLY` and `DROP INDEX CONCURRENTLY` are now supported as no-ops, as all indexes are created concurrently. [#46802][#46802] {% comment %}doc{% endcomment %} -- The type checking code now prefers aggregate overloads with string inputs if there are multiple possible candidates due to arguments of unknown type. [#46898][#46898] -- Added an unimplemented error when attempting to `ADD CONSTRAINT` with the `EXCLUDE USING` syntax. [#46909][#46909] -- Added support for `CREATE INDEX .... INCLUDE (col1, col2, ...)`, which is an alias that PostgreSQL uses that is analogous to CockroachDB's `STORING (col1, col2, ...)` syntax. [#46909][#46909] -- Added support for parsing the `REINDEX` syntax, which results in an unimplemented error that explains that `REINDEX`ing is not required in CockroachDB. [#46909][#46909] -- The [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) now only runs queries with streaming operators. To enable vectorized execution for buffering operators, use `SET vectorize=on`. [#46925][#46925] {% comment %}doc{% endcomment %} -- The [`EXPLAIN`](https://www.cockroachlabs.com/docs/v20.1/explain) response now shows `SPANS | FULL SCAN` for full table scans and `SPANS | LIMITED SCAN` if there is a limit. Previously, both cases would return `SPANS | ALL`. [#47013][#47013] {% comment %}doc{% endcomment %} -- The `CREATE ROLE`/`ALTER ROLE`/`DROP ROLE` results no longer show the rows affected, as this number could be misleading. [#46819][#46819] -- Added a hint to use `ALTER ROLE` when trying to `GRANT` a role option directly to a user using the `GRANT ROLE` syntax. [#46819][#46819] -- Improved the error message for `ALTER COLUMN ... SET DATA TYPE` for data type conversions that involve overwriting existing values. [#47170][#47170] - -Command-line changes
- -- The `cockroach` commands that internally use SQL, including [`cockroach sql`](https://www.cockroachlabs.com/docs/v20.1/cockroach-sql) and [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo), now can connect to a server using a unix datagram socket. The syntax for this is `--url 'postgres://user@?host=/path/to/directory?port=NNNN'`. [#47007][#47007] {% comment %}doc{% endcomment %} -- The [`cockroach workload`](https://www.cockroachlabs.com/docs/v20.1/cockroach-workload) command now sets its `application_name` based on the chosen workload. [#46546][#46546] {% comment %}doc{% endcomment %} -- The [`cockroach debug zip`](https://www.cockroachlabs.com/docs/v20.1/cockroach-debug-zip) command now creates valid zip files even if some of its requests encounter an error. [#46634][#46634] -- The [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) command now displays a TCP-based connection URL and unix datagram socket for each node of a demo cluster. [#46935][#46935] {% comment %}doc{% endcomment %} -- It is now possible to pre-configure the secure mode of [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) using the `COCKROACH_INSECURE` environment variable like other client commands. [#46959][#46959] {% comment %}doc{% endcomment %} -- When running [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) in secure mode, the generated SQL URL now embeds the password so that commands using this URL can run without a request for password. [#47007][#47007] {% comment %}doc{% endcomment %} -- The SQL URL generated by [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) no longer requires TLS client certificates in particular directory locations. [#47007][#47007] {% comment %}doc{% endcomment %} -- The new experimental client-side command `demo ls` for [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) displays the connection parameters for every node in a demo cluster. [#47007][#47007] {% comment %}doc{% endcomment %} -- The client-side commands specific to [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo), starting with `demo`, are now advertised in the output of `?`. Note that this feature is currently experimental. [#47007][#47007] {% comment %}doc{% endcomment %} - -Admin UI changes
- -- The ALL filter on the Statements page now excludes internal statements. [#45646][#45646] -- Tooltips showing statements and jobs are now limited in size for very long statements. [#46982][#46982] -- The default timescale on metrics pages is now 10 minutes. Previously, the timescale defaulted to the age of the longest running node. [#46980][#46980] -- Improved tooltips for existing capacity and storage metrics. [#46987][#46987] -- Added analytics tracking for table sorts, searches and diagnostics activation on the Statements page, and navigation on the Statement Details page. [#47003][#47003] -- The download link for statement diagnostics now points to the bundle zip file. [#47016][#47016] -- Removed the Statements tab from the Databases > Table Details page. [#47102][#47102] -- Cleaned up barcharts on the Statements page. [#47129][#47129] - -Bug fixes
- -- Fixed an Admin UI bug where sort columns were only being applied per-page instead of for the entire multi-page list of statements [#46978][#46978] -- Fixed a performance bug where truncate would take 2*num columns + 2*num indexes round trips. This could lead to slow truncate performance in distributed clusters. [#46334][#46334] -- It is no longer possible to inject stats within an explicit transaction. [#46567][#46567] -- Casting a bit array to a bigger varbit array no longer adds extra 0 padding at the end. [#46532][#46532] -- Fixed a bug where `pg_catalog.pg_indexes` showed the wrong index definition for inverted indexes. [#46527][#46527] -- Fixed incorrect query results in some corner cases involving variance/stddev/corr. [#46436][#46436] -- Fixed an internal error or incorrect evaluation of check constraints in certain cases involving `UPSERT` and foreign key checks. [#46409][#46409] -- `cockroach debug zip` now properly collects heap profiles. [#46469][#46469] -- The goroutine dump facility now functions properly when logging to files is disabled, e.g., via `--log-dir=` or `--logtostderr`. [#46469][#46469] -- Fixed an internal error that could occur during planning for some queries with a join and negative `LIMIT`. [#46440][#46440] -- Fixed a bug where the vectorized engine could sometimes give an incorrect result when reading from interleaved parents or children. [#46456][#46456] -- Fixed a bug where the vectorized engine would throw an internal error when executing a query that utilized an inverted index. [#46267][#46267] -- Fixed a bug where operations on an index that contained a collated string in descending order would fail. [#46570][#46570] -- Fixed a bug with `SET TIME ZONE`, where a string prefixed with `UTC` or `GMT` and with time zones with colons had it's offset inverted the wrong way. [#46510][#46510] -- CockroachDB no longer incorrectly accounts for some RAM usage when computing aggregate functions. [#46545][#46545] -- `SHOW INDEXES ... WITH COMMENT` no longer shows duplicate rows for certain tables if indexes are identically named. [#46621][#46621] -- Fixed an internal error that could happen during planning when a column with a histogram was filtered with a predicate of a different data type. [#46552][#46552] -- Scans that lock rows (via `FOR UPDATE`) are no longer elided when the results are unused. [#46676][#46676] -- Fixed a bug (introduced in v20.1.0-beta.3) in the new schema change GC job implementation which would cause the execution of GC jobs to be incorrectly delayed in the presence of other table descriptor updates. [#46691][#46691] -- Fixed a bug with distinct aggregations on `JSONB` columns. [#46711][#46711] -- Fixed a rare bug causing the assertion failure "caller violated contract: discovered non-conflicting lock". [#46744][#46744] -- Ensured that index and table GC happen closer to their GC deadline. [#46743][#46743] -- Statement diagnostics created through `EXPLAIN ANALYZE (DEBUG)` now show up in the UI page. [#46804][#46804] -- Benign "outbox next" errors are now only logged when log verbosity is set to 1 or greater. [#46838][#46838] -- Failed or canceled `IMPORT`s now properly clean up partially imported data. [#46856][#46856] -- Failed or canceled `RESTORE`s now properly clean up partially imported data. [#46855][#46855] -- Fixed a rare bug causing errors to be returned for successfully committed transactions. The most common error message was "TransactionStatusError: already committed". [#46848][#46848] -- The "insecure cluster" indicator is once again displayed at the top right of Admin UI for insecure clusters. [#46865][#46865] -- Fixed a rare assertion failure that contained the text "existing lock cannot be acquired by different transaction". This assertion was only present in earlier v20.1 releases and not in any earlier releases. [#46896][#46896] -- Fixed an incorrect query result that could occur when a scalar aggregate was called with a null input. [#46898][#46898] -- Fixed incorrect result with count(*) when grouping on constant columns. [#46891][#46891] -- `cockroach demo` now properly cleans up its temporary files if the background license acquisition fails. [#47007][#47007] -- Tooltips for statement diagnostics are now only shown on hover. [#46995][#46995] -- Fixed a bug when queries with projections of only `INT2` and/or `INT4` columns were executed via the vectorized engine. [#46977][#46977] -- CockroachDB no longer considers a non-`NULL` value from an interleaved parent table to be `NULL` when the interleaved child has a `NULL` value in the row with the corresponding index key. [#47103][#47103] -- Incremental, full-cluster `BACKUP`s with revision history are no longer disallowed in some cases where system tables have changed. [#47132][#47132] -- Fixed a bug when adding a self-referencing foreign key constraint in the same transaction that creates a table. [#47128][#47128] -- Change data capture no longer combines with long running transactions to trigger an assertion with the text "lock timestamp regression". [#47139][#47139] -- As part of migrating to the new schema change job implementation in 20.1, failed `IMPORT` and `RESTORE` jobs that left behind table data in 19.2 that had not been completely garbage collected by the time the cluster was upgraded to 20.1 will now have GC jobs automatically created for them. [#47144][#47144] -- Fixed a bug preventing clusters from creating `TIMETZ` columns before an upgrade to v20.1 is finalized. [#47169][#47169] -- Fixed a data race on AST nodes for `SELECT` statements that include a `WINDOW` clause. [#47175][#47175] -- Fixed the behavior of `crdb_internal.zones` in mixed-version clusters. [#47236][#47236] -- Fixed reads from `system.namespace` and `crdb_internal.zones` on 19.2 nodes in a mixed-version cluster. [#47236][#47236] -- Fixed incompatibility with v19.2 nodes for tables with computed columns. [#47274][#47274] -- Restoring a backup from v2.1 to v20.1 with a timestamp column no longer results in incomplete type data. [#47240][#47240] -- Fixed some cases where limits were applied incorrectly when pushed down into scans (resulting in some queries returning more results than they should). [#47296][#47296] -- Fixed an assertion failure with the text "expected latches held, found none". [#47301][#47301] - -Performance improvements
- -- Improved execution plans involving filters with `OR` expressions. [#46371][#46371] -- Improved execution plans for queries containing a division by a constant. [#46861][#46861] -- Virtual tables that access all table descriptors now make fewer round trips. [#46949][#46949] - -Build changes
- -- Building from source now requires Go 1.13.19. [#46619][#46619] {% comment %}doc{% endcomment %} -- It is now possible to build CockroachDB with the Clang++ v10 compiler. [#46860][#46860] {% comment %}doc{% endcomment %} - -Doc updates
- -- Improved the documentation on [viewing and controlling backup jobs](https://www.cockroachlabs.com/docs/v20.1/backup#viewing-and-controlling-backups-jobs) and added documentation on [showing a backup with privileges](https://www.cockroachlabs.com/docs/v20.1/show-backup#show-a-backup-with-privileges). [#7101](https://github.com/cockroachdb/docs/pull/7101) -- Documented [key/passphrase-based backup encryption](https://www.cockroachlabs.com/docs/v20.1/backup-and-restore). [#7085](https://github.com/cockroachdb/docs/pull/7085) -- Documented how to use [`EXPLAIN(DISTSQL, TYPES)`](https://www.cockroachlabs.com/docs/v20.1/explain#distsql-option) to include the data types of the input columns in the generated physical plan. [#7045](https://github.com/cockroachdb/docs/pull/7045) -- Updated [Azure hardware recommendations](https://www.cockroachlabs.com/docs/v20.1/recommended-production-settings#azure). [#7005](https://github.com/cockroachdb/docs/pull/7005) -- Documented [`INTERVAL`](https://www.cockroachlabs.com/docs/v20.1/interval) duration fields and updated the syntax and precision details. [#7000](https://github.com/cockroachdb/docs/pull/7000) -- Various updates related to [role-based access control (RBAC)](https://www.cockroachlabs.com/docs/v20.1/authorization) moving under the BSL license. [#7003](https://github.com/cockroachdb/docs/pull/7003) - -Contributors
- -This release includes 173 merged PRs by 32 authors. We would like to thank the following contributors from the CockroachDB community: - -- Andrii Vorobiov -- Shaker Islam (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -SQL language changes
- -- The new ability to specify [`TIME`/`TIMETZ`](https://www.cockroachlabs.com/docs/v20.1/time#precision) and [`INTERVAL`](https://www.cockroachlabs.com/docs/v20.1/interval#precision) precision is available only after finalizing an upgrade to v20.1. Previously, it was allowed to specify precision for these data types in clusters with mixed v19.2 and v20.1 nodes, but nodes running v19.2 would not respect the precision. [#47438][#47438] - -Command-line changes
- -- The new `--clock-device` flag for [`cockroach start`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start) and [`cockroach start-single-node`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start-single-node) identifies a [PTP hardware clock](https://www.kernel.org/doc/html/latest/driver-api/ptp.html) for querying current time. This is supported on Linux only and may be needed in cases where the host clock is unreliable or prone to large jumps (e.g., when using vMotion). [#47379][#47379] - -Bug fixes
- -- Fixed a bug causing some schema change rollbacks to fail permanently even on transient errors. [#47575][#47575] -- Fixed an incompatibility between Pebble and RocksDB bloom filters that could result in keys disappearing or reappearing when switching storage engines. [#47611][#47611] -- Fixed a panic that would result in "invalid truncation decision" error messages. [#47346][#47346] -- Fixed a backward incompatibility between RocksDB and Pebble that prevented RocksDB from opening a Pebble created WAL file under certain conditions. [#47383][#47383] -- Fixed a mishandling of truncated WAL records in Pebble that could prevent Pebble from opening a DB after a crash. [#47383][#47383] -- Fixed a bug in the new schema change GC job implementation that caused unnecessary table descriptor lookups whenever a table was updated. [#47490][#47490] -- Fixed a bug introduced in an earlier v20.1 release that could cause a workload to stall under heavy load. [#47493][#47493] -- Fixed a bug introduced with the new schema change job implementation in v20.1.0-beta.3 that caused errors when rolling back a schema change to be swallowed. [#47499][#47499] -- Fixed a bug that could could trigger an assertion with the text "received X results, limit was Y". [#47501][#47501] - -Contributors
- -This release includes 15 merged PRs by 10 authors. - -[#47346]: https://github.com/cockroachdb/cockroach/pull/47346 -[#47379]: https://github.com/cockroachdb/cockroach/pull/47379 -[#47383]: https://github.com/cockroachdb/cockroach/pull/47383 -[#47438]: https://github.com/cockroachdb/cockroach/pull/47438 -[#47490]: https://github.com/cockroachdb/cockroach/pull/47490 -[#47493]: https://github.com/cockroachdb/cockroach/pull/47493 -[#47499]: https://github.com/cockroachdb/cockroach/pull/47499 -[#47501]: https://github.com/cockroachdb/cockroach/pull/47501 -[#47575]: https://github.com/cockroachdb/cockroach/pull/47575 -[#47611]: https://github.com/cockroachdb/cockroach/pull/47611 diff --git a/src/current/_includes/releases/v20.1/v20.1.0.md b/src/current/_includes/releases/v20.1/v20.1.0.md deleted file mode 100644 index 7988f024cc2..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.0.md +++ /dev/null @@ -1,117 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -With the release of CockroachDB v20.1, we've made a variety of productivity, performance, and security improvements. Check out a comprehensive [summary of the most significant user-facing changes](#v20-1-0-summary) and then [upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version). You can also read more about these changes in the [v20.1 blog post](https://www.cockroachlabs.com/blog/cockroachdb-20-1-release/) or [watch our 20.1 release demo and overview](https://www.cockroachlabs.com/webinars/introducing-cockroachdb-20-1-build-fast-and-build-to-last/). - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -Summary
- -This section summarizes the most significant user-facing changes in v20.1.0. For a complete list of features and changes, including bug fixes and performance improvements, see the [release notes]({% link releases/index.md %}#testing-releases) for previous testing releases. - -- [CockroachCloud](#v20-1-0-cockroachcloud) -- [Core features](#v20-1-0-core-features) -- [Enterprise features](#v20-1-0-enterprise-features) -- [Backward-incompatible changes](#v20-1-0-backward-incompatible-changes) -- [Known limitations](#v20-1-0-known-limitations) -- [Education](#v20-1-0-education) - - - -CockroachCloud
- -- You can now use the code `CRDB30` for a **free 30-day trial of CockroachCloud**. - -- **[CockroachCloud pricing](https://www.cockroachlabs.com/pricing/)** is now available on our website. - -- **VPC peering** is now supported for CockroachCloud clusters running on GCP. [Contact us](https://www.cockroachlabs.com/contact-sales/) to set up a VPC peering-enabled CockroachCloud cluster. - -Core features
- -These features are freely available in the core version and do not require an enterprise license. - -Area | Feature | Description ------|---------|------------ -SQL | **Online Primary Key Changes** | The new [`ALTER TABLE ... ALTER PRIMARY KEY`](https://www.cockroachlabs.com/docs/v20.1/alter-primary-key) statement lets you change a table’s primary key with no interruption to data access. The old primary key is converted to a `UNIQUE` secondary index to help optimize the performance of queries that still filter on the old key. However, if this conversion is not desired, you can [drop and add a primary key constraint](https://www.cockroachlabs.com/docs/v20.1/add-constraint#drop-and-add-a-primary-key-constraint) instead. -SQL | **Schema Change Controls** | [Online schema changes](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes) can now be paused, resumed, and cancelled via [`PAUSE JOB`](https://www.cockroachlabs.com/docs/v20.1/pause-job), [`RESUME JOB`](https://www.cockroachlabs.com/docs/v20.1/resume-job), and [`CANCEL JOB`](https://www.cockroachlabs.com/docs/v20.1/cancel-job). -SQL | **Foreign Key Improvements** | CockroachDB now supports [multiple foreign key constraints on a single column](https://www.cockroachlabs.com/docs/v20.1/foreign-key#add-multiple-foreign-key-constraints-to-a-single-column). Also, it's now possible to drop the index on foreign key columns, or on the referenced columns, if another index exists on the same columns and fulfills [indexing requirements](https://www.cockroachlabs.com/docs/v20.1/foreign-key#rules-for-creating-foreign-keys). -SQL | **`SELECT FOR UPDATE`** | The new [`SELECT FOR UPDATE`](https://www.cockroachlabs.com/docs/v20.1/select-for-update) statement lets you order transactions by controlling concurrent access to one or more rows of a table. It works by locking the rows returned by a selection query, such that other transactions attempting to `SELECT` the same data and then `UPDATE` the results of that selection are forced to wait for the transaction that locked the rows to finish. This prevents [transaction retries](https://www.cockroachlabs.com/docs/v20.1/transactions#transaction-retries) that would otherwise occur and, thus, leads to increased throughput and decreased tail latency for contended operations. -SQL | **Nested Transactions and Savepoints** | CockroachDB now supports the nesting of transactions using savepoints. These [nested transactions](https://www.cockroachlabs.com/docs/v20.1/transactions#nested-transactions), also known as sub-transactions, can be rolled back without discarding the state of the entire surrounding transaction. This can be useful in applications that abstract database access using an application development framework or ORM. Different components of the application can operate on different sub-transactions without having to know about each others' internal operations, while trusting that the database will maintain isolation between sub-transactions and preserve data integrity. -SQL | **Hash-Sharded Indexes** | For tables indexed on sequential keys, CockroachDB nows offers [hash-sharded indexes](https://www.cockroachlabs.com/docs/v20.1/indexes#hash-sharded-indexes) to distribute sequential traffic uniformly across ranges, eliminating single-range hotspots and improving write performance on sequentially-keyed indexes at a small cost to read performance. This feature is currently [experimental](https://www.cockroachlabs.com/docs/v20.1/experimental-features). -SQL | **Slow Query Log** | You can now enable a [slow query log](https://www.cockroachlabs.com/docs/v20.1/query-behavior-troubleshooting#using-the-slow-query-log) to record SQL queries whose service latency exceeds a specified threshold. -SQL | **`EXPLAIN` Improvements** | The new [`EXPLAIN ANALYZE (DEBUG)`](https://www.cockroachlabs.com/docs/v20.1/explain-analyze#debug-option) option executes a query and generates a link to a ZIP file that contains the physical query plan, execution statistics, statement tracing, and other information about the query. Also, the `(DISTSQL, TYPES)` option on `EXPLAIN` and `EXPLAIN ANALYZE` include the data types of the input columns in the physical plan. -SQL | **Recursive Common Table Expressions** | CockroachDB now supports [common table expressions that contain subqueries that refer to their own output](https://www.cockroachlabs.com/docs/v20.1/common-table-expressions#recursive-common-table-expressions). -SQL | **`TIMETZ` Data Type** | CockroachDB now supports the [`TIMETZ` variant](https://www.cockroachlabs.com/docs/v20.1/time#timetz) of the `TIME` data type for SQL standard compliance and increased compatibility with ORMS. -SQL | **Precision in Time Values** | CockroachDB now supports precision levels from 0 (seconds) to 6 (microseconds) for [`TIME`/`TIMETZ`](https://www.cockroachlabs.com/docs/v20.1/time#precision) and [`INTERVAL`](https://www.cockroachlabs.com/docs/v20.1/interval#precision) values. Precision in time values specifies the number of fractional digits retained in the seconds field. -SQL | **Vectorized Execution Improvements** | [Vectorized execution](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) now supports [hash joins](https://www.cockroachlabs.com/docs/v20.1/joins#hash-joins), [merge joins](https://www.cockroachlabs.com/docs/v20.1/joins#merge-joins), most [window functions](https://www.cockroachlabs.com/docs/v20.1/window-functions), as well as the [`TIMESTAMPTZ`](https://www.cockroachlabs.com/docs/v20.1/timestamp) data type in addition to several other previously [supported data types](https://www.cockroachlabs.com/docs/v20.1/data-types). -SQL | **Column Families in Secondary Indexes** | [Secondary indexes](https://www.cockroachlabs.com/docs/v20.1/column-families) now respect the column family definitions applied to tables. When you define a secondary index, CockroachDB breaks the secondary index key-value pairs into column families, according to the family and stored column configurations. -SQL | **Temporary Tables** | CockroachDB now supports session-scoped [temporary tables](https://www.cockroachlabs.com/docs/v20.1/temporary-tables), [views](https://www.cockroachlabs.com/docs/v20.1/views#temporary-views), and [sequences](https://www.cockroachlabs.com/docs/v20.1/create-sequence#temporary-sequences). Unlike persistent objects, temp objects can only be accessed from the session in which they were created, and they are dropped at the end of the session. This feature is currently [experimental](https://www.cockroachlabs.com/docs/v20.1/experimental-features). -Dev Tools | **Expanded ORM Support** | CockroachDB now supports additional Postgres-compatible ORMs, including [Django](https://www.cockroachlabs.com/docs/v20.1/build-a-python-app-with-cockroachdb-django) and [pewee](https://www.cockroachlabs.com/docs/v20.1/install-client-drivers#peewee) for Python developers, and [jOOQ](https://www.cockroachlabs.com/docs/v20.1/build-a-java-app-with-cockroachdb-jooq) for Java developers. -I/O | **Bulk Import Improvements** | The [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import) and [`IMPORT INTO`](https://www.cockroachlabs.com/docs/v20.1/import-into) statements now support bulk importing [from Avro files](https://www.cockroachlabs.com/docs/v20.1/migrate-from-avro). This makes it easier to migrate from systems like Spanner that export data in the Avro format.Also, the new [`cockroach nodelocal upload`](https://www.cockroachlabs.com/docs/v20.1/cockroach-nodelocal-upload) command makes it easier to upload a file to a node's external IO directory for import from the node rather than from cloud storage.
Finally, [paused](https://www.cockroachlabs.com/docs/v20.1/pause-job) imports, when [resumed](https://www.cockroachlabs.com/docs/v20.1/resume-job), now continue from their internally recorded progress instead of starting over. -Security | **RBAC Changes** | All [role-based access control (RBAC) features](https://www.cockroachlabs.com/docs/v20.1/authorization#roles) (`CREATE ROLE`, `ALTER ROLE`, `DROP ROLE`, `GRANT ROLE`, `REVOKE ROLE`) are now covered by the [BSL license](https://www.cockroachlabs.com/docs/v20.1/licensing-faqs) and available to non-enterprise users. -Security | **Various Improvements** | Several security features have been added to CockroachDB v20.1, including the ability to [customize the mapping between TLS certificates and principals](https://www.cockroachlabs.com/docs/v20.1/create-security-certificates-openssl#step-2-create-the-certificate-and-key-pairs-for-nodes), to [name user/roles with periods](https://www.cockroachlabs.com/docs/v20.1/create-user#considerations) so as to reflect the structure of internet domain names, to [allow or disallow users from authenticating](https://www.cockroachlabs.com/docs/v20.1/create-user#set-login-privileges-for-a-user), and to [allow or disallow users from creating, altering, and dropping other users](https://www.cockroachlabs.com/docs/v20.1/create-user#allow-the-user-to-create-other-users).
Also, CockroachDB's support for the PostgreSQL Host-Based Authentication (HBA) configuration language, which enables sites to customize the principal/client address/authentication method matrix, has been extended and unified. -CLI | **Demo Cluster Improvements** | Several features have been added to the [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) command, including the ability to start a demo cluster in secure mode using TLS certificates to encrypt network communication (via the `--insecure=false` flag), to return the client connection URLs for all nodes in a demo cluster (via the `demo ls` shell command), to shut down/restart/decommission/recommission individual nodes in a multi-node demo cluster (via the `demo shutdown|restart|decommission|recommission
Also, the **Statement Details** page now allows you to write information about a SQL statement to a [diagnostics bundle](https://www.cockroachlabs.com/docs/v20.1/admin-ui-statements-page#diagnostics) that you can download. This bundle consists of a JSON file that contains a distributed trace of the SQL statement, a physical query plan, execution statistics, and other information about the query. -Internals | **Various Improvements** | CockroachDB's storage layer now uses [protected timestamps](https://www.cockroachlabs.com/docs/v20.1/architecture/storage-layer#protected-timestamps) to ensure the safety of historical data while also enabling shorter [GC TTLs](https://www.cockroachlabs.com/docs/v20.1/configure-replication-zones#gc-ttlseconds). A shorter GC TTL means that fewer previous MVCC values are kept around. This can help lower query execution costs for workloads which update rows frequently throughout the day, since the [SQL layer](https://www.cockroachlabs.com/docs/v20.1/architecture/sql-layer) has to scan over previous MVCC values to find the current value of a row.
Also, Cockroach's transaction layer now uses a [concurrency manager](https://www.cockroachlabs.com/docs/v20.1/architecture/transaction-layer#concurrency-manager) to sequence incoming requests and provide isolation between the transactions that issued those requests that intend to perform conflicting operations. - -
Enterprise features
- -These features require an [enterprise license](https://www.cockroachlabs.com/docs/v19.2/enterprise-licensing). Register for a 30-day trial license [here](https://www.cockroachlabs.com/get-cockroachdb/enterprise/), or consider testing enterprise features locally using the [`cockroach demo`](https://www.cockroachlabs.com/docs/v19.2/cockroach-demo) CLI command, which starts an in-memory CockroachDB cluster with a temporary enterprise license pre-loaded. [CockroachCloud clusters](https://cockroachlabs.cloud/) also include all enterprise features. - -Area | Feature | Description ------|---------|------------ -Recovery | **Full-cluster backup and restore** | CockroachDB's `BACKUP` feature now supports [backing up an entire cluster's data](https://www.cockroachlabs.com/docs/v20.1/backup-and-restore#full-backups), including all configuration and system information such as [user privileges](https://www.cockroachlabs.com/docs/v20.1/authorization#privileges), [zone configurations](https://www.cockroachlabs.com/docs/v20.1/configure-replication-zones), and [cluster settings](https://www.cockroachlabs.com/docs/v20.1/cluster-settings). In rare disaster recovery situations, CockroachDB's `RESTORE` feature can now [restore a cluster backup to a new cluster](https://www.cockroachlabs.com/docs/v20.1/restore#full-cluster). Restoring a cluster backup to an existing cluster is not supported. -Recovery | **Encrypted backups** | CockroachDB now supports using an [encryption passphrase](https://www.cockroachlabs.com/docs/v20.1/backup-and-restore) to encrypt data in Enterprise `BACKUP` files and to decrypt the data upon `RESTORE`. -SQL | **Improved follower reads** | [Follower reads](https://www.cockroachlabs.com/docs/v20.1/follower-reads) are now available for `AS OF SYSTEM TIME` queries at least 4.8 seconds in the past, a much shorter window than the previous 48 seconds. - -Backward-incompatible changes
- -Before [upgrading to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version), be sure to review the following backward-incompatible changes and adjust your application as necessary. - -- The `extract()` [built-in function](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators) with sub-second arguments (millisecond, microsecond) is now Postgres-compatible and returns the total number of seconds in addition to sub-seconds instead of returning only sub-seconds. - -- Casting intervals to integers and floats is now Postgres-compatible and values a year at 365.25 days in seconds instead of 365 days. - -- The combination of the [`CHANGEFEED`](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) options `format=experimental_avro`, `envelope=key_only`, and `updated` is now rejected. This is because the use of `key_only` prevents any rows with updated fields from being emitted, which renders the `updated` option meaningless. - -- The [`cockroach init`](https://www.cockroachlabs.com/docs/v20.1/cockroach-init) CLI command now waits for server readiness and thus no longer fails when a mistaken server address is provided. - -- The `cockroach user` CLI command has been removed. It was previously deprecated in CockroachDB v19.2. Note that a v19.2 client (supporting `cockroach user`) can still operate user accounts in a v20.1 server. - -- CockroachDB now creates files without read permissions for the "others" group. Sites that automate file management (e.g., log collection) using multiple user accounts now must ensure that the CockroachDB server and the management tools running on the same system are part of a shared unix group. - -- The [`GRANT`](https://www.cockroachlabs.com/docs/v20.1/grant) and [`REVOKE`](https://www.cockroachlabs.com/docs/v20.1/revoke) statements now require that the requesting user already have the target privileges themselves. For example, `GRANT SELECT ON t TO foo` requires that the requesting user already have the `SELECT` privilege on `t`. - -- During an [upgrade to v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version), ongoing [schema changes](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes) will stop making progress, and it will not be possible to manipulate them via [`PAUSE JOB`](https://www.cockroachlabs.com/docs/v20.1/pause-job)/[`RESUME JOB`](https://www.cockroachlabs.com/docs/v20.1/resume-job)/[`CANCEL JOB`](https://www.cockroachlabs.com/docs/v20.1/cancel-job) statements. Once the upgrade has been finalized, these schema changes will run to completion. - -- During an [upgrade to v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version), new [schema changes](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes) will be blocked and return an error, with the exception of [`CREATE TABLE`](https://www.cockroachlabs.com/docs/v20.1/create-table) statements without foreign key references and no-op schema change statements that use `IF NOT EXISTS`. Also, ongoing schema changes started will stop making progress, and it will not be possible to manipulate them via [`PAUSE JOB`](https://www.cockroachlabs.com/docs/v20.1/pause-job)/[`RESUME JOB`](https://www.cockroachlabs.com/docs/v20.1/resume-job)/[`CANCEL JOB`](https://www.cockroachlabs.com/docs/v20.1/cancel-job) statements. Once the upgrade has been finalized, ongoing schema changes will run to completion and new schema changes will be allowed. - -Known limitations
- -For information about new and unresolved limitations in CockroachDB v20.1, with suggested workarounds where applicable, see [Known Limitations](https://www.cockroachlabs.com/docs/v20.1/known-limitations). - -Education
- -Area | Topic | Description ------|-------|------------ -Training | **Videos Lessons on YouTube** | Added two [Cockroach University](https://university.cockroachlabs.com) playlists to YouTube, one with the entire set of video lessons from ["Getting Started with CockroachDB"](https://www.youtube.com/playlist?list=PL_QaflmEF2e8Prn7r7CIyBKsHPgsgNO_1), and the other featuring the first batch of video lessons from the upcoming course, ["CockroachDB for Python Developers"](https://www.youtube.com/playlist?list=PL_QaflmEF2e8ijr7gxCZHSKH9-Vl8Yf9q). -Docs | **Developer Guide** | Added guidance on common tasks when building apps on CockroachDB, such as [installing Postgres clients](https://www.cockroachlabs.com/docs/v20.1/install-client-drivers); [connecting to the database](https://www.cockroachlabs.com/docs/v20.1/connect-to-the-database); effectively [inserting](https://www.cockroachlabs.com/docs/v20.1/insert-data), [querying](https://www.cockroachlabs.com/docs/v20.1/query-data), [updating](https://www.cockroachlabs.com/docs/v20.1/update-data), and [deleting](https://www.cockroachlabs.com/docs/v20.1/delete-data); [handling errors](https://www.cockroachlabs.com/docs/v20.1/error-handling-and-troubleshooting); and [making queries fast](https://www.cockroachlabs.com/docs/v20.1/make-queries-fast). For convenience, much of the guidance is offered across various popular languages (Java, Python, Go) in addition to straight SQL. -Docs | **"Hello World" Repos** | Added several language-specific [GitHub repos](https://github.com/cockroachlabs?q=hello-world&type=&language=) with the simple starter applications featured in our ["Hello World" tutorials](https://www.cockroachlabs.com/docs/v20.1/hello-world-example-apps). -Docs | **Multi-Region Sample App and Tutorial** | Added a full-stack, multi-region sample application ([GitHub repo](https://github.com/cockroachlabs/movr-flask)) with an [accompanying tutorial](https://www.cockroachlabs.com/docs/v20.1/multi-region-overview) on building a multi-region application on a multi-region CockroachCloud cluster. Also added a [video demonstration](https://www.youtube.com/playlist?list=PL_QaflmEF2e8o2heLyIt5iDUTgJE3EPkp) as a YouTube playlist. -Docs | **Streaming Changefeeds to Snowflake Tutorial** | Added an [end-to-end tutorial](https://www.cockroachlabs.com/docs/cockroachcloud/stream-changefeed-to-snowflake-aws) on how to use an Enterprise changefeed to stream row-level changes from CockroachCloud to Snowflake, an online analytical processing (OLAP) database. -Docs | **Improved Backup/Restore Docs** | Updated the backup/restore docs to better separate [broadly applicable guidance and best practices](https://www.cockroachlabs.com/docs/v20.1/backup-and-restore) from more advanced topics. -Docs | **Release Support Policy** | Added a page explaining Cockroach Labs' [policy for supporting major releases of CockroachDB]({% link releases/release-support-policy.md %}), including the phases of support that each major release moves through, the currently supported releases, and an explanation of the [naming scheme]({% link releases/index.md %}#overview) used for CockroachDB. diff --git a/src/current/_includes/releases/v20.1/v20.1.1.md b/src/current/_includes/releases/v20.1/v20.1.1.md deleted file mode 100644 index aed4c12e947..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.1.md +++ /dev/null @@ -1,210 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -This page lists additions and changes in v20.1.1 since v20.1.0. - -- For a comprehensive summary of features in v20.1, see the [v20.1 GA release notes]({% link releases/v20.1.md %}#v20-1-0). -- To upgrade to v20.1, see [Upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version) - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -Backward-incompatible changes
- -- The copy of `system` and `crdb_internal` tables extracted by [`cockroach debug zip`](https://www.cockroachlabs.com/docs/v20.1/cockroach-debug-zip) is now written using the `TSV` format (inside the .zip file), instead of an ASCII-art table. [#48094][#48094] {% comment %}doc{% endcomment %} -- Updated the textual error and warning messages displayed by [`cockroach quit`](https://www.cockroachlabs.com/docs/v20.1/cockroach-quit). [#47692][#47692] -- [`cockroach quit`](https://www.cockroachlabs.com/docs/v20.1/cockroach-quit) now prints progress details on its standard error stream, even when `--logtostderr` is not specified. Scripts that wish to ignore this output can redirect the standard error stream. [#47692][#47692] {% comment %}doc{% endcomment %} -- CockroachDB v20.1 introduced an experimental new rule for the `--join` flag causing it to prefer SRV records, if present in DNS, to look up the peer nodes to join. However, it is also found to cause disruption in in certain deployments. To reduce this disruption and UX surprise, the feature is now gated behind a new command-line flag `--experimental-dns-srv` which must now be explicitly passed to [`cockroach start`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start) to enable it. [#49129][#49129] {% comment %}doc{% endcomment %} -- Added a new cluster setting, `server.shutdown.lease_transfer_wait`, that allows you to configure the server shutdown timeout period for transferring range leases to other nodes. Previously, the timeout period was not configurable and was set to 5 seconds, and the phase of server shutdown responsible for range lease transfers would give up after 10000 attempts of transferring replica leases away. The limit of 10000 attempts has been removed, so that now only the maximum duration `server.shutdown.lease_transfer_wait` applies. [#47692][#47692] {% comment %}doc{% endcomment %} - -General changes
- -- The [statement diagnostics](https://www.cockroachlabs.com/docs/v20.1/admin-ui-statements-page#diagnostics) bundle now contains a new file, `trace-jaeger.json`, that can be manually imported in Jaeger for visualization. [#47432][#47432] {% comment %}doc{% endcomment %} - -Enterprise edition changes
- -- Fixed a bug where the job ID of a lagging [changefeed](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) would be omitted, and instead it would be reported as sinkless. [#48562][#48562] - -SQL language changes
- -- The `pg_collation`, `pg_proc`, `pg_database`, and `pg_type` tables in the `pg_catalog` database no longer require privileges on any database in order for the data to be visible. [#48080][#48080], [#48765][#48765] -- Histogram collection with [`CREATE STATISTICS`](https://www.cockroachlabs.com/docs/v20.1/create-statistics) is no longer supported on columns with type `array`. Only row count, distinct count, and null count are collected for array-type columns. [#48343][#48343] {% comment %}doc{% endcomment %} -- [`ROLLBACK TO SAVEPOINT`](https://www.cockroachlabs.com/docs/v20.1/rollback-transaction) is no longer permitted after miscellaneous internal errors. [#48305][#48305] {% comment %}doc{% endcomment %} -- Fixed an issue with optimizing subqueries involving [set operations](https://www.cockroachlabs.com/docs/v20.1/selection-queries) that can prevent queries from executing. [#48680][#48680] -- CockroachDB now correctly reports the type length for the `char` type. [#48642][#48642] -- The `RowDescription` message of the wire-level protocol now contains the table ID and column ID for each column in the result set. These values correspond to `pg_attribute.attrelid` and `pg_attribute.attnum`. If a result column does not refer to a simple table or view, these values will be zero, as they were before. The message also contains the type modifier for each column in the result set. This corresponds to `pg_attribute.atttypmod`. If it is not available, the value is `-1`, as it was before. [#48748][#48748], [#49087][#49087] - -Command-line changes
- -- [`cockroach debug zip`](https://www.cockroachlabs.com/docs/v20.1/cockroach-debug-zip) now tries multiple times to retrieve data using SQL if it encounters retry errors and skips over fully decommissioned nodes. It also supports two command-line parameters `--nodes` and `--exclude-nodes`. When specified, they control which nodes are inspected when gathering the data. This makes it possible to focus on a group of nodes of interest in a large cluster, or to exclude nodes that `cockroach debug zip` would have trouble reaching otherwise. Both flags accept a list of individual node IDs or ranges of node IDs, e.g., `--nodes=1,10,13-15`. [#48094][#48094] {% comment %}doc{% endcomment %} -- Client commands such as [`cockroach init`](https://www.cockroachlabs.com/docs/v20.1/cockroach-init) and [`cockroach quit`](https://www.cockroachlabs.com/docs/v20.1/cockroach-quit) now support the `--cluster-name` and `--disable-cluster-name-verification` flags in order to support running them on clusters that have been configured to use a cluster name. Previously it was impossible to run such commands against nodes configured with the `--cluster-name` flag. [#48016][#48016] {% comment %}doc{% endcomment %} -- It is now possible to drain a node without shutting down the process, using the `cockroach node drain` command. This makes it easier to integrate with service managers and orchestration: it now becomes safe to issue `cockroach node drain` and then separately stop the service via a process manager or orchestrator. Without this new mode, there is a risk to misconfigure the service manager to auto-restart the node after it shuts down via `quit`, in a way that's surprising or unwanted. The new command `node drain` also recognizes the new `--drain-wait` flag. [#47692][#47692] {% comment %}doc{% endcomment %} -- The time that [`cockroach quit`](https://www.cockroachlabs.com/docs/v20.1/cockroach-quit) waits client-side for the node to drain (remove existing clients and push range leases away) is now configurable via the command-line flag `--drain-wait`. Note that separate server-side timeouts also apply separately. Check the `server.shutdown.*` cluster settings for details. [#47692][#47692] {% comment %}doc{% endcomment %} -- The commands [`cockroach quit`](https://www.cockroachlabs.com/docs/v20.1/cockroach-quit) and `cockroach node drain` now report a "work remaining" metric on their standard error stream. The value reduces until it reaches `0` to indicate that the graceful shutdown has completed server-side. An operator can now rely on `cockroach node drain` to obtain confidence of a graceful shutdown prior to terminating the server process. [#47692][#47692] {% comment %}doc{% endcomment %} -- The default value of the parameter `--drain-wait` for [`cockroach quit`](https://www.cockroachlabs.com/docs/v20.1/cockroach-quit) has been increased from 1 minute to 10 minutes, to give more time for nodes with thousands of ranges to migrate their leases away. [#47692][#47692] {% comment %}doc{% endcomment %} -- Added support for `list cert` with certificates which require `--cert-principal-map` to pass validation. [#48177][#48177] {% comment %}doc{% endcomment %} -- Added support for the `--cert-principal-map` flag in the [`cockroach cert`](https://www.cockroachlabs.com/docs/v20.1/cockroach-cert), [`cockroach sql`](https://www.cockroachlabs.com/docs/v20.1/cockroach-sql), [`cockroach init`](https://www.cockroachlabs.com/docs/v20.1/cockroach-init), and [`cockroach quit`](https://www.cockroachlabs.com/docs/v20.1/cockroach-quit) commands. [#48177][#48177] {% comment %}doc{% endcomment %} -- Made `--storage-engine` sticky (i.e., resolve to the last used engine type when unspecified) even when specified stores are encrypted at rest. [#49073][#49073] {% comment %}doc{% endcomment %} - -Admin UI changes
- -- Fixed a bug where `Raft log too large` was reported incorrectly for replicas for which the raft log size is not to be trusted. [#48286][#48286] -- Fixed a bug where a multi-node cluster without localities defined wouldn't be able to render the [**Network Latency**](https://www.cockroachlabs.com/docs/v20.1/admin-ui-network-latency-page) page. [#49191][#49191] -- Fixed a bug where link to specific problem ranges had an incorrect path. Problem ranges are now linked correctly again. [#49188][#49188] - -Bug fixes
- -- Fixed a bug where vectorized queries on composite datatypes could sometimes return invalid data. [#48463][#48463] -- Fixed a bug that could lead to data corruption or data loss if a replica was both the source of a snapshot and was being concurrently removed from the range and certain specific conditions exist inside RocksDB. This scenario is rare, but possible. [#48321][#48321] -- Fixed a bug where the migration for ongoing schema change jobs would cause the node to panic with an "index out of bounds" error upon encountering a malformed table descriptor with no schema change mutation corresponding to the job to be migrated. [#48838][#48838] -- Fixed an error where instead of returning a parsing error in queries with `count(*)` CockroachDB could incorrectly return no output (when the query was executed via row-by-row engine). [#47485][#47485] -- Fixed a bug where CockroachDB was incorrectly releasing memory used by hash aggregation. [#47518][#47518] -- [`cockroach debug zip`](https://www.cockroachlabs.com/docs/v20.1/cockroach-debug-zip) can now successfully avoid out-of-memory errors when extracting very large `system` or `crdb_internal` tables. It will also report an error encountered while writing the end of the output ZIP file. [#48094][#48094] -- Removed redundant metadata information for subqueries and postqueries in [`EXPLAIN (VERBOSE)`](https://www.cockroachlabs.com/docs/v20.1/explain) output. [#47975][#47975] -- [`TRUNCATE`](https://www.cockroachlabs.com/docs/v20.1/truncate) can now run on temporary tables, fixing a bug in v20.1 where temporary tables could not be truncated, resulting in an error `unexpected value: nil`. [#48078][#48078] -- Fixed a bug in which `(tuple).*` was only expanded to the first column in the tuple and the remaining elements were dropped. [#48290][#48290] -- Fixed case where [`PARTITION BY`](https://www.cockroachlabs.com/docs/v20.1/partition-by) and [`ORDER BY`](https://www.cockroachlabs.com/docs/v20.1/query-order) columns in window specifications were losing qualifications when used inside views. [#47715][#47715] -- CockroachDB will no longer display a severe `internal error` upon certain privilege check failures via `pg_catalog` built-in functions. [#48242][#48242] -- Fixed a bug where a read operation in a transaction with a past savepoint rollback would give an internal error for exceeding the maximum count of results requested [#48165][#48165] -- The distinction between delete jobs for columns and dependent jobs for deleting indices, views and sequences is now better defined. [#48259][#48259] -- Fixed incorrect results that could occur when casting negative intervals or timestamps to type `decimal`. [#48345][#48345] -- Fixed an error that occurred when statistics collection was explicitly requested on a column with type `array`. [#48343][#48343] -- Fixed a nil pointer dereference in Pebble's block cache due to a rare "double free" of a block. [#48346][#48346] -- Fixed Pebble to properly mark `sstables` for compaction which contain range tombstones. This matches the behavior when using RocksDB and ensures that space used for temporary storage is reclaimed quickly. [#48346][#48346] -- Fixed a bug introduced in v20.1 that could cause multiple index GC jobs to be created for the same schema change in rare cases. [#47818][#47818] -- Fixed a bug where CockroachDB could return an internal error when performing a query with `CASE`, `AND`, `OR` operators in some cases when it was executed via the vectorized engine. [#48072][#48072] -- Fixed a rare bug where stats were not automatically generated for a new table. [#48027][#48027] -- Fixed a panic that could occur when [`SHOW RANGES`](https://www.cockroachlabs.com/docs/v20.1/show-ranges) or [`SHOW RANGE FOR ROW`](https://www.cockroachlabs.com/docs/v20.1/show-range-for-row) was called with a virtual table. [#48347][#48347] -- Made SRV resolution non-fatal for join list records to align with the standard and improve reliability of node startup. [#48349][#48349] -- Fixed a rare bug causing a range to deadlock and all the writes to the respective range to timeout. [#48303][#48303] -- Fixed a long-standing bug where HTTP requests would start to fail with error 503 "`transport: authentication handshake failed: io: read/write on closed pipe`" and never become possible again until the node is restarted. [#48456][#48456] -- When processing `--join`, invalid SRV records with port number `0` are now properly ignored. [#48527][#48527] -- Fixed a bug where `SHOW STATISTICS USING JSON` contained incorrect single quotes for strings with spaces inside histograms. [#48544][#48544] -- Fixed a bug where the two settings `kv.range_split.by_load_enabled` and `kv.range_split.load_qps_threshold` were incorrectly marked as non-public in the output of `SHOW CLUSTER SETTINGS`. [#48585][#48585] -- You can no longer [drop databases](https://www.cockroachlabs.com/docs/v20.1/drop-database) that contain tables which are currently offline due to [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import) or [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore). Previously dropping a database in this state could lead to a corrupted schema which prevented running backups. [#48606][#48606] -- Fixed a bug preventing timestamps from being closed which could result in failed follower reads or failure to observe resolved timestamps in [changefeeds](https://www.cockroachlabs.com/docs/v20.1/change-data-capture). [#48682][#48682] -- Fixed `debug encryption-status` and the Admin UI display of encryption status when using Pebble. [#47995][#47995] -- CockroachDB now deletes the partially imported data after an [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import) fails or is canceled. [#48605][#48605] -- Fixed a bug where the [`SHOW CREATE`](https://www.cockroachlabs.com/docs/v20.1/show-create) statement would sometimes show a partitioning step for an index that has been dropped. [#48768][#48768] -- Re-allowed `diagnostics.forced_sql_stat_reset.interval`, `diagnostics.sql_stat_reset.interval` and `external.graphite.interval` to set to their maximum values (24hr, 24hr and 15min respectively). [#48760][#48760] -- Fixed a bug where CockroachDB could encounter an internal error when a query with `LEFT SEMI` or `LEFT ANTI` join was performed via the vectorized execution engine. This is likely to occur only with `vectorize=on` setting. [#48751][#48751] -- Fixed a bug where running [`cockroach dump`](https://www.cockroachlabs.com/docs/v20.1/cockroach-dump) on tables with interleaved primary keys would erroneously include an extra `CREATE UNIQUE INDEX "primary" ... INTERLEAVE IN PARENT` statement in the dump output. This made it impossible to reimport dumped data without manual editing. [#48776][#48776] -- Fixed a bug where running [`cockroach dump`](https://www.cockroachlabs.com/docs/v20.1/cockroach-dump) on a table with collated strings would omit the collation clause for the data insertion statements. [#48832][#48832] -- CockroachDB now properly [restores tables](https://www.cockroachlabs.com/docs/v20.1/restore) that were backed up while they were in the middle of a schema change. [#48850][#48850] -- Manually writing a `NULL` value into the `system.users` table for the `hashedPassword` column will no longer cause a server crash during user authentication. [#48836][#48836] -- Fixed a bug where in rare circumstances, CockroachDB may fail to open a store configured to use the Pebble storage engine. [#49080][#49080] -- Fixed a bug where the storage engine, when configured to use the Pebble storage engine, would return duplicate keys, causing incorrect or inconsistent results. [#49080][#49080] -- Fixed a bug where columns of a table could not be dropped after a primary key change. [#49088][#49088] -- Fixed a bug which falsely indicated that `kv.closed_timestamp.max_behind_nanos` was almost always growing. [#48716][#48716] -- Fixed a bug where changing the primary key of a table that had [partitioned indexes](https://www.cockroachlabs.com/docs/v20.1/multi-region-database) could cause indexes to lose their zone configurations. In particular, the indexes rebuilt as part of a primary key change would keep their partitions but lose the zone configurations attached to those partitions. [#48827][#48827] -- Fixed costing of lookup join with a limit on top, resulting in better plans in some cases. [#49137][#49137] -- Fixed a bug where on [dropping a database](https://www.cockroachlabs.com/docs/v20.1/drop-database), it would not drop the entry for its public schema in the `system.namespace` table. [#49139][#49139] -- [`SHOW BACKUP SCHEMAS`](https://www.cockroachlabs.com/docs/v20.1/show-backup#show-a-backup-with-schemas) no longer shows table comments as they may be inaccurate. [#49130][#49130] -- Fixed a memory leak which can affect [changefeeds](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) performing scans of large tables. [#49161][#49161] -- Prevented namespace orphans (manifesting as `database "" not found` errors) when migrating from v19.2. [#49200][#49200] -- Fixed a bug that caused query failures when using arrays in [window functions](https://www.cockroachlabs.com/docs/v20.1/window-functions). [#49238][#49238] - -Performance improvements
- -- Disabled the Go runtime block profile by default which results in a small but measurable reduction in CPU usage. The block profile has diminished in utility with the advent of mutex contention profiles and is almost never used during performance investigations. [#48153][#48153] -- The cleanup job which runs after a primary key change to remove old indexes, which blocks other schema changes from running, now starts immediately after the primary key swap is complete. This reduces the amount of waiting time before subsequent schema changes can run. [#47818][#47818] -- Histograms used by the optimizer for query planning now have more accurate row counts per histogram bucket, particularly for columns that have many null values. The histograms also have improved cardinality estimates. This results in better plans in some cases. [#48626][#48626], [#48646][#48646] -- Fixed a bug that caused a simple schema change to take more than 30s. [#48621][#48621] -- Queries run via the [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) are now processed faster, with most noticeable gains on the queries that output many rows. [#48732][#48732] -- Reduced time needed to run a [backup command](https://www.cockroachlabs.com/docs/v20.1/backup) when it is built on a lot of previous incremental backups. [#48772][#48772] - -Doc updates
- -- Added a tutorial on [using Flyway with CockroachDB](https://www.cockroachlabs.com/docs/v20.1/flyway). [#7329][#7329] - -Contributors
- -This release includes 94 merged PRs by 27 authors. -We would like to thank the following contributors from the CockroachDB community: - -- Drew Kimball (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -- For a comprehensive summary of features in v20.1, see the [v20.1 GA release notes]({% link releases/v20.1.md %}#v20-1-0). -- To upgrade to v20.1, see [Upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version). - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -Backward-incompatible changes
- -- The file names for heap profile dumps are now `memprof.SQL language changes
- -- Fixed a bug where temporary tables may be included in [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) commands. [#56475][#56475] - -Command-line changes
- -- CockroachDB now better attempts to retain heap profile dumps after a crash due to an out-of-memory error. [#55260][#55260] -- CockroachDB now better attempts to retain memory statistics corresponding to increases in total memory usage, not just heap allocations. [#55260][#55260] - -Bug fixes
- -- Fixed a panic that could occur when running [`SHOW STATISTICS USING JSON`](https://www.cockroachlabs.com/docs/v20.1/show-statistics) for a table in which at least one of the columns contained all null values. [#56515][#56515] -- The file names for generated `goroutine`, CPU and memory profiles were sometimes incorrect, resulting in repeated warnings like `strconv.ParseUint: parsing "txt": invalid syntax` in log files. This has been corrected. [#55260][#55260] -- Fixed a bug when the Pebble storage engine is used with [encryption-at-rest](https://www.cockroachlabs.com/docs/v20.1/encryption#encryption-at-rest-enterprise) that could result in data corruption in some fairly rare cases after a table drop, table truncate, or replica deletion. [#56680][#56680] -- Previously, dumps of tables with a [`BIT`](https://www.cockroachlabs.com/docs/v20.1/bit) type column would result in an error. This column type is now supported. [#56452][#56452] -- In 20.1.8, we attempted to fix `age`'s lack of normalization of `H:M:S` into the years, months, and days field. However, this was also broken for values greater than 1 month, as well as breaking `a::timestamp(tz) - b::timestamp(tz)` operators. This has now been resolved. [#56769][#56769] -- CockroachDB previously would crash when executing a query with an [`AS OF SYSTEM TIME`](https://www.cockroachlabs.com/docs/v20.1/as-of-system-time) clause that used a placeholder (note that it wasn't a prepared statement, it was an attempt to use an unspecified placeholder value on a non-prepared statement). This is now fixed. [#56781][#56781] -- CockroachDB previously could encounter an internal error when [`DATE`](https://www.cockroachlabs.com/docs/v20.1/date), [`TIMESTAMP`](https://www.cockroachlabs.com/docs/v20.1/timestamp), or [`TIMESTAMPTZ`](https://www.cockroachlabs.com/docs/v20.1/timestamp) values that used year 1 BC were sent between nodes for execution. Additionally, previously it was not possible to specify `DATE`, `TIMESTAMP`, or `TIMESTAMPTZ` values with year 1 BC without using AD/BC notation. This is now fixed. [#56743][#56743] -- Fixed internal error when collecting a statement diagnostic bundle in some cases where the query hits an error. [#56785][#56785] -- Some boolean session variables would only accept string (`"true"` or `"false"`) values. Now they also accept unquoted true or false values. [#56814][#56814] -- Fixed a bug which would prevent the dropping of hash sharded indexes if they were added prior to other columns. [#55823][#55823] -- Fixed a race condition in the [`tpcc`](https://www.cockroachlabs.com/docs/v20.1/performance-benchmarking-with-tpc-c-10-warehouses) workload with the `--scatter` flag where tables could be scattered multiple times or not at all. [#56979][#56979] -- Previously if a cluster backup that was taken during a schema change, a cluster restore of that backup would create duplicates of the ongoing schema changes. [#56450][#56450] -- Fixed a case where attempting to start a second [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) to the same location while the first was running using passphrase-based encryption could overwrite the metadata required to decrypt it and thus render it unreadable. [#57025][#57025] -- Fixed an internal error when using aggregates and window functions in an `ORDER BY` for a [`UNION or VALUES` clause](https://www.cockroachlabs.com/docs/v20.1/selection-queries). [#57522][#57522] -- The [`CREATE TEMP TABLE AS`](https://www.cockroachlabs.com/docs/v20.1/temporary-tables) statement previously created a non-temporary table. Now it makes a temporary one. [#57550][#57550] -- Fixed a bug where schema change jobs to add foreign keys to existing tables, via [`ALTER TABLE`](https://www.cockroachlabs.com/docs/v20.1/alter-table), could sometimes not be successfully reverted (either due to being canceled or having failed). [#57810][#57810] -- Fixed a bug where concurrent addition of a [foreign key constraint](https://www.cockroachlabs.com/docs/v20.1/foreign-key) and drop of a unique index could cause the foreign key constraint to be added with no unique constraint on the referenced columns. [#57810][#57810] -- Fixed a bug which can occur when canceling [schema changes](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes) when there are multiple queued schema changes that could result in future schema changes being stuck. [#55058][#55058] -- Fixed a bug which can lead to canceled [schema change](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes) jobs ending in the failed rather than canceled state. [#55058][#55058] - -Performance improvements
- -- Interactions between Raft heartbeats and the Raft `goroutine` pool scheduler are now more efficient and avoid excessive mutex contention. This was observed to prevent instability on large machines (32+ vCPU) in clusters with many ranges (50k+ per node). [#57009][#57009] - -Backward-compatible change
- -- The reserved, non-documented [cluster settings](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) `server.heap_profile.xxx` have been renamed to `server.mem_profile.xxx`. They now control collection of multiple sorts of memory profiles besides just Go heap allocations. [#55260][#55260] - -Contributors
- -This release includes 34 merged PRs by 16 authors. - -[#55058]: https://github.com/cockroachdb/cockroach/pull/55058 -[#55260]: https://github.com/cockroachdb/cockroach/pull/55260 -[#55823]: https://github.com/cockroachdb/cockroach/pull/55823 -[#56444]: https://github.com/cockroachdb/cockroach/pull/56444 -[#56450]: https://github.com/cockroachdb/cockroach/pull/56450 -[#56452]: https://github.com/cockroachdb/cockroach/pull/56452 -[#56475]: https://github.com/cockroachdb/cockroach/pull/56475 -[#56515]: https://github.com/cockroachdb/cockroach/pull/56515 -[#56680]: https://github.com/cockroachdb/cockroach/pull/56680 -[#56743]: https://github.com/cockroachdb/cockroach/pull/56743 -[#56769]: https://github.com/cockroachdb/cockroach/pull/56769 -[#56781]: https://github.com/cockroachdb/cockroach/pull/56781 -[#56785]: https://github.com/cockroachdb/cockroach/pull/56785 -[#56814]: https://github.com/cockroachdb/cockroach/pull/56814 -[#56979]: https://github.com/cockroachdb/cockroach/pull/56979 -[#57009]: https://github.com/cockroachdb/cockroach/pull/57009 -[#57025]: https://github.com/cockroachdb/cockroach/pull/57025 -[#57485]: https://github.com/cockroachdb/cockroach/pull/57485 -[#57522]: https://github.com/cockroachdb/cockroach/pull/57522 -[#57550]: https://github.com/cockroachdb/cockroach/pull/57550 -[#57810]: https://github.com/cockroachdb/cockroach/pull/57810 -[0b5b521ae]: https://github.com/cockroachdb/cockroach/commit/0b5b521ae -[6a8c69a9b]: https://github.com/cockroachdb/cockroach/commit/6a8c69a9b diff --git a/src/current/_includes/releases/v20.1/v20.1.11.md b/src/current/_includes/releases/v20.1/v20.1.11.md deleted file mode 100644 index b3a56e1074d..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.11.md +++ /dev/null @@ -1,47 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -- For a comprehensive summary of features in v20.1, see the [v20.1 GA release notes]({% link releases/v20.1.md %}#v20-1-0). -- To upgrade to v20.1, see [Upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version). - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -SQL language changes
- -- Fixed a bug in [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) where some unusual range boundaries in interleaved tables caused an error. [#58260][#58260] - -Bug fixes
- -- In v20.1.8, we attempted to fix `age`'s lack of normalization of `H:M:S` into the years, months and days field. However, this was also broken for values greater than 1 month, as well as breaking `a::timestamp(tz) - b::timestamp(tz)` operators. This has now been resolved. [#57956][#57956] -- Fixed an assertion error caused by some DDL statements used in conjunction with common table expressions (`WITH`). [#57952][#57952] -- Fixed a bug that caused temp tables to not be cleaned up after the associated session was closed. [#58167][#58167] -- Added a safeguard against crashes while running `SHOW STATISTICS USING JSON`, which is used internally for statement diagnostics, and [`EXPLAIN ANALYZE (DEBUG)`](https://www.cockroachlabs.com/docs/v20.1/explain-analyze). [#58264][#58264] -- Previously, CockroachDB could return non-deterministic output when querying the `information_schema.statistics` virtual table (internally used by the `SHOW INDEXES` command)—namely, the implicit columns of the secondary indexes could be in arbitrary order. This is now fixed, and the columns will be in the same order as they are in the primary index. [#58215][#58215] -- Previously, CockroachDB could crash when performing a [`DELETE`](https://www.cockroachlabs.com/docs/v20.1/delete) operation after an alteration of the primary key when in some cases, and now it is fixed. The bug was introduced in v20.1. [#58267][#58267] -- Fixed a panic in protobuf decoding. [#58861][#58861] -- Fixed a bug that caused errors when accessing a tuple column (`tuple.column` syntax) of a tuples that could be statically determined to be null. [#58899][#58899] -- Fixed an internal error involving string literals used as arrays. [#59066][#59066] -- GC jobs now populate the `running_status` column for [`SHOW JOBS`](https://www.cockroachlabs.com/docs/v20.1/show-jobs). This bug has been present since v20.1. [#59138][#59138] -- Fixed a bug in which some non-conflicting rows provided as input to an [`INSERT ... ON CONFLICT DO NOTHING`](https://www.cockroachlabs.com/docs/v20.1/insert) statement could be discarded, and not inserted. This could happen in cases where the table had one or more unique indexes in addition to the primary index, and some of the rows in the input conflicted with existing values in one or more unique index. This scenario could cause the rows that did not conflict to be erroneously discarded. This is now fixed. [#59172][#59172] - -Contributors
- -This release includes 24 merged PRs by 17 authors. - -[#57952]: https://github.com/cockroachdb/cockroach/pull/57952 -[#57956]: https://github.com/cockroachdb/cockroach/pull/57956 -[#58052]: https://github.com/cockroachdb/cockroach/pull/58052 -[#58167]: https://github.com/cockroachdb/cockroach/pull/58167 -[#58215]: https://github.com/cockroachdb/cockroach/pull/58215 -[#58260]: https://github.com/cockroachdb/cockroach/pull/58260 -[#58264]: https://github.com/cockroachdb/cockroach/pull/58264 -[#58267]: https://github.com/cockroachdb/cockroach/pull/58267 -[#58861]: https://github.com/cockroachdb/cockroach/pull/58861 -[#58899]: https://github.com/cockroachdb/cockroach/pull/58899 -[#59066]: https://github.com/cockroachdb/cockroach/pull/59066 -[#59138]: https://github.com/cockroachdb/cockroach/pull/59138 -[#59172]: https://github.com/cockroachdb/cockroach/pull/59172 -[d076397a4]: https://github.com/cockroachdb/cockroach/commit/d076397a4 diff --git a/src/current/_includes/releases/v20.1/v20.1.12.md b/src/current/_includes/releases/v20.1/v20.1.12.md deleted file mode 100644 index e0b9f6ef766..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.12.md +++ /dev/null @@ -1,31 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -- For a comprehensive summary of features in v20.1, see the [v20.1 GA release notes]({% link releases/v20.1.md %}#v20-1-0). -- To upgrade to v20.1, see [Upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version). - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -Bug fixes
- -- Fixed a bug in URL handling of HTTP external storage paths on Windows. [#59268][#59268] -- Fixed a bug where CockroachDB could encounter an internal error when executing queries with [`BYTES`](https://www.cockroachlabs.com/docs/v20.1/bytes) or [`STRING`](https://www.cockroachlabs.com/docs/v20.1/string) types via the [vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution). [#59257][#59257] -- Fixed a bug where CockroachDB could crash when executing an [`ALTER INDEX ... SPLIT/UNSPLIT AT`](https://www.cockroachlabs.com/docs/v20.1/split-at) statement when more values are provided than are explicitly specified in the [index](https://www.cockroachlabs.com/docs/v20.1/indexes). [#59272][#59272] - -Contributors
- -This release includes 3 merged PRs by 3 authors. -We would like to thank the following contributors from the CockroachDB community: - -- Cheng Jing (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -- For a comprehensive summary of features in v20.1, see the [v20.1 GA release notes]({% link releases/v20.1.md %}#v20-1-0). -- To upgrade to v20.1, see [Upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version). - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -Bug fixes
- -- Previously, if [`RELEASE SAVEPOINT cockroach_restart`](https://www.cockroachlabs.com/docs/v20.1/release-savepoint#commit-a-transaction-by-releasing-a-retry-savepoint) was followed by [`ROLLBACK`](https://www.cockroachlabs.com/docs/v20.1/rollback-transaction), the `sql.txn.rollback.count` metric would be incremented. This was incorrect, because the transaction had already committed. The metric is no longer incremented in this case. [#60251][#60251] -- Fixed a bug where an error in protecting a record could be incorrectly reported, preventing some backups of very large tables from succeeding. [#60961][#60961] -- Fixed a bug where high-latency global clusters could sometimes fall behind in [resolving timestamps for changefeeds](https://www.cockroachlabs.com/docs/v20.1/create-changefeed#messages). [#60926][#60926] -- Creating [interleaved](https://www.cockroachlabs.com/docs/v20.1/interleave-in-parent) partitioned indexes is now disallowed. Previously, the database would crash when trying to create one. Note that [interleaved tables will be deprecated altogether](https://www.cockroachlabs.com/docs/v20.2/interleave-in-parent#deprecation) in a future release. [#61423][#61423] -- In the Advanced Debugging section of the Admin UI (DB Console), manually enqueueing a range to the garbage collection (GC) queue now properly respects the `SkipShouldQueue` option. This ensures that you can force the GC of a specific range. [#60746][#60746] - -Contributors
- -This release includes 10 merged PRs by 10 authors. - -[#60251]: https://github.com/cockroachdb/cockroach/pull/60251 -[#60746]: https://github.com/cockroachdb/cockroach/pull/60746 -[#60926]: https://github.com/cockroachdb/cockroach/pull/60926 -[#60961]: https://github.com/cockroachdb/cockroach/pull/60961 -[#61423]: https://github.com/cockroachdb/cockroach/pull/61423 diff --git a/src/current/_includes/releases/v20.1/v20.1.14.md b/src/current/_includes/releases/v20.1/v20.1.14.md deleted file mode 100644 index 95a0ef78db1..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.14.md +++ /dev/null @@ -1,34 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -- For a comprehensive summary of features in v20.1, see the [v20.1 GA release notes]({% link releases/v20.1.md %}#v20-1-0). -- To upgrade to v20.1, see [Upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version). - -Bug fixes
- -- Fixed a bug where some import failures would cause tables to stay `OFFLINE` when they should have been brought back to `PUBLIC`. [#61481][#61481] -- Fixed a bug where an invalid tuple comparison using `ANY` was causing an internal error. CockroachDB now returns "unsupported comparison operator". [#61725][#61725] -- Changed the behavior of the `kv.closed_timestamp.target_duration` [cluster setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings) when set to 0. This would make [follower reads](https://www.cockroachlabs.com/docs/v20.1/follower-reads) more aggressive instead of disabling them. Setting `kv.closed_timestamp.target_duration` to 0 will now disable routing requests to follower replicas. [#62442][#62442] -- Fixed a bug where [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) using `AS OF SYSTEM TIME` of tables that included [foreign key constraints](https://www.cockroachlabs.com/docs/v20.1/foreign-key) from backups created by v19.x or earlier would lead to malformed schema metadata. [#62493][#62493] -- Fixed an internal error that could occur during planning when a query used the output of the `RETURNING` clause of an [`UPDATE`](https://www.cockroachlabs.com/docs/v20.1/update), and one or more of the columns in the `RETURNING` clause were from a table specified in the `FROM` clause of the `UPDATE` (i.e., not from the table being updated). [#62964][#62964] -- Dropping a [foreign key](https://www.cockroachlabs.com/docs/v20.1/foreign-key) that was added in the same transaction no longer triggers an internal error. This bug has been present since at least v20.1. [#62881][#62881] -- Fixed a bug where index backfill data might have been missed by [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) in incremental backups. [#63303][#63303] - -Performance improvements
- -- SQL statistics collection has been made more efficient by avoiding an accidental heap allocation per row for some schemas. [#58199][#58199] - -Contributors
- -This release includes 16 merged PRs by 13 authors. - -[#58199]: https://github.com/cockroachdb/cockroach/pull/58199 -[#61481]: https://github.com/cockroachdb/cockroach/pull/61481 -[#61725]: https://github.com/cockroachdb/cockroach/pull/61725 -[#62442]: https://github.com/cockroachdb/cockroach/pull/62442 -[#62493]: https://github.com/cockroachdb/cockroach/pull/62493 -[#62789]: https://github.com/cockroachdb/cockroach/pull/62789 -[#62881]: https://github.com/cockroachdb/cockroach/pull/62881 -[#62964]: https://github.com/cockroachdb/cockroach/pull/62964 -[#63303]: https://github.com/cockroachdb/cockroach/pull/63303 diff --git a/src/current/_includes/releases/v20.1/v20.1.15.md b/src/current/_includes/releases/v20.1/v20.1.15.md deleted file mode 100644 index 9a88b559382..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.15.md +++ /dev/null @@ -1,21 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -- For a comprehensive summary of features in v20.1, see the [v20.1 GA release notes]({% link releases/v20.1.md %}#v20-1-0). -- To upgrade to v20.1, see [Upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version). - -Bug fixes
- -- Fixed a bug where [incremental cluster backups](https://www.cockroachlabs.com/docs/v20.1/backup-and-restore) may have missed data written to tables while they were `OFFLINE`. In practice this can happen if a [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) or [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import) was running across incremental backups. [#63494][#63494] -- Fixed a bug where [cluster restore](https://www.cockroachlabs.com/docs/v20.1/backup-and-restore) would sometimes (very rarely) fail after retrying. [#63773][#63773] -- Fixed a bug where some of the writes of the jobs while they were running may have been missed by the backup. [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import) and [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) jobs are now restored as reverting so that they cleanup after themselves. [#63773][#63773] -- Fixed a rare issue that caused [replica divergence](https://www.cockroachlabs.com/docs/v20.1/architecture/replication-layer). When it occurred, it was reported by the replica consistency checker, typically within 24 hours of occurrence, which would terminate the nodes. [#63475][#63475] - -Contributors
- -This release includes 7 merged PRs by 6 authors. - -[#63475]: https://github.com/cockroachdb/cockroach/pull/63475 -[#63494]: https://github.com/cockroachdb/cockroach/pull/63494 -[#63773]: https://github.com/cockroachdb/cockroach/pull/63773 diff --git a/src/current/_includes/releases/v20.1/v20.1.16.md b/src/current/_includes/releases/v20.1/v20.1.16.md deleted file mode 100644 index 316941a4021..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.16.md +++ /dev/null @@ -1,32 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -This page lists additions and changes in version v20.1.16 since version v20.1.15. - -- For a comprehensive summary of features in v20.1, see the [v20.1 GA release notes]({% link releases/v20.1.md %}#v20-1-0). -- To upgrade to v20.1, see [Upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version). - -Bug fixes
- -- Fixed a correctness bug which caused [partitioned](https://www.cockroachlabs.com/docs/v20.1/partitioning) index scans to omit rows where the value of the first index column was `NULL`. This bug was present since v19.2.0. [#64050][#64050] -- Fixed a bug where multiple concurrent invocations of [`cockroach debug zip`](https://www.cockroachlabs.com/docs/v20.1/cockroach-debug-zip) could lead to cluster instability. This bug was present since CockroachDB v20.1. [#64086][#64086] -- Previously, passwords in SQL statements in telemetry updates and crash reports were anonymized as `*****`. Passwords are now anonymized as `'*****'` so that the SQL statements do not result in parsing errors when executed. [#64347][#64347] -- Fixed a race condition where read-only requests during replica removal (e.g., during range merges or rebalancing) could be evaluated on the removed replica, returning an empty result. [#64377][#64377] -- Fixed a bug where [encryption-at-rest](https://www.cockroachlabs.com/docs/v20.1/encryption#encryption-at-rest-enterprise) metadata was not synced and might become corrupted during a hard reset. [#64498][#64498] - -Performance improvements
- -- The Raft processing goroutine pool's size is now capped at 96. This was observed to prevent instability on large machines (32+ vCPU) in clusters with many ranges (50k+ per node). [#64568][#64568] -- The Raft scheduler now prioritizes the node liveness Range. This was observed to prevent instability on large machines (32+ vCPU) in clusters with many ranges (50k+ per node). [#64568][#64568] - -Contributors
- -This release includes 9 merged PRs by 10 authors. - -[#64050]: https://github.com/cockroachdb/cockroach/pull/64050 -[#64086]: https://github.com/cockroachdb/cockroach/pull/64086 -[#64347]: https://github.com/cockroachdb/cockroach/pull/64347 -[#64377]: https://github.com/cockroachdb/cockroach/pull/64377 -[#64498]: https://github.com/cockroachdb/cockroach/pull/64498 -[#64568]: https://github.com/cockroachdb/cockroach/pull/64568 diff --git a/src/current/_includes/releases/v20.1/v20.1.17.md b/src/current/_includes/releases/v20.1/v20.1.17.md deleted file mode 100644 index 77970c8b24c..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.17.md +++ /dev/null @@ -1,25 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -- For a comprehensive summary of features in v20.1, see the [v20.1 GA release notes]({% link releases/v20.1.md %}#v20-1-0). -- To upgrade to v20.1, see [Upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version). - -Bug fixes
- -- Fixed a race condition where read-write requests during replica removal (for example, during range merges or rebalancing) could be evaluated on the removed replica. These cases would not result in data being written to persistent storage, but could result in errors that should not have been returned. [#64604][#64604] -- Fixed a bug where users of OSS builds of CockroachDB would see "Page Not Found" when loading the DB Console. [#64126][#64126] - -Contributors
- -This release includes 3 merged PRs by 4 authors. -We would like to thank the following contributor from the CockroachDB community: - -- Joshua M. Clulow (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -This page lists additions and changes in v20.1.2 since v20.1.1. - -- For a comprehensive summary of features in v20.1, see the [v20.1 GA release notes]({% link releases/v20.1.md %}#v20-1-0). -- To upgrade to v20.1, see [Upgrade to CockroachDB v20.1](https://www.cockroachlabs.com/docs/v20.1/upgrade-cockroach-version) - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -Bug fixes
- -- Corrected the replicas count for table details in the Admin UI. [#49206][#49206] -- The `rolcanlogin` value for roles is now correctly populated in `pg_roles` and `pg_catalog`. [#49622][#49622] -- Fixed a rare bug in the Pebble storage engine that could lead to storage engine inconsistencies. [#49378][#49378] -- Corrected how engine type is reported in bug reports when using [`cockroach demo`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo). [#49377][#49377] -- Fixed a bug where [`cockroach quit`](https://www.cockroachlabs.com/docs/v20.1/cockroach-quit) would not proceed to perform a hard shutdown when the value passed to `--drain-wait` was very small, but non-zero. This bug existed since v19.1.9, v19.2.7 and v20.1.1. [#49363][#49363] -- Fixed a bug where [`demo node restart`](https://www.cockroachlabs.com/docs/v20.1/cockroach-demo) would not work due to an invalid certificate directory. [#49390][#49390] -- Fixed some benign errors that were being reported as unexpected internal errors by the vectorized execution engine. [#49534][#49534] -- Fixed a rare bug in the Pebble storage engine where keys were being returned out-of-order from large sstable files. [#49602][#49602] -- When run via the [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution), queries with a hash routed in the DistSQL plan no longer return an internal error or incorrect results. [#49624][#49624] -- When run via the [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution), queries that have columns of the [`BYTES`](https://www.cockroachlabs.com/docs/v20.1/bytes) type in the output no longer result in an internal error. [#49384][#49384] -- CockroachDB no longer leaks file descriptors during [GSS authentication](https://www.cockroachlabs.com/docs/v20.1/gssapi_authentication). [#49614][#49614] -- Attempting to perform a full cluster [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) on a backup that did not contain any user data no longer fails. [#49745][#49745] -- Abandoned intents due to failed transaction coordinators are now cleaned up much faster. This resolves a regression in v20.1.0 compared to prior releases. [#49835][#49835] -- Fixed the descriptions for `--socket-dir` and `--socket` in the CLI help. They were incorrect since v20.1.0. [#49906][#49906] -- Adjusted Pebble's out of memory error behavior to match that of the Go runtime in order to make the condition more obvious. [#49874][#49874] -- When performing incremental backups with revision history on a database (or full cluster), and a table in the database was dropped and then other tables were later created, the backup no longer returns an error. [#49925][#49925] -- Fixed an internal planning error for recursive CTEs (`WITH RECURSIVE` expressions) in which the left side of the `UNION ALL` query used in the CTE definition produced zero rows. [#49964][#49964] - -Doc updates
- -- Added a [CockroachCloud Quickstart](https://www.cockroachlabs.com/docs/cockroachcloud/quickstart) on creating and connecting to a 30-day free CockroachCloud cluster and running your first query. [#7454][#7454] -- Updated the [Active Record tutorial](https://www.cockroachlabs.com/docs/v20.1/build-a-ruby-app-with-cockroachdb-activerecord) to use a new CockroachDB adapter version. [#7480][#7480] -- Changed instances of "whitelist"/"blacklist" to "allowlist"/"blocklist" throughout the documentation. [#7479][#7479] -- Updated all mentions of `range_min_size` and `range_max_size` to use the new default values of `134217728` and `536870912`, respectively. [#7449][#7449] -- Updated the [hardware storage recommendations](https://www.cockroachlabs.com/docs/v20.1/recommended-production-settings#storage). [#7514][#7514] -- Revised the node [decommissioning guidance](https://www.cockroachlabs.com/docs/v20.1/remove-nodes). [#7304][#7304] - -Contributors
- -This release includes 30 merged PRs by 20 authors. - -[#49206]: https://github.com/cockroachdb/cockroach/pull/49206 -[#49349]: https://github.com/cockroachdb/cockroach/pull/49349 -[#49363]: https://github.com/cockroachdb/cockroach/pull/49363 -[#49377]: https://github.com/cockroachdb/cockroach/pull/49377 -[#49378]: https://github.com/cockroachdb/cockroach/pull/49378 -[#49384]: https://github.com/cockroachdb/cockroach/pull/49384 -[#49390]: https://github.com/cockroachdb/cockroach/pull/49390 -[#49534]: https://github.com/cockroachdb/cockroach/pull/49534 -[#49602]: https://github.com/cockroachdb/cockroach/pull/49602 -[#49614]: https://github.com/cockroachdb/cockroach/pull/49614 -[#49622]: https://github.com/cockroachdb/cockroach/pull/49622 -[#49624]: https://github.com/cockroachdb/cockroach/pull/49624 -[#49745]: https://github.com/cockroachdb/cockroach/pull/49745 -[#49835]: https://github.com/cockroachdb/cockroach/pull/49835 -[#49874]: https://github.com/cockroachdb/cockroach/pull/49874 -[#49906]: https://github.com/cockroachdb/cockroach/pull/49906 -[#49925]: https://github.com/cockroachdb/cockroach/pull/49925 -[#49964]: https://github.com/cockroachdb/cockroach/pull/49964 -[#7454]: https://github.com/cockroachdb/docs/pull/7454 -[#7480]: https://github.com/cockroachdb/docs/pull/7480 -[#7479]: https://github.com/cockroachdb/docs/pull/7479 -[#7449]: https://github.com/cockroachdb/docs/pull/7449 -[#7514]: https://github.com/cockroachdb/docs/pull/7514 -[#7304]: https://github.com/cockroachdb/docs/pull/7304 diff --git a/src/current/_includes/releases/v20.1/v20.1.3.md b/src/current/_includes/releases/v20.1/v20.1.3.md deleted file mode 100644 index 4357ae4495b..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.3.md +++ /dev/null @@ -1,84 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -Security updates
- -- HTTP endpoints beginning with `/debug/` now require a valid [`admin`](https://www.cockroachlabs.com/docs/v20.1/authorization) login session. [#50487][#50487] - -Enterprise edition changes
- -- [Full cluster restore](https://www.cockroachlabs.com/docs/v20.1/restore#full-cluster) is now more resilient to transient transaction retry errors during restore. [#50004][#50004] -- The default flush interval for [changefeeds](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) that do not specify a `RESOLVED` option is now 5s instead of 200ms to more gracefully handle higher-latency sinks. [#50251][#50251] - -SQL language changes
- -- Previously, using `infinity` evaluated to a negative, i.e., "-292277022365-05-08T08:17:07Z". This has been fixed to be the maximum supported timestamp in PostgreSQL that is not infinity. Likewise, `-infinity` is the smallest supported value. Note this does currently does not behave exactly like `infinity` in PostgreSQL (this is a work in progress and may be resolved later). [#50365][#50365] - -Bug fixes
- -- Previously, `extract(epoch from timestamptz)` from a session time zone not in UTC would return a value which was incorrectly offset by the session time zone. This is now fixed. [#50075][#50075] -- Previously, the parallel importer could get stuck due to a race between emitted import batches and checking for context cancellation (either due to an unforeseen error, or due to explicit context cancallation). This is now fixed. [#50089][#50089] -- Previously, using separate groups for producer and consumer could lead to a situation where consumer would exit (due to an error, or explicit context cancellation) without the producer realizing, leading to a deadlock. Producer and consumer are now correctly linked during data import. [#50089][#50089] -- Casting to width-limited strings now works correctly for strings containing Unicode characters. [#50159][#50159] -- Fixed some cases in which casting a string to a width-limited string array was not truncating the string. [#50168][#50168] -- Fixed a bug in which restarting CockroachDB with the Pebble storage engine after a crash during write-ahead logging could, in some rare cases, return an "unexpected EOF" error. [#50282][#50282] -- Previously, the [Admin UI Statements page](https://www.cockroachlabs.com/docs/v20.1/admin-ui-statements-page) was incorrectly displaying information about whether or not a statement was distributed (it was always `Yes`). This is now fixed. [#50347][#50347] -- Fixed a RocksDB bug that could result in inconsistencies in rare circumstances. [#50397][#50397] -- Fixed a bug that broke the data distribution [Advanced Debug page](https://www.cockroachlabs.com/docs/v20.1/admin-ui-debug-pages) in the Admin UI on clusters that had upgraded from 19.2 to 20.1. [#49987][#49987] -- Previously, when a [changefeed](https://www.cockroachlabs.com/docs/v20.1/change-data-capture) would fail to set up its flows due to a node draining, the changefeed would be marked as failed. These errors are now retryable. [#50088][#50088] - -Performance improvements
- -- CockroachDB now optimizes reading of files when doing backups and storage-level compactions of files. This should deliver a performance improvement for some read-heavy operations on an IOPS-constrained device. [#50105][#50105] -- Limited [`SELECT`](https://www.cockroachlabs.com/docs/v20.1/select-clause) statements now do a better job avoiding unnecessary contention with [`UPDATE`](https://www.cockroachlabs.com/docs/v20.1/update) and [`SELECT FOR UPDATE`](https://www.cockroachlabs.com/docs/v20.1/select-for-update) statements. [#50119][#50119] -- Improved the [optimizer](https://www.cockroachlabs.com/docs/v19.2/cost-based-optimizer)'s estimation of the selectivity of some filters involving a disjunction (`OR`) of predicates over multiple columns. This results in more accurate cardinality estimation and enables the optimizer to choose better query plans in some cases. [#50470][#50470] - -Build changes
- -- Release Docker images are now built on Debian 9.12. [#50482][#50482] - -Doc updates
- -- Updated guidance on [node decommissioning](https://www.cockroachlabs.com/docs/v20.1/remove-nodes). [#7304][#7304] -- Added node density guidance to the [Production Checklist](https://www.cockroachlabs.com/docs/v20.1/recommended-production-settings#node-density-testing-configuration). [#7514][#7514] -- Renamed "whitelist/blacklist" terminology to "allowlist/blocklist". [#7535][#7535] -- Updated the Releases navigation in the sidebar to expose the latest Production and Testing releases. [#7550][#7550] -- Fixed scrollbar visibility on Chrome. [#7487][#7487] - -Contributors
- -This release includes 22 merged PRs by 15 authors. - -[#49987]: https://github.com/cockroachdb/cockroach/pull/49987 -[#50004]: https://github.com/cockroachdb/cockroach/pull/50004 -[#50075]: https://github.com/cockroachdb/cockroach/pull/50075 -[#50088]: https://github.com/cockroachdb/cockroach/pull/50088 -[#50089]: https://github.com/cockroachdb/cockroach/pull/50089 -[#50105]: https://github.com/cockroachdb/cockroach/pull/50105 -[#50119]: https://github.com/cockroachdb/cockroach/pull/50119 -[#50159]: https://github.com/cockroachdb/cockroach/pull/50159 -[#50168]: https://github.com/cockroachdb/cockroach/pull/50168 -[#50216]: https://github.com/cockroachdb/cockroach/pull/50216 -[#50251]: https://github.com/cockroachdb/cockroach/pull/50251 -[#50282]: https://github.com/cockroachdb/cockroach/pull/50282 -[#50347]: https://github.com/cockroachdb/cockroach/pull/50347 -[#50365]: https://github.com/cockroachdb/cockroach/pull/50365 -[#50397]: https://github.com/cockroachdb/cockroach/pull/50397 -[#50470]: https://github.com/cockroachdb/cockroach/pull/50470 -[#50482]: https://github.com/cockroachdb/cockroach/pull/50482 -[#50487]: https://github.com/cockroachdb/cockroach/pull/50487 -[48d02125b]: https://github.com/cockroachdb/cockroach/commit/48d02125b -[#7304]: https://github.com/cockroachdb/docs/pull/7304 -[#7550]: https://github.com/cockroachdb/docs/pull/7550 -[#7535]: https://github.com/cockroachdb/docs/pull/7535 -[#7487]: https://github.com/cockroachdb/docs/pull/7487 -[#7514]: https://github.com/cockroachdb/docs/pull/7514 diff --git a/src/current/_includes/releases/v20.1/v20.1.4.md b/src/current/_includes/releases/v20.1/v20.1.4.md deleted file mode 100644 index 96a7b59e007..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.4.md +++ /dev/null @@ -1,119 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -CockroachDB introduced a critical bug in the v20.1.4 release that affects [`UPSERT`](https://www.cockroachlabs.com/docs/v20.1/upsert) and [`INSERT … ON CONFLICT DO UPDATE SET x = excluded.x`](https://www.cockroachlabs.com/docs/v20.1/insert#on-conflict-clause) statements involving more than 10,000 rows. All deployments running CockroachDB v20.1.4 and v20.1.5 are affected. A fix is included in [v20.1.6]({% link releases/v20.1.md %}#v20-1-6). - -For more information, see [Technical Advisory 54418](https://www.cockroachlabs.com/docs/advisories/a54418). -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -General changes
- -- Links in error messages that point to unimplemented issues now use the Cockroach Labs redirect/short-link server. [#50310][#50310] -- [Schema changes](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes) are now logged in greater detail. [#50373][#50373] - -Enterprise edition changes
- -- [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) now has a new option `skip_missing_sequence_owners` that must be supplied when restoring only the table/sequence that was previously a sequence owner/owned by a table. Additionally, a bug causing ownership relationships to not be remapped after a restore has been fixed. [#51629][#51629] {% comment %}doc{% endcomment %} - -SQL language changes
- -- CockroachDB no longer writes to slow query log unless explicitly enabled. [#50941][#50941] {% comment %}doc{% endcomment %} - -Command-line changes
- -- The new `statement-diag` [`cockroach` command](https://www.cockroachlabs.com/docs/v20.1/cockroach-commands) can now be used to manage statement diagnostics. [#51229][#51229] {% comment %}doc{% endcomment %} -- The `statement-diag` command now shows all times in UTC. [#51457][#51457] {% comment %}doc{% endcomment %} - -Bug fixes
- -- Fixed a bug affecting some [`DROP DATABASE`](https://www.cockroachlabs.com/docs/v20.1/drop-database) schema changes where multiple GC jobs are created, causing the GC job for the database to fail. GC jobs will no longer fail if a table descriptor that has already been deleted by a different GC job is not found. [#50556][#50556] -- Previously, if a full cluster [restore](https://www.cockroachlabs.com/docs/v20.1/restore) failed while restoring the system table data, it would not clean up after itself properly and would leave some [temporary tables](https://www.cockroachlabs.com/docs/v20.1/temporary-tables) public and not dropped. This bug has been fixed. [#50209][#50209] -- Fixed a bug causing a cluster restore to fail when the largest descriptor in the backup was a database. This was typically seen when the last action in backing up a cluster was a [database creation](https://www.cockroachlabs.com/docs/v20.1/create-database). [#50817][#50817] -- Cluster backup would previously appear as [`BACKUP TABLE TO`](https://www.cockroachlabs.com/docs/v20.1/backup) rather than `BACKUP TO` in the [jobs table](https://www.cockroachlabs.com/docs/v20.1/show-jobs). This bug has been fixed. [#50818][#50818] -- Fixed a bug causing a badly timed power outage or a system crash to report an error upon process restart. [#50847][#50847] -- Some `pg_catalog` queries that previously returned an error like "`crdb_internal_vtable_pk` column not allowed" now work again. [#50843][#50843] -- Fixed "column not in input" internal error in some corner cases. [#50859][#50859] -- Fixed a rare bug causing a multi-range [`SELECT FOR UPDATE`](https://www.cockroachlabs.com/docs/v20.1/select-clause) statement containing an `IN` clause to fail to observe a consistent snapshot and violate serializability. [#50816][#50816] -- Fixed regression where [granting privileges](https://www.cockroachlabs.com/docs/v20.1/grant) and [dropping objects](https://www.cockroachlabs.com/docs/v20.1/drop-table) would be slow when performed on a large number of objects due to unnecessary queries for looking up jobs in the `system.jobs` table. Previously, CockroachDB executed a quadratic number of queries based on the number of objects. CockroachDB now executes a linear number of queries based on the number of objects, which significantly improves the speed of dropping multiple objects or granting multiple privileges to a user. [#50923][#50923] -- Previously, CockroachDB could crash when internal memory accounting hit a discrepancy. Now it will report an error instead. [#51014][#51014] -- Improved support for large statement diagnostic bundles. [#51031][#51031] -- CockroachDB now prevents spurious "SimpleQuery not allowed while in extended protocol mode" errors. [#51249][#51249] -- [Renaming](https://www.cockroachlabs.com/docs/v20.1/rename-table) a [temporary table](https://www.cockroachlabs.com/docs/v20.1/temporary-tables) no longer converts it to a persistent table. The table continues to remain temporary after a rename. This patch also prevents users from converting a temporary table to a persistent table by renaming the table with a fully-qualified name and a schema referring to `public`. [#51309][#51309] -- Fixed incorrect results in some cases involving [joins](https://www.cockroachlabs.com/docs/v20.1/joins) on [interleaved tables](https://www.cockroachlabs.com/docs/v20.1/interleave-in-parent) with [limits](https://www.cockroachlabs.com/docs/v20.1/limit-offset). [#51432][#51432] -- [`cockroach dump`](https://www.cockroachlabs.com/docs/v20.1/cockroach-dump) no longer errors out when dumping [temporary tables](https://www.cockroachlabs.com/docs/v20.1/temporary-tables), [views](https://www.cockroachlabs.com/docs/v20.1/views#temporary-views), or [sequences](https://www.cockroachlabs.com/docs/v20.1/create-sequence#temporary-sequences). It either ignores them or throws an informative error if the temporary object is explicitly requested to be dumped via the [CLI](https://www.cockroachlabs.com/docs/v20.1/cockroach-commands). [#51457][#51457] -- Fix a bug causing `cockroach dump` to improperly escape quotes within table comments. [#51510][#51510] -- Fix a bug causing `cockroach dump` to not emit a correct statement for comments on [indexes](https://www.cockroachlabs.com/docs/v20.1/indexes). [#51510][#51510] -- There is a known issue where [`BACKUP`s](https://www.cockroachlabs.com/docs/v20.1/backup) may get stuck when nearly completed. When this happens, we prevent garbage collection of old data from the targets that are being backed up, until the job is cancelled. This change stops the garbage build-up while the `BACKUP` is stuck. [#51519][#51519] -- Previously, CockroachDB could hit an internal error when executing `regexp_replace` [builtin](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators). This bug has been fixed. [#51347][#51347] -- Previously, CockroachDB could hit a "command is too large" error when performing [`UPSERT`](https://www.cockroachlabs.com/docs/v20.1/upsert) operations with many values. This bug has been fixed. [#51626][#51626] -- Fixed a bug that prevented a table from being [dropped](https://www.cockroachlabs.com/docs/v20.1/drop-table) if a user created a [sequence](https://www.cockroachlabs.com/docs/v20.1/create-sequence) owned by the table's column and then dropped the sequence. [#51629][#51629] -- [`DROP DATABASE CASCADE`](https://www.cockroachlabs.com/docs/v20.1/drop-database) now works as expected even when the database has a sequence with an owner in it. [#51629][#51629] -- Fixed a bug causing descriptors to be in an invalid state due to ownership issues. [#51629][#51629] -- Previously, orphaned `system.namespace/system.descriptor` entries were left if a `DROP DATABASE CASCADE` was issued, and the database contained dependency relations. For example, if the database included a [view](https://www.cockroachlabs.com/docs/v20.1/views) that depended on a table in the database, dropping the database would result in an orphaned entry for the view. This bug is now fixed, and cleanup happens as expected. [#51895][#51895] -- CockroachDB now returns proper error messages for [index creation statements](https://www.cockroachlabs.com/docs/v20.1/create-index) that use a column that does not exist. [#51892][#51892] -- Fixed a bug preventing `NULL` index members from being added to [hash-sharded indexes](https://www.cockroachlabs.com/docs/v20.1/indexes#hash-sharded-indexes). [#51906][#51906] -- In earlier testing releases, columns that were members of hash-sharded indexes could not be renamed. Indexes created in prior releases will need to [be dropped](https://www.cockroachlabs.com/docs/v20.1/drop-index) and [recreated](https://www.cockroachlabs.com/docs/v20.1/create-index) to resolve this limitation. [#51906][#51906] -- It is no longer possible for rapid range lease movement to trigger a rare assertion failure under contended workloads. The assertion contained the text: "discovered lock by different transaction than existing lock". [#51869][#51869] -- Fixed bug in the Pebble storage engine that in rare circumstances could construct corrupted store, resulting in a node crash. [#51915][#51915] -- Fixed a bug causing traces collected through the `sql.trace.txn.enable_threshold` setting to be incomplete sometimes. [#51845][#51845] -- Increased the robustness of [restore](https://www.cockroachlabs.com/docs/v20.1/restore) against descriptors which may be in an unexpected state. [#51925][#51925] -- Previously, CockroachDB could encounter benign internal "context canceled" errors when queries were executed by [the vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution). [#51933][#51933] -- Fixed a bug causing [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) jobs to block when finished backing up data. [#52003][#52003] -- Fixed a bug causing [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) jobs to sometimes block at the end of the job when sending its results back if the connection that started the job disconnected. [#52003][#52003] -- Fixed a bug causing CockroachDB to crash on some queries with [merge joins](https://www.cockroachlabs.com/docs/v20.1/joins#merge-joins). [#52046][#52046] -- An unknown condition previously caused CockroachDB to crash with the message "committed txn with writeTooOld err". This condition no longer crashes a node. Instead, an error message is printed to the logs asking for help in the investigation. [#51843][#51843] - -Performance improvements
- -- Introduced a new `server.consistency_check.max_rate` [setting](https://www.cockroachlabs.com/docs/v20.1/cluster-settings), expressed in bytes/seconds, to throttle the rate at which CockroachDB scans through the disk to perform a consistency check. This control is necessary to ensure smooth performance on a cluster with large node sizes, in the 10TB+ range. [#50066][#50066] {% comment %}doc{% endcomment %} - -Contributors
- -This release includes 41 merged PRs by 18 authors. - -[#50066]: https://github.com/cockroachdb/cockroach/pull/50066 -[#50209]: https://github.com/cockroachdb/cockroach/pull/50209 -[#50310]: https://github.com/cockroachdb/cockroach/pull/50310 -[#50373]: https://github.com/cockroachdb/cockroach/pull/50373 -[#50556]: https://github.com/cockroachdb/cockroach/pull/50556 -[#50816]: https://github.com/cockroachdb/cockroach/pull/50816 -[#50817]: https://github.com/cockroachdb/cockroach/pull/50817 -[#50818]: https://github.com/cockroachdb/cockroach/pull/50818 -[#50843]: https://github.com/cockroachdb/cockroach/pull/50843 -[#50847]: https://github.com/cockroachdb/cockroach/pull/50847 -[#50859]: https://github.com/cockroachdb/cockroach/pull/50859 -[#50923]: https://github.com/cockroachdb/cockroach/pull/50923 -[#50941]: https://github.com/cockroachdb/cockroach/pull/50941 -[#51014]: https://github.com/cockroachdb/cockroach/pull/51014 -[#51031]: https://github.com/cockroachdb/cockroach/pull/51031 -[#51229]: https://github.com/cockroachdb/cockroach/pull/51229 -[#51249]: https://github.com/cockroachdb/cockroach/pull/51249 -[#51309]: https://github.com/cockroachdb/cockroach/pull/51309 -[#51347]: https://github.com/cockroachdb/cockroach/pull/51347 -[#51432]: https://github.com/cockroachdb/cockroach/pull/51432 -[#51457]: https://github.com/cockroachdb/cockroach/pull/51457 -[#51510]: https://github.com/cockroachdb/cockroach/pull/51510 -[#51519]: https://github.com/cockroachdb/cockroach/pull/51519 -[#51626]: https://github.com/cockroachdb/cockroach/pull/51626 -[#51629]: https://github.com/cockroachdb/cockroach/pull/51629 -[#51843]: https://github.com/cockroachdb/cockroach/pull/51843 -[#51845]: https://github.com/cockroachdb/cockroach/pull/51845 -[#51869]: https://github.com/cockroachdb/cockroach/pull/51869 -[#51892]: https://github.com/cockroachdb/cockroach/pull/51892 -[#51895]: https://github.com/cockroachdb/cockroach/pull/51895 -[#51906]: https://github.com/cockroachdb/cockroach/pull/51906 -[#51915]: https://github.com/cockroachdb/cockroach/pull/51915 -[#51925]: https://github.com/cockroachdb/cockroach/pull/51925 -[#51933]: https://github.com/cockroachdb/cockroach/pull/51933 -[#52003]: https://github.com/cockroachdb/cockroach/pull/52003 -[#52046]: https://github.com/cockroachdb/cockroach/pull/52046 diff --git a/src/current/_includes/releases/v20.1/v20.1.5.md b/src/current/_includes/releases/v20.1/v20.1.5.md deleted file mode 100644 index cfc632bb010..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.5.md +++ /dev/null @@ -1,61 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -CockroachDB introduced a critical bug in the [v20.1.4 release]({% link releases/v20.1.md %}#v20-1-4) that affects [`UPSERT`](https://www.cockroachlabs.com/docs/v20.1/upsert) and [`INSERT … ON CONFLICT DO UPDATE SET x = excluded.x`](https://www.cockroachlabs.com/docs/v20.1/insert#on-conflict-clause) statements involving more than 10,000 rows. All deployments running CockroachDB v20.1.4 and v20.1.5 are affected. A fix is included in [v20.1.6]({% link releases/v20.1.md %}#v20-1-6). - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -For more information, see [Technical Advisory 54418](https://www.cockroachlabs.com/docs/advisories/a54418). -{{site.data.alerts.end}} - -SQL language changes
- -- Reduced memory used by table scans containing JSON data. [#53318][#53318] - -Bug fixes
- -- Fixed an internal error that could occur when an [aggregate function](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators#aggregate-functions) argument contained [a correlated subquery](https://www.cockroachlabs.com/docs/v20.1/subqueries#correlated-subqueries) with another aggregate function referencing the outer scope. This now returns an appropriate user-friendly error, "aggregate function calls cannot be nested". [#52142][#52142] -- Previously, subtracting months from a [`TIMESTAMP`](https://www.cockroachlabs.com/docs/v20.1/timestamp)/[`DATE`](https://www.cockroachlabs.com/docs/v20.1/date)/[`TIMESTAMPTZ`](https://www.cockroachlabs.com/docs/v20.1/timestamp) whose date value is greater than 28 could subtract an additional year. This bug is now fixed. [#52156][#52156] -- Previously, CockroachDB could return incorrect results on queries that encountered `ReadWithinUncertaintyInterval` errors. This bug is now fixed. [#52045][#52045] -- Fixed instances of slow plans for prepared queries involving [CTEs](https://www.cockroachlabs.com/docs/v20.1/common-table-expressions) or foreign key checks. [#52205][#52205] -- Large write requests no longer have a chance of erroneously throwing a "transaction with sequence has a different value" error. [#52267][#52267] -- Type OIDs in the result metadata were incorrect for the `bit`, `bpchar`, `char(n)`, and `varchar(n)` types, and the corresponding array types. They are now correct. [#52351][#52351] -- CockroachDB now prevents deadlocks on connection close with an open user transaction and [temporary tables](https://www.cockroachlabs.com/docs/v20.1/temporary-tables). [#52326][#52326] -- Fixed a bug that could prevent schema changes for up to 5 minutes when using the `COPY` protocol. [#52455][#52455] -- Executing a large number of statements in a transaction without committing could previously crash a CockroachDB server. This bug is now fixed. [#52402][#52402] -- Fixed a bug causing the temporary object cleaner to get stuck trying to remove objects that it mistakenly thought were temporary. Note that no persistent data was deleted. The temporary cleaner simply returned an error because it thought certain persistent data was temporary. [#52662][#52662] -- Previously, CockroachDB would erroneously restart the execution of empty, unclosed portals after they had been fully exhausted. This bug is now fixed. [#52443][#52443] -- Fixed a bug causing the Google Cloud API client used by [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup), [`RESTORE`](https://www.cockroachlabs.com/docs/v20.1/restore) and [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import) to leak memory when interacting with Google Cloud Storage. [#53229][#53229] -- CockroachDB no longer displays a value for `gc.ttlseconds` if not set. [#52813][#52813] - -Performance improvements
- -- Queries no longer block during planning if cached table statistics have become stale and the new statistics have not yet been loaded. Instead, the stale statistics are used for planning until the new statistics have been loaded. This improves performance because it prevents latency spikes that may occur if there is a delay in loading the new statistics. [#52191][#52191] - -Contributors
- -This release includes 31 merged PRs by 15 authors. - -[#52045]: https://github.com/cockroachdb/cockroach/pull/52045 -[#52142]: https://github.com/cockroachdb/cockroach/pull/52142 -[#52156]: https://github.com/cockroachdb/cockroach/pull/52156 -[#52191]: https://github.com/cockroachdb/cockroach/pull/52191 -[#52205]: https://github.com/cockroachdb/cockroach/pull/52205 -[#52267]: https://github.com/cockroachdb/cockroach/pull/52267 -[#52326]: https://github.com/cockroachdb/cockroach/pull/52326 -[#52351]: https://github.com/cockroachdb/cockroach/pull/52351 -[#52402]: https://github.com/cockroachdb/cockroach/pull/52402 -[#52443]: https://github.com/cockroachdb/cockroach/pull/52443 -[#52455]: https://github.com/cockroachdb/cockroach/pull/52455 -[#52662]: https://github.com/cockroachdb/cockroach/pull/52662 -[#52813]: https://github.com/cockroachdb/cockroach/pull/52813 -[#53229]: https://github.com/cockroachdb/cockroach/pull/53229 -[#53318]: https://github.com/cockroachdb/cockroach/pull/53318 diff --git a/src/current/_includes/releases/v20.1/v20.1.6.md b/src/current/_includes/releases/v20.1/v20.1.6.md deleted file mode 100644 index 8506c8cea00..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.6.md +++ /dev/null @@ -1,59 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -SQL language changes
- -- The concurrency of the evaluation of [`UNION ALL`](https://www.cockroachlabs.com/docs/v20.1/selection-queries#union-combine-two-queries) queries has been reduced. Previously, such queries could crash a server (in extreme cases, due to memory shortage). That bug is now fixed, at the expense of possible minor reduction in performance. [#53444][#53444] - -Bug fixes
- -- The [cluster Node Map](https://www.cockroachlabs.com/docs/v20.1/admin-ui-cluster-overview-page#node-map-enterprise) and the [debug page](https://www.cockroachlabs.com/docs/v20.1/admin-ui-debug-pages) for cluster locality reports are now again available to non-admin users. [#53331][#53331] -- Previously, CockroachDB could return incorrect results when performing `LEFT ANTI` [hash joins](https://www.cockroachlabs.com/docs/v20.1/joins#hash-joins) when the right equality columns formed a key and the query was executed with the [vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution). This bug has been fixed. [#53346][#53346] -- Fixed a rare internal error related to [foreign key checks](https://www.cockroachlabs.com/docs/v20.1/foreign-key). [#53648][#53648] -- CockroachDB could previously crash when evaluating queries containing [window functions](https://www.cockroachlabs.com/docs/v20.1/window-functions) with the `GROUPS` framing mode when `Contributors
- -This release includes 27 merged PRs by 15 authors. - -[#51176]: https://github.com/cockroachdb/cockroach/pull/51176 -[#53331]: https://github.com/cockroachdb/cockroach/pull/53331 -[#53346]: https://github.com/cockroachdb/cockroach/pull/53346 -[#53444]: https://github.com/cockroachdb/cockroach/pull/53444 -[#53561]: https://github.com/cockroachdb/cockroach/pull/53561 -[#53648]: https://github.com/cockroachdb/cockroach/pull/53648 -[#53755]: https://github.com/cockroachdb/cockroach/pull/53755 -[#53806]: https://github.com/cockroachdb/cockroach/pull/53806 -[#53962]: https://github.com/cockroachdb/cockroach/pull/53962 -[#54037]: https://github.com/cockroachdb/cockroach/pull/54037 -[#54075]: https://github.com/cockroachdb/cockroach/pull/54075 -[#54129]: https://github.com/cockroachdb/cockroach/pull/54129 -[#54285]: https://github.com/cockroachdb/cockroach/pull/54285 -[#54288]: https://github.com/cockroachdb/cockroach/pull/54288 -[#54380]: https://github.com/cockroachdb/cockroach/pull/54380 -[#54406]: https://github.com/cockroachdb/cockroach/pull/54406 -[#54418]: https://github.com/cockroachdb/cockroach/pull/54418 diff --git a/src/current/_includes/releases/v20.1/v20.1.7.md b/src/current/_includes/releases/v20.1/v20.1.7.md deleted file mode 100644 index 74ca53548c6..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.7.md +++ /dev/null @@ -1,40 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -Security updates
- -- Fixed a case where connections to Google Cloud storage would ignore the [`--external-io-disable-implicit-credentials`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start#external-io-disable-implicit-credentials) flag to `cockroach start`. [#55091][#55091] - -General changes
- -- Reduced the memory overhead of rangefeeds (i.e., long-lived requests) which reduces the memory overhead for running [`CHANGEFEED`](https://www.cockroachlabs.com/docs/v20.2/stream-data-out-of-cockroachdb-using-changefeeds)s over large tables. [#54632][#54632] - -Bug fixes
- -- Fixed a bug where columns used in an [index](https://www.cockroachlabs.com/docs/v20.1/indexes) which contained the columns of a [foreign key](https://www.cockroachlabs.com/docs/v20.1/foreign-key) as a prefix could lead to all of the index columns being set to _NULL_ or the default value on cascade. [#54543][#54543] -- Fixed a bug causing servers to crash with the message "committed txn with writeTooOld". Versions below 20.1.4 are susceptible to this bug. Versions 20.1.4+ will not crash, but instead print messages to the log files. [#54282][#54282] -- Fixed a rare bug which can lead to index backfills failing in the face of [transaction restarts](https://www.cockroachlabs.com/docs/v20.1/transactions#transaction-retries). [#54859][#54859] -- Fixed a race condition propagating post-query metadata in the [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution). [#55168][#55168] -- Fixed a bug causing nodes running version 20.1 to not be able to serve [follower reads](https://www.cockroachlabs.com/docs/v20.1/follower-reads) in mixed-version clusters running versions 19.2 and 20.1. [#55089][#55089] -- The first timing column in the trace.txt file collected as part of a [statement diagnostics bundle](https://www.cockroachlabs.com/docs/v20.1/explain-analyze#debug-option) has been fixed. - -Contributors
- -This release includes 19 merged PRs by 8 authors. - -[#54282]: https://github.com/cockroachdb/cockroach/pull/54282 -[#54543]: https://github.com/cockroachdb/cockroach/pull/54543 -[#54632]: https://github.com/cockroachdb/cockroach/pull/54632 -[#54859]: https://github.com/cockroachdb/cockroach/pull/54859 -[#55089]: https://github.com/cockroachdb/cockroach/pull/55089 -[#55091]: https://github.com/cockroachdb/cockroach/pull/55091 -[#55168]: https://github.com/cockroachdb/cockroach/pull/55168 diff --git a/src/current/_includes/releases/v20.1/v20.1.8.md b/src/current/_includes/releases/v20.1/v20.1.8.md deleted file mode 100644 index 374f361ce7d..00000000000 --- a/src/current/_includes/releases/v20.1/v20.1.8.md +++ /dev/null @@ -1,38 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -Bug fixes
- -- Fixed a bug where [schema changes](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes), which affect referenced tables, might not have propagated to other nodes. [#55375][#55375] -- Fixed a bug where inscrutable errors were returned on failed [backup creation](https://www.cockroachlabs.com/docs/v20.1/backup). [#54968][#54968] -- Fixed a bug where CockroachDB crashed when [executing a query via the vectorized engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution) when most of the SQL memory (determined via [`--max-sql-memory`](https://www.cockroachlabs.com/docs/v20.1/cockroach-start#flags) startup argument) had already been reserved. [#55458][#55458] -- Fixed a bug where the [`age()`](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators#date-and-time-functions) function did not normalize the duration for large day or H:M:S values in the same way PostgreSQL does. [#55527][#55527] -- Fixed a bug where CockroachDB did not account for all the memory used by the vectorized hash aggregation which could lead to an OOM crash. [#55571][#55571] -- Fixed a bug where using the `MIN`/`MAX` aggregates in a prepared statement did not report the correct [data type](https://www.cockroachlabs.com/docs/v20.1/data-types) size. [#55621][#55621] - -Contributors
- -This release includes 8 merged PRs by 6 authors. -We would like to thank the following contributors from the CockroachDB community: - -- kev (first-time contributor) - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a58932.md %} -{{site.data.alerts.end}} - -{{site.data.alerts.callout_danger}} -{% include /v20.1/alerts/warning-a63162.md %} -{{site.data.alerts.end}} - -Enterprise edition changes
- -- Added a setting to opt in or out of including [SQL statistics](https://www.cockroachlabs.com/docs/v20.1/create-statistics) in [backups](https://www.cockroachlabs.com/docs/v20.1/backup). [#55879][#55879] - -SQL language changes
- -- Parsing [intervals](https://www.cockroachlabs.com/docs/v20.1/interval) with fractional years now produces intervals with no more precision than months, to match the behavior of PostgreSQL. [#56247][#56247] -- Table names are now listed before index names in [`EXPLAIN (DISTSQL)`](https://www.cockroachlabs.com/docs/v20.1/explain) diagram output. Previously, the diagrams used `index@table`, and now they use `table@index`. [#56396][#56396] - -Bug fixes
- -- [Changefeeds](https://www.cockroachlabs.com/docs/v20.1/changefeed-for) were previously incompatible with the [vectorized execution engine](https://www.cockroachlabs.com/docs/v20.1/vectorized-execution), and creating changefeeds with the vectorized engine enabled could cause a server to hang. This could happen in v20.2 releases with `SET vectorize_row_count_threshold=0;`, and in v20.1 releases with `SET vectorize=on`. This bug is now fixed. [#55754][#55754] -- Fixed possible write skew in distributed queries that have both zigzag [joins](https://www.cockroachlabs.com/docs/v20.1/joins) and table readers with the zigzag joins reading keys not read by the table readers. [#55874][#55874] -- CockroachDB previously could return incorrect results when computing [aggregation functions](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators#aggregate-functions) when some of the functions contained a `DISTINCT` clause and some did not. This bug is now fixed. [#55873][#55873] -- CockroachDB previously could incorrectly evaluate the `sqrdiff` function when used as a [window function](https://www.cockroachlabs.com/docs/v20.1/functions-and-operators#window-functions) in some cases. This bug is now fixed. [#55999][#55999] -- Fixed a `top-level relational expression cannot have outer columns` error in some queries that involve `WITH`. [#56086][#56086] -- Fix a bug causing [`IMPORT`](https://www.cockroachlabs.com/docs/v20.1/import)s of malformed Avro records to hang forever. [#56097][#56097] -- Fixed a bug causing CockroachDB to crash when a [`BACKUP`](https://www.cockroachlabs.com/docs/v20.1/backup) query was unable to count the total nodes in the cluster. [#56096][#56096] -- Fixed an error that could occur at the end of a restoration of a backup that had ongoing [schema change jobs](https://www.cockroachlabs.com/docs/v20.1/online-schema-changes). [#56021][#56021] -- Previously, cluster backups created in releases before v20.2 could not be [restored](https://www.cockroachlabs.com/docs/v20.1/restore) in 20.2 clusters, and would produce an error message about failing to restore a system table. This bug is now fixed. [#56024][#56024] -- [Options set on users](https://www.cockroachlabs.com/docs/v20.1/alter-user) (e.g., `ALTER USERContributors
- -This release includes 22 merged PRs by 12 authors. -We would like to thank the following contributors from the CockroachDB community: - -- Max Neverov (first-time contributor) - -EXPLAIN",
- "urls": [
- "/${VERSION}/sql-tuning-with-explain.html"
- ]
- }
- ]
- }
- ]
- },
- {
- "title": "Develop",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/developer-guide-overview.html"
- ]
- },
- {
- "title": "Install a Postgres Client",
- "urls": [
- "/${VERSION}/install-client-drivers.html"
- ]
- },
- {
- "title": "Connect to the Database",
- "urls": [
- "/${VERSION}/connect-to-the-database.html"
- ]
- },
- {
- "title": "Insert Data",
- "urls": [
- "/${VERSION}/insert-data.html"
- ]
- },
- {
- "title": "Query Data",
- "urls": [
- "/${VERSION}/query-data.html"
- ]
- },
- {
- "title": "Update Data",
- "urls": [
- "/${VERSION}/update-data.html"
- ]
- },
- {
- "title": "Delete Data",
- "urls": [
- "/${VERSION}/delete-data.html"
- ]
- },
- {
- "title": "Run Multi-Statement Transactions",
- "urls": [
- "/${VERSION}/run-multi-statement-transactions.html"
- ]
- },
- {
- "title": "Error Handling & Troubleshooting",
- "urls": [
- "/${VERSION}/error-handling-and-troubleshooting.html"
- ]
- },
- {
- "title": "Make Queries Fast",
- "urls": [
- "/${VERSION}/make-queries-fast.html"
- ]
- },
- {
- "title": "Sample Apps",
- "items": [
- {
- "title": "Hello World",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/hello-world-example-apps.html"
- ]
- },
- {
- "title": "Go",
- "urls": [
- "/${VERSION}/build-a-go-app-with-cockroachdb.html",
- "/${VERSION}/build-a-go-app-with-cockroachdb-pq.html",
- "/${VERSION}/build-a-go-app-with-cockroachdb-gorm.html",
- "/${VERSION}/build-a-go-app-with-cockroachdb-upperdb.html"
- ]
- },
- {
- "title": "Python",
- "urls": [
- "/${VERSION}/build-a-python-app-with-cockroachdb.html",
- "/${VERSION}/build-a-python-app-with-cockroachdb-sqlalchemy.html",
- "/${VERSION}/build-a-python-app-with-cockroachdb-django.html"
- ]
- },
- {
- "title": "Ruby",
- "urls": [
- "/${VERSION}/build-a-ruby-app-with-cockroachdb.html",
- "/${VERSION}/build-a-ruby-app-with-cockroachdb-activerecord.html"
- ]
- },
- {
- "title": "Java",
- "urls": [
- "/${VERSION}/build-a-java-app-with-cockroachdb.html",
- "/${VERSION}/build-a-java-app-with-cockroachdb-hibernate.html",
- "/${VERSION}/build-a-java-app-with-cockroachdb-jooq.html"
- ]
- },
- {
- "title": "Node.js",
- "urls": [
- "/${VERSION}/build-a-nodejs-app-with-cockroachdb.html",
- "/${VERSION}/build-a-nodejs-app-with-cockroachdb-sequelize.html"
- ]
- },
- {
- "title": "C++",
- "urls": [
- "/${VERSION}/build-a-c++-app-with-cockroachdb.html"
- ]
- },
- {
- "title": "C# (.NET)",
- "urls": [
- "/${VERSION}/build-a-csharp-app-with-cockroachdb.html"
- ]
- },
- {
- "title": "Clojure",
- "urls": [
- "/${VERSION}/build-a-clojure-app-with-cockroachdb.html"
- ]
- },
- {
- "title": "PHP",
- "urls": [
- "/${VERSION}/build-a-php-app-with-cockroachdb.html"
- ]
- },
- {
- "title": "Rust",
- "urls": [
- "/${VERSION}/build-a-rust-app-with-cockroachdb.html"
- ]
- }
- ]
- },
- {
- "title": "Roach Data",
- "items": [
- {
- "title": "Spring Boot with JDBC",
- "urls": [
- "/${VERSION}/build-a-spring-app-with-cockroachdb-jdbc.html"
- ]
- },
- {
- "title": "Spring Boot with JPA",
- "urls": [
- "/${VERSION}/build-a-spring-app-with-cockroachdb-jpa.html"
- ]
- }
- ]
- },
- {
- "title": "Multi-Region",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/multi-region-overview.html"
- ]
- },
- {
- "title": "Use-Case",
- "urls": [
- "/${VERSION}/multi-region-use-case.html"
- ]
- },
- {
- "title": "Database Schema",
- "urls": [
- "/${VERSION}/multi-region-database.html"
- ]
- },
- {
- "title": "Setup",
- "urls": [
- "/${VERSION}/multi-region-setup.html"
- ]
- },
- {
- "title": "Application",
- "urls": [
- "/${VERSION}/multi-region-application.html"
- ]
- },
- {
- "title": "Deployment",
- "urls": [
- "/${VERSION}/multi-region-deployment.html"
- ]
- }
- ]
- }
- ]
- },
- {
- "title": "Third-Party Database Tools",
- "urls": [
- "/${VERSION}/third-party-database-tools.html"
- ],
- "items": [
- {
- "title": "DBeaver GUI",
- "urls": [
- "/${VERSION}/dbeaver.html"
- ]
- },
- {
- "title": "Flyway Schema Migrations",
- "urls": [
- "/${VERSION}/flyway.html"
- ]
- },
- {
- "title": "IntelliJ IDEA",
- "urls": [
- "/${VERSION}/intellij-idea.html"
- ]
- }
- ]
- }
- ]
- },
- {
- "title": "Deploy",
- "items": [
- {
- "title": "Production Checklist",
- "urls": [
- "/${VERSION}/recommended-production-settings.html"
- ]
- },
- {
- "title": "Topology Patterns",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/topology-patterns.html"
- ]
- },
- {
- "title": "Development",
- "urls": [
- "/${VERSION}/topology-development.html"
- ]
- },
- {
- "title": "Basic Production",
- "urls": [
- "/${VERSION}/topology-basic-production.html"
- ]
- },
- {
- "title": "Geo-Partitioned Replicas",
- "urls": [
- "/${VERSION}/topology-geo-partitioned-replicas.html"
- ]
- },
- {
- "title": "Geo-Partitioned Leaseholders",
- "urls": [
- "/${VERSION}/topology-geo-partitioned-leaseholders.html"
- ]
- },
- {
- "title": "Duplicate Indexes",
- "urls": [
- "/${VERSION}/topology-duplicate-indexes.html"
- ]
- },
- {
- "title": "Follower Reads",
- "urls": [
- "/${VERSION}/topology-follower-reads.html"
- ]
- },
- {
- "title": "Follow-the-Workload",
- "urls": [
- "/${VERSION}/topology-follow-the-workload.html"
- ]
- }
- ]
- },
- {
- "title": "Manual Deployment",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/manual-deployment.html"
- ]
- },
- {
- "title": "On-Premises",
- "urls": [
- "/${VERSION}/deploy-cockroachdb-on-premises.html",
- "/${VERSION}/deploy-cockroachdb-on-premises-insecure.html"
- ]
- },
- {
- "title": "AWS",
- "urls": [
- "/${VERSION}/deploy-cockroachdb-on-aws.html",
- "/${VERSION}/deploy-cockroachdb-on-aws-insecure.html"
- ]
- },
- {
- "title": "Azure",
- "urls": [
- "/${VERSION}/deploy-cockroachdb-on-microsoft-azure.html",
- "/${VERSION}/deploy-cockroachdb-on-microsoft-azure-insecure.html"
- ]
- },
- {
- "title": "Digital Ocean",
- "urls": [
- "/${VERSION}/deploy-cockroachdb-on-digital-ocean.html",
- "/${VERSION}/deploy-cockroachdb-on-digital-ocean-insecure.html"
- ]
- },
- {
- "title": "Google Cloud Platform GCE",
- "urls": [
- "/${VERSION}/deploy-cockroachdb-on-google-cloud-platform.html",
- "/${VERSION}/deploy-cockroachdb-on-google-cloud-platform-insecure.html"
- ]
- }
- ]
- },
- {
- "title": "Orchestrated Deployment",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/orchestration.html"
- ]
- },
- {
- "title": "Kubernetes Single-Cluster Deployment",
- "urls": [
- "/${VERSION}/orchestrate-cockroachdb-with-kubernetes.html",
- "/${VERSION}/orchestrate-cockroachdb-with-kubernetes-insecure.html"
- ]
- },
- {
- "title": "Kubernetes Multi-Cluster Deployment",
- "urls": [
- "/${VERSION}/orchestrate-cockroachdb-with-kubernetes-multi-cluster.html"
- ]
- },
- {
- "title": "Kubernetes Performance Optimization",
- "urls": [
- "/${VERSION}/kubernetes-performance.html"
- ]
- },
- {
- "title": "Docker Swarm Deployment",
- "urls": [
- "/${VERSION}/orchestrate-cockroachdb-with-docker-swarm.html",
- "/${VERSION}/orchestrate-cockroachdb-with-docker-swarm-insecure.html"
- ]
- }
- ]
- },
- {
- "title": "Performance",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/performance.html"
- ]
- },
- {
- "title": "Benchmarking Instructions",
- "urls": [
- "/${VERSION}/performance-benchmarking-with-tpc-c-10-warehouses.html",
- "/${VERSION}/performance-benchmarking-with-tpc-c-1k-warehouses.html",
- "/${VERSION}/performance-benchmarking-with-tpc-c-10k-warehouses.html",
- "/${VERSION}/performance-benchmarking-with-tpc-c-100k-warehouses.html"
- ]
- },
- {
- "title": "Tuning Best Practices",
- "urls": [
- "/${VERSION}/performance-best-practices-overview.html"
- ]
- },
- {
- "title": "Tuning Tutorial",
- "urls": [
- "/${VERSION}/performance-tuning.html",
- "/${VERSION}/performance-tuning-insecure.html"
- ]
- }
- ]
- },
- {
- "title": "Security",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/security-overview.html"
- ]
- },
- {
- "title": "Authentication",
- "urls": [
- "/${VERSION}/authentication.html"
- ]
- },
- {
- "title": "Encryption",
- "urls": [
- "/${VERSION}/encryption.html"
- ]
- },
- {
- "title": "Authorization",
- "urls": [
- "/${VERSION}/authorization.html"
- ]
- },
- {
- "title": "SQL Audit Logging",
- "urls": [
- "/${VERSION}/sql-audit-logging.html"
- ]
- },
- {
- "title": "GSSAPI Authentication",
- "urls": [
- "/${VERSION}/gssapi_authentication.html"
- ]
- }
- ]
- },
- {
- "title": "Monitoring and Alerting",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/monitoring-and-alerting.html"
- ]
- },
- {
- "title": "Enable the Node Map",
- "urls": [
- "/${VERSION}/enable-node-map.html"
- ]
- },
- {
- "title": "Use Prometheus and Alertmanager",
- "urls": [
- "/${VERSION}/monitor-cockroachdb-with-prometheus.html"
- ]
- }
- ]
- },
- {
- "title": "Cluster Maintenance",
- "items": [
- {
- "title": "Upgrade to CockroachDB v20.1",
- "urls": [
- "/${VERSION}/upgrade-cockroach-version.html"
- ]
- },
- {
- "title": "Online Schema Changes",
- "urls": [
- "/${VERSION}/online-schema-changes.html"
- ]
- },
- {
- "title": "Manage Long-Running Queries",
- "urls": [
- "/${VERSION}/manage-long-running-queries.html"
- ]
- },
- {
- "title": "Decommission Nodes",
- "urls": [
- "/${VERSION}/remove-nodes.html"
- ]
- },
- {
- "title": "Back up and Restore Data",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/backup-and-restore.html"
- ]
- },
- {
- "title": "Advanced Options",
- "urls": [
- "/${VERSION}/backup-and-restore-advanced-options.html"
- ]
- }
- ]
- },
- {
- "title": "Create a File Server for IMPORT/BACKUP",
- "urls": [
- "/${VERSION}/create-a-file-server.html"
- ]
- },
- {
- "title": "Rotate Security Certificates",
- "urls": [
- "/${VERSION}/rotate-certificates.html"
- ]
- },
- {
- "title": "Disaster Recovery",
- "urls": [
- "/${VERSION}/disaster-recovery.html"
- ]
- }
- ]
- },
- {
- "title": "Replication Controls",
- "urls": [
- "/${VERSION}/configure-replication-zones.html"
- ]
- },
- {
- "title": "Enterprise Features",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/enterprise-licensing.html"
- ]
- },
- {
- "title": "Table Partitioning",
- "urls": [
- "/${VERSION}/partitioning.html"
- ]
- },
- {
- "title": "Change Data Capture",
- "urls": [
- "/${VERSION}/change-data-capture.html"
- ]
- }
- ]
- }
- ]
- },
- {
- "title": "Migrate",
- "items": [
- {
- "title": "Migration Overview",
- "urls": [
- "/${VERSION}/migration-overview.html"
- ]
- },
- {
- "title": "Migrate from Oracle",
- "urls": [
- "/${VERSION}/migrate-from-oracle.html"
- ]
- },
- {
- "title": "Migrate from Postgres",
- "urls": [
- "/${VERSION}/migrate-from-postgres.html"
- ]
- },
- {
- "title": "Migrate from MySQL",
- "urls": [
- "/${VERSION}/migrate-from-mysql.html"
- ]
- },
- {
- "title": "Migrate from CSV",
- "urls": [
- "/${VERSION}/migrate-from-csv.html"
- ]
- },
- {
- "title": "Migrate from Avro",
- "urls": [
- "/${VERSION}/migrate-from-avro.html"
- ]
- },
- {
- "title": "Import Performance Best Practices",
- "urls": [
- "/${VERSION}/import-performance-best-practices.html"
- ]
- }
+ "title": "Release Info",
+ "urls": [
+ "/releases/v20.1.html"
]
},
{
- "title": "Troubleshoot",
+ "title": "Third-party Tools",
"items": [
{
- "title": "Overview",
- "urls": [
- "/${VERSION}/troubleshooting-overview.html"
- ]
- },
- {
- "title": "Common Errors",
- "urls": [
- "/${VERSION}/common-errors.html"
- ]
- },
- {
- "title": "Troubleshoot Cluster Setup",
- "urls": [
- "/${VERSION}/cluster-setup-troubleshooting.html"
- ]
- },
- {
- "title": "Troubleshoot Query Behavior",
- "urls": [
- "/${VERSION}/query-behavior-troubleshooting.html"
- ]
- },
- {
- "title": "Understand Debug Logs",
- "urls": [
- "/${VERSION}/debug-and-error-logs.html"
- ]
- },
- {
- "title": "Replication Reports",
- "urls": [
- "/${VERSION}/query-replication-reports.html"
- ]
- },
- {
- "title": "Support Resources",
+ "title": "DBeaver",
"urls": [
- "/${VERSION}/support-resources.html"
+ "/${VERSION}/dbeaver.html"
]
},
{
- "title": "File an Issue",
+ "title": "IntelliJ IDEA",
"urls": [
- "/${VERSION}/file-an-issue.html"
+ "/${VERSION}/intellij-idea.html"
]
}
]
},
{
- "title": "Reference",
- "items": [
- {
- "title": "Architecture",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/architecture/overview.html"
- ]
- },
- {
- "title": "SQL Layer",
- "urls": [
- "/${VERSION}/architecture/sql-layer.html"
- ]
- },
- {
- "title": "Transaction Layer",
- "urls": [
- "/${VERSION}/architecture/transaction-layer.html"
- ]
- },
- {
- "title": "Distribution Layer",
- "urls": [
- "/${VERSION}/architecture/distribution-layer.html"
- ]
- },
- {
- "title": "Replication Layer",
- "urls": [
- "/${VERSION}/architecture/replication-layer.html"
- ]
- },
- {
- "title": "Storage Layer",
- "urls": [
- "/${VERSION}/architecture/storage-layer.html"
- ]
- },
- {
- "title": "Life of a Distributed Transaction",
- "urls": [
- "/${VERSION}/architecture/life-of-a-distributed-transaction.html"
- ]
- },
- {
- "title": "Reads and Writes Overview",
- "urls": [
- "/${VERSION}/architecture/reads-and-writes-overview.html"
- ]
- }
- ]
- },
- {
- "title": "SQL",
- "items": [
- {
- "title": "PostgreSQL Compatibility",
- "urls": [
- "/${VERSION}/postgresql-compatibility.html"
- ]
- },
- {
- "title": "Client Connection Parameters",
- "urls": [
- "/${VERSION}/connection-parameters.html"
- ]
- },
- {
- "title": "SQL Best Practices",
- "urls": [
- "/${VERSION}/performance-best-practices-overview.html"
- ]
- },
- {
- "title": "SQL Feature Support",
- "urls": [
- "/${VERSION}/sql-feature-support.html"
- ]
- },
- {
- "title": "SQL Statements",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/sql-statements.html"
- ]
- },
- {
- "title": "ADD COLUMN",
- "urls": [
- "/${VERSION}/add-column.html"
- ]
- },
- {
- "title": "ADD CONSTRAINT",
- "urls": [
- "/${VERSION}/add-constraint.html"
- ]
- },
- {
- "title": "ALTER COLUMN",
- "urls": [
- "/${VERSION}/alter-column.html"
- ]
- },
- {
- "title": "ALTER DATABASE",
- "urls": [
- "/${VERSION}/alter-database.html"
- ]
- },
- {
- "title": "ALTER INDEX",
- "urls": [
- "/${VERSION}/alter-index.html"
- ]
- },
- {
- "title": "ALTER PARTITION (Enterprise)",
- "urls": [
- "/${VERSION}/alter-partition.html"
- ]
- },
- {
- "title": "ALTER PRIMARY KEY",
- "urls": [
- "/${VERSION}/alter-primary-key.html"
- ]
- },
- {
- "title": "ALTER RANGE",
- "urls": [
- "/${VERSION}/alter-range.html"
- ]
- },
- {
- "title": "ALTER ROLE",
- "urls": [
- "/${VERSION}/alter-role.html"
- ]
- },
- {
- "title": "ALTER SEQUENCE",
- "urls": [
- "/${VERSION}/alter-sequence.html"
- ]
- },
- {
- "title": "ALTER TABLE",
- "urls": [
- "/${VERSION}/alter-table.html"
- ]
- },
- {
- "title": "ALTER USER",
- "urls": [
- "/${VERSION}/alter-user.html"
- ]
- },
- {
- "title": "EXPERIMENTAL_AUDIT",
- "urls": [
- "/${VERSION}/experimental-audit.html"
- ]
- },
- {
- "title": "ALTER VIEW",
- "urls": [
- "/${VERSION}/alter-view.html"
- ]
- },
- {
- "title": "BACKUP (Enterprise)",
- "urls": [
- "/${VERSION}/backup.html"
- ]
- },
- {
- "title": "BEGIN",
- "urls": [
- "/${VERSION}/begin-transaction.html"
- ]
- },
- {
- "title": "CANCEL JOB",
- "urls": [
- "/${VERSION}/cancel-job.html"
- ]
- },
- {
- "title": "CANCEL QUERY",
- "urls": [
- "/${VERSION}/cancel-query.html"
- ]
- },
- {
- "title": "CANCEL SESSION",
- "urls": [
- "/${VERSION}/cancel-session.html"
- ]
- },
- {
- "title": "COMMENT ON",
- "urls": [
- "/${VERSION}/comment-on.html"
- ]
- },
- {
- "title": "COMMIT",
- "urls": [
- "/${VERSION}/commit-transaction.html"
- ]
- },
- {
- "title": "CONFIGURE ZONE",
- "urls": [
- "/${VERSION}/configure-zone.html"
- ]
- },
- {
- "title": "CREATE CHANGEFEED (Enterprise)",
- "urls": [
- "/${VERSION}/create-changefeed.html"
- ]
- },
- {
- "title": "CREATE DATABASE",
- "urls": [
- "/${VERSION}/create-database.html"
- ]
- },
- {
- "title": "CREATE INDEX",
- "urls": [
- "/${VERSION}/create-index.html"
- ]
- },
- {
- "title": "CREATE ROLE",
- "urls": [
- "/${VERSION}/create-role.html"
- ]
- },
- {
- "title": "CREATE SEQUENCE",
- "urls": [
- "/${VERSION}/create-sequence.html"
- ]
- },
- {
- "title": "CREATE STATISTICS",
- "urls": [
- "/${VERSION}/create-statistics.html"
- ]
- },
- {
- "title": "CREATE TABLE",
- "urls": [
- "/${VERSION}/create-table.html"
- ]
- },
- {
- "title": "CREATE TABLE AS",
- "urls": [
- "/${VERSION}/create-table-as.html"
- ]
- },
- {
- "title": "CREATE USER",
- "urls": [
- "/${VERSION}/create-user.html"
- ]
- },
- {
- "title": "CREATE VIEW",
- "urls": [
- "/${VERSION}/create-view.html"
- ]
- },
- {
- "title": "DELETE",
- "urls": [
- "/${VERSION}/delete.html"
- ]
- },
- {
- "title": "DROP COLUMN",
- "urls": [
- "/${VERSION}/drop-column.html"
- ]
- },
- {
- "title": "DROP CONSTRAINT",
- "urls": [
- "/${VERSION}/drop-constraint.html"
- ]
- },
- {
- "title": "DROP DATABASE",
- "urls": [
- "/${VERSION}/drop-database.html"
- ]
- },
- {
- "title": "DROP INDEX",
- "urls": [
- "/${VERSION}/drop-index.html"
- ]
- },
- {
- "title": "DROP ROLE",
- "urls": [
- "/${VERSION}/drop-role.html"
- ]
- },
- {
- "title": "DROP SEQUENCE",
- "urls": [
- "/${VERSION}/drop-sequence.html"
- ]
- },
- {
- "title": "DROP TABLE",
- "urls": [
- "/${VERSION}/drop-table.html"
- ]
- },
- {
- "title": "DROP USER",
- "urls": [
- "/${VERSION}/drop-user.html"
- ]
- },
- {
- "title": "DROP VIEW",
- "urls": [
- "/${VERSION}/drop-view.html"
- ]
- },
- {
- "title": "EXPERIMENTAL CHANGEFEED FOR",
- "urls": [
- "/${VERSION}/changefeed-for.html"
- ]
- },
- {
- "title": "EXPLAIN",
- "urls": [
- "/${VERSION}/explain.html"
- ]
- },
- {
- "title": "EXPLAIN ANALYZE",
- "urls": [
- "/${VERSION}/explain-analyze.html"
- ]
- },
- {
- "title": "EXPORT (Enterprise)",
- "urls": [
- "/${VERSION}/export.html"
- ]
- },
- {
- "title": "GRANT <privileges>",
- "urls": [
- "/${VERSION}/grant.html"
- ]
- },
- {
- "title": "GRANT <roles>",
- "urls": [
- "/${VERSION}/grant-roles.html"
- ]
- },
- {
- "title": "IMPORT",
- "urls": [
- "/${VERSION}/import.html"
- ]
- },
- {
- "title": "IMPORT INTO",
- "urls": [
- "/${VERSION}/import-into.html"
- ]
- },
- {
- "title": "INSERT",
- "urls": [
- "/${VERSION}/insert.html"
- ]
- },
- {
- "title": "PARTITION BY (Enterprise)",
- "urls": [
- "/${VERSION}/partition-by.html"
- ]
- },
- {
- "title": "PAUSE JOB",
- "urls": [
- "/${VERSION}/pause-job.html"
- ]
- },
- {
- "title": "RENAME COLUMN",
- "urls": [
- "/${VERSION}/rename-column.html"
- ]
- },
- {
- "title": "RENAME CONSTRAINT",
- "urls": [
- "/${VERSION}/rename-constraint.html"
- ]
- },
- {
- "title": "RENAME DATABASE",
- "urls": [
- "/${VERSION}/rename-database.html"
- ]
- },
- {
- "title": "RENAME INDEX",
- "urls": [
- "/${VERSION}/rename-index.html"
- ]
- },
- {
- "title": "RENAME TABLE",
- "urls": [
- "/${VERSION}/rename-table.html"
- ]
- },
- {
- "title": "RENAME SEQUENCE",
- "urls": [
- "/${VERSION}/rename-sequence.html"
- ]
- },
- {
- "title": "RELEASE SAVEPOINT",
- "urls": [
- "/${VERSION}/release-savepoint.html"
- ]
- },
- {
- "title": "RESET <session variable>",
- "urls": [
- "/${VERSION}/reset-vars.html"
- ]
- },
- {
- "title": "RESET CLUSTER SETTING",
- "urls": [
- "/${VERSION}/reset-cluster-setting.html"
- ]
- },
- {
- "title": "RESTORE (Enterprise)",
- "urls": [
- "/${VERSION}/restore.html"
- ]
- },
- {
- "title": "RESUME JOB",
- "urls": [
- "/${VERSION}/resume-job.html"
- ]
- },
- {
- "title": "REVOKE <privileges>",
- "urls": [
- "/${VERSION}/revoke.html"
- ]
- },
- {
- "title": "REVOKE <roles>",
- "urls": [
- "/${VERSION}/revoke-roles.html"
- ]
- },
- {
- "title": "ROLLBACK",
- "urls": [
- "/${VERSION}/rollback-transaction.html"
- ]
- },
- {
- "title": "SAVEPOINT",
- "urls": [
- "/${VERSION}/savepoint.html"
- ]
- },
- {
- "title": "SELECT",
- "urls": [
- "/${VERSION}/select-clause.html"
- ]
- },
- {
- "title": "SELECT FOR UPDATE",
- "urls": [
- "/${VERSION}/select-for-update.html"
- ]
- },
- {
- "title": "SET <session variable>",
- "urls": [
- "/${VERSION}/set-vars.html"
- ]
- },
- {
- "title": "SET CLUSTER SETTING",
- "urls": [
- "/${VERSION}/set-cluster-setting.html"
- ]
- },
- {
- "title": "SET TRANSACTION",
- "urls": [
- "/${VERSION}/set-transaction.html"
- ]
- },
- {
- "title": "SHOW <session variables>",
- "urls": [
- "/${VERSION}/show-vars.html"
- ]
- },
- {
- "title": "SHOW BACKUP",
- "urls": [
- "/${VERSION}/show-backup.html"
- ]
- },
- {
- "title": "SHOW CLUSTER SETTING",
- "urls": [
- "/${VERSION}/show-cluster-setting.html"
- ]
- },
- {
- "title": "SHOW COLUMNS",
- "urls": [
- "/${VERSION}/show-columns.html"
- ]
- },
- {
- "title": "SHOW CONSTRAINTS",
- "urls": [
- "/${VERSION}/show-constraints.html"
- ]
- },
- {
- "title": "SHOW CREATE",
- "urls": [
- "/${VERSION}/show-create.html"
- ]
- },
- {
- "title": "SHOW DATABASES",
- "urls": [
- "/${VERSION}/show-databases.html"
- ]
- },
- {
- "title": "SHOW GRANTS",
- "urls": [
- "/${VERSION}/show-grants.html"
- ]
- },
- {
- "title": "SHOW INDEX",
- "urls": [
- "/${VERSION}/show-index.html"
- ]
- },
- {
- "title": "SHOW JOBS",
- "urls": [
- "/${VERSION}/show-jobs.html"
- ]
- },
- {
- "title": "SHOW LOCALITY",
- "urls": [
- "/${VERSION}/show-locality.html"
- ]
- },
- {
- "title": "SHOW PARTITIONS (Enterprise)",
- "urls": [
- "/${VERSION}/show-partitions.html"
- ]
- },
- {
- "title": "SHOW QUERIES",
- "urls": [
- "/${VERSION}/show-queries.html"
- ]
- },
- {
- "title": "SHOW RANGES",
- "urls": [
- "/${VERSION}/show-ranges.html"
- ]
- },
- {
- "title": "SHOW RANGE FOR ROW",
- "urls": [
- "/${VERSION}/show-range-for-row.html"
- ]
- },
- {
- "title": "SHOW ROLES",
- "urls": [
- "/${VERSION}/show-roles.html"
- ]
- },
- {
- "title": "SHOW SCHEMAS",
- "urls": [
- "/${VERSION}/show-schemas.html"
- ]
- },
- {
- "title": "SHOW SEQUENCES",
- "urls": [
- "/${VERSION}/show-sequences.html"
- ]
- },
- {
- "title": "SHOW SESSIONS",
- "urls": [
- "/${VERSION}/show-sessions.html"
- ]
- },
- {
- "title": "SHOW STATISTICS",
- "urls": [
- "/${VERSION}/show-statistics.html"
- ]
- },
- {
- "title": "SHOW SAVEPOINT STATUS",
- "urls": [
- "/${VERSION}/show-savepoint-status.html"
- ]
- },
- {
- "title": "SHOW TABLES",
- "urls": [
- "/${VERSION}/show-tables.html"
- ]
- },
- {
- "title": "SHOW TRACE FOR SESSION",
- "urls": [
- "/${VERSION}/show-trace.html"
- ]
- },
- {
- "title": "SHOW USERS",
- "urls": [
- "/${VERSION}/show-users.html"
- ]
- },
- {
- "title": "SHOW ZONE CONFIGURATIONS",
- "urls": [
- "/${VERSION}/show-zone-configurations.html"
- ]
- },
- {
- "title": "SPLIT AT",
- "urls": [
- "/${VERSION}/split-at.html"
- ]
- },
- {
- "title": "TRUNCATE",
- "urls": [
- "/${VERSION}/truncate.html"
- ]
- },
- {
- "title": "UNSPLIT AT",
- "urls": [
- "/${VERSION}/unsplit-at.html"
- ]
- },
- {
- "title": "UPDATE",
- "urls": [
- "/${VERSION}/update.html"
- ]
- },
- {
- "title": "UPSERT",
- "urls": [
- "/${VERSION}/upsert.html"
- ]
- },
- {
- "title": "VALIDATE CONSTRAINT",
- "urls": [
- "/${VERSION}/validate-constraint.html"
- ]
- }
- ]
- },
- {
- "title": "Data Types",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/data-types.html"
- ]
- },
- {
- "title": "ARRAY",
- "urls": [
- "/${VERSION}/array.html"
- ]
- },
- {
- "title": "BIT",
- "urls": [
- "/${VERSION}/bit.html"
- ]
- },
- {
- "title": "BOOL",
- "urls": [
- "/${VERSION}/bool.html"
- ]
- },
- {
- "title": "BYTES",
- "urls": [
- "/${VERSION}/bytes.html"
- ]
- },
- {
- "title": "COLLATE",
- "urls": [
- "/${VERSION}/collate.html"
- ]
- },
- {
- "title": "DATE",
- "urls": [
- "/${VERSION}/date.html"
- ]
- },
- {
- "title": "DECIMAL",
- "urls": [
- "/${VERSION}/decimal.html"
- ]
- },
- {
- "title": "FLOAT",
- "urls": [
- "/${VERSION}/float.html"
- ]
- },
- {
- "title": "INET",
- "urls": [
- "/${VERSION}/inet.html"
- ]
- },
- {
- "title": "INT",
- "urls": [
- "/${VERSION}/int.html"
- ]
- },
- {
- "title": "INTERVAL",
- "urls": [
- "/${VERSION}/interval.html"
- ]
- },
- {
- "title": "JSONB",
- "urls": [
- "/${VERSION}/jsonb.html"
- ]
- },
- {
- "title": "SERIAL",
- "urls": [
- "/${VERSION}/serial.html"
- ]
- },
- {
- "title": "STRING",
- "urls": [
- "/${VERSION}/string.html"
- ]
- },
- {
- "title": "TIME",
- "urls": [
- "/${VERSION}/time.html"
- ]
- },
- {
- "title": "TIMESTAMP",
- "urls": [
- "/${VERSION}/timestamp.html"
- ]
- },
- {
- "title": "UUID",
- "urls": [
- "/${VERSION}/uuid.html"
- ]
- }
- ]
- },
- {
- "title": "Constraints",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/constraints.html"
- ]
- },
- {
- "title": "Check",
- "urls": [
- "/${VERSION}/check.html"
- ]
- },
- {
- "title": "Default Value",
- "urls": [
- "/${VERSION}/default-value.html"
- ]
- },
- {
- "title": "Foreign Key",
- "urls": [
- "/${VERSION}/foreign-key.html"
- ]
- },
- {
- "title": "Not Null",
- "urls": [
- "/${VERSION}/not-null.html"
- ]
- },
- {
- "title": "Primary Key",
- "urls": [
- "/${VERSION}/primary-key.html"
- ]
- },
- {
- "title": "Unique",
- "urls": [
- "/${VERSION}/unique.html"
- ]
- }
- ]
- },
- {
- "title": "Functions and Operators",
- "urls": [
- "/${VERSION}/functions-and-operators.html"
- ]
- },
- {
- "title": "SQL Syntax",
- "items": [
- {
- "title": "Full SQL Grammar",
- "urls": [
- "/${VERSION}/sql-grammar.html"
- ]
- },
- {
- "title": "Keywords & Identifiers",
- "urls": [
- "/${VERSION}/keywords-and-identifiers.html"
- ]
- },
- {
- "title": "Constants",
- "urls": [
- "/${VERSION}/sql-constants.html"
- ]
- },
- {
- "title": "Selection Queries",
- "urls": [
- "/${VERSION}/selection-queries.html"
- ]
- },
- {
- "title": "Ordering Query Results",
- "urls": [
- "/${VERSION}/query-order.html"
- ]
- },
- {
- "title": "Limiting Query Results",
- "urls": [
- "/${VERSION}/limit-offset.html"
- ]
- },
- {
- "title": "Table Expressions",
- "urls": [
- "/${VERSION}/table-expressions.html"
- ]
- },
- {
- "title": "Common Table Expressions",
- "urls": [
- "/${VERSION}/common-table-expressions.html"
- ]
- },
- {
- "title": "Join Expressions",
- "urls": [
- "/${VERSION}/joins.html"
- ]
- },
- {
- "title": "Computed Columns",
- "urls": [
- "/${VERSION}/computed-columns.html"
- ]
- },
- {
- "title": "Scalar Expressions",
- "urls": [
- "/${VERSION}/scalar-expressions.html"
- ]
- },
- {
- "title": "Subqueries",
- "urls": [
- "/${VERSION}/subqueries.html"
- ]
- },
- {
- "title": "Temporary Tables",
- "urls": [
- "/${VERSION}/temporary-tables.html"
- ]
- },
- {
- "title": "Name Resolution",
- "urls": [
- "/${VERSION}/sql-name-resolution.html"
- ]
- },
- {
- "title": "AS OF SYSTEM TIME",
- "urls": [
- "/${VERSION}/as-of-system-time.html"
- ]
- },
- {
- "title": "NULL Handling",
- "urls": [
- "/${VERSION}/null-handling.html"
- ]
- }
- ]
- },
- {
- "title": "Transactions",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/transactions.html"
- ]
- },
- {
- "title": "Advanced Client-side Transaction Retries",
- "urls": [
- "/${VERSION}/advanced-client-side-transaction-retries.html"
- ]
- }
- ]
- },
- {
- "title": "Views",
- "urls": [
- "/${VERSION}/views.html"
- ]
- },
- {
- "title": "Window Functions",
- "urls": [
- "/${VERSION}/window-functions.html"
- ]
- },
- {
- "title": "Performance Optimization",
- "items": [
- {
- "title": "SQL Best Practices",
- "urls": [
- "/${VERSION}/performance-best-practices-overview.html"
- ]
- },
- {
- "title": "Indexes",
- "urls": [
- "/${VERSION}/indexes.html"
- ]
- },
- {
- "title": "Inverted Indexes",
- "urls": [
- "/${VERSION}/inverted-indexes.html"
- ]
- },
- {
- "title": "Column Families",
- "urls": [
- "/${VERSION}/column-families.html"
- ]
- },
- {
- "title": "Interleaved Tables",
- "urls": [
- "/${VERSION}/interleave-in-parent.html"
- ]
- },
- {
- "title": "Cost-Based Optimizer",
- "urls": [
- "/${VERSION}/cost-based-optimizer.html"
- ]
- },
- {
- "title": "Vectorized Execution",
- "urls": [
- "/${VERSION}/vectorized-execution.html"
- ]
- }
- ]
- },
- {
- "title": "Information Schema",
- "urls": [
- "/${VERSION}/information-schema.html"
- ]
- },
- {
- "title": "Experimental Features",
- "urls": [
- "/${VERSION}/experimental-features.html"
- ]
- }
- ]
- },
- {
- "title": "CLI",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/cockroach-commands.html"
- ]
- },
- {
- "title": "cockroach start",
- "urls": [
- "/${VERSION}/cockroach-start.html"
- ]
- },
- {
- "title": "cockroach init",
- "urls": [
- "/${VERSION}/cockroach-init.html"
- ]
- },
- {
- "title": "cockroach start-single-node",
- "urls": [
- "/${VERSION}/cockroach-start-single-node.html"
- ]
- },
- {
- "title": "cockroach cert",
- "urls": [
- "/${VERSION}/cockroach-cert.html"
- ]
- },
- {
- "title": "cockroach quit",
- "urls": [
- "/${VERSION}/cockroach-quit.html"
- ]
- },
- {
- "title": "cockroach sql",
- "urls": [
- "/${VERSION}/cockroach-sql.html"
- ]
- },
- {
- "title": "cockroach sqlfmt",
- "urls": [
- "/${VERSION}/cockroach-sqlfmt.html"
- ]
- },
- {
- "title": "cockroach node",
- "urls": [
- "/${VERSION}/cockroach-node.html"
- ]
- },
- {
- "title": "cockroach nodelocal upload",
- "urls": [
- "/${VERSION}/cockroach-nodelocal-upload.html"
- ]
- },
- {
- "title": "cockroach auth-session",
- "urls": [
- "/${VERSION}/cockroach-auth-session.html"
- ]
- },
- {
- "title": "cockroach dump",
- "urls": [
- "/${VERSION}/cockroach-dump.html"
- ]
- },
- {
- "title": "cockroach demo",
- "urls": [
- "/${VERSION}/cockroach-demo.html"
- ]
- },
- {
- "title": "cockroach debug ballast",
- "urls": [
- "/${VERSION}/cockroach-debug-ballast.html"
- ]
- },
- {
- "title": "cockroach debug encryption-active-key",
- "urls": [
- "/${VERSION}/cockroach-debug-encryption-active-key.html"
- ]
- },
- {
- "title": "cockroach debug merge-logs",
- "urls": [
- "/${VERSION}/cockroach-debug-merge-logs.html"
- ]
- },
- {
- "title": "cockroach debug zip",
- "urls": [
- "/${VERSION}/cockroach-debug-zip.html"
- ]
- },
- {
- "title": "cockroach statement-diag",
- "urls": [
- "/${VERSION}/cockroach-statement-diag.html"
- ]
- },
- {
- "title": "cockroach gen",
- "urls": [
- "/${VERSION}/cockroach-gen.html"
- ]
- },
- {
- "title": "cockroach version",
- "urls": [
- "/${VERSION}/cockroach-version.html"
- ]
- },
- {
- "title": "cockroach workload",
- "urls": [
- "/${VERSION}/cockroach-workload.html"
- ]
- }
- ]
- },
- {
- "title": "Cluster Settings",
- "items": [
- {
- "title": "Cluster Settings Overview",
- "urls": [
- "/${VERSION}/cluster-settings.html"
- ]
- },
- {
- "title": "Cost-Based Optimizer",
- "urls": [
- "/${VERSION}/cost-based-optimizer.html"
- ]
- },
- {
- "title": "Follower Reads",
- "urls": [
- "/${VERSION}/follower-reads.html"
- ]
- },
- {
- "title": "Load-Based Splitting",
- "urls": [
- "/${VERSION}/load-based-splitting.html"
- ]
- },
- {
- "title": "Range Merges",
- "urls": [
- "/${VERSION}/range-merges.html"
- ]
- }
- ]
- },
- {
- "title": "Admin UI",
- "items": [
- {
- "title": "Admin UI Overview",
- "urls": [
- "/${VERSION}/admin-ui-overview.html"
- ]
- },
- {
- "title": "Cluster Overview Page",
- "urls": [
- "/${VERSION}/admin-ui-cluster-overview-page.html"
- ]
- },
- {
- "title": "Metrics Dashboards",
- "items": [
- {
- "title": "Overview Dashboard",
- "urls": [
- "/${VERSION}/admin-ui-overview-dashboard.html"
- ]
- },
- {
- "title": "Hardware Dashboard",
- "urls": [
- "/${VERSION}/admin-ui-hardware-dashboard.html"
- ]
- },
- {
- "title": "Runtime Dashboard",
- "urls": [
- "/${VERSION}/admin-ui-runtime-dashboard.html"
- ]
- },
- {
- "title": "SQL Dashboard",
- "urls": [
- "/${VERSION}/admin-ui-sql-dashboard.html"
- ]
- },
- {
- "title": "Storage Dashboard",
- "urls": [
- "/${VERSION}/admin-ui-storage-dashboard.html"
- ]
- },
- {
- "title": "Replication Dashboard",
- "urls": [
- "/${VERSION}/admin-ui-replication-dashboard.html"
- ]
- },
- {
- "title": "Changefeeds Dashboard",
- "urls": [
- "/${VERSION}/admin-ui-cdc-dashboard.html"
- ]
- },
- {
- "title": "Custom Chart",
- "urls": [
- "/${VERSION}/admin-ui-custom-chart-debug-page.html"
- ]
- }
- ]
- },
- {
- "title": "Databases Page",
- "urls": [
- "/${VERSION}/admin-ui-databases-page.html"
- ]
- },
- {
- "title": "Statements Page",
- "urls": [
- "/${VERSION}/admin-ui-statements-page.html"
- ]
- },
- {
- "title": "Network Latency Page",
- "urls": [
- "/${VERSION}/admin-ui-network-latency-page.html"
- ]
- },
- {
- "title": "Jobs Page",
- "urls": [
- "/${VERSION}/admin-ui-jobs-page.html"
- ]
- },
- {
- "title": "Advanced Debug Page",
- "urls": [
- "/${VERSION}/admin-ui-debug-pages.html"
- ]
- }
- ]
- },
- {
- "title": "Third-Party Database Tools",
- "urls": [
- "/${VERSION}/third-party-database-tools.html"
- ]
- },
- {
- "title": "Diagnostics Reporting",
- "urls": [
- "/${VERSION}/diagnostics-reporting.html"
- ]
- },
- {
- "title": "Sample Applications",
- "items": [
- {
- "title": "MovR: Vehicle-Sharing App",
- "urls": [
- "/${VERSION}/movr.html"
- ]
- }
- ]
- }
+ "title": "SQL Shell",
+ "urls": [
+ "/${VERSION}/cockroach-sql.html"
]
},
{
- "title": "FAQs",
- "items": [
- {
- "title": "Product FAQs",
- "urls": [
- "/${VERSION}/frequently-asked-questions.html"
- ]
- },
- {
- "title": "SQL FAQs",
- "urls": [
- "/${VERSION}/sql-faqs.html"
- ]
- },
- {
- "title": "Operational FAQs",
- "urls": [
- "/${VERSION}/operational-faqs.html"
- ]
- },
- {
- "title": "Availability FAQs",
- "urls": [
- "/${VERSION}/multi-active-availability.html"
- ]
- },
- {
- "title": "Licensing FAQs",
- "urls": [
- "/${VERSION}/licensing-faqs.html"
- ]
- },
- {
- "title": "CockroachDB in Comparison",
- "urls": [
- "/${VERSION}/cockroachdb-in-comparison.html"
- ]
- }
+ "title": "Archived Documentation",
+ "urls": [
+ "/releases/archived-documentation.html"
]
- },
- {% include sidebar-releases.json %}
+ }
]
}
-]
+]
\ No newline at end of file
diff --git a/src/current/_includes/v20.1/admin-ui-custom-chart-debug-page-00.html b/src/current/_includes/v20.1/admin-ui-custom-chart-debug-page-00.html
deleted file mode 100644
index 36e0764df99..00000000000
--- a/src/current/_includes/v20.1/admin-ui-custom-chart-debug-page-00.html
+++ /dev/null
@@ -1,109 +0,0 @@
-| - Column - | -- Description - | -
|---|---|
| - Metric Name - | -
- How the system refers to this metric, e.g., sql.bytesin.
- |
-
| - Downsampler - | -
- - The "Downsampler" operation is used to combine the individual datapoints over the longer period into a single datapoint. We store one data point every ten seconds, but for queries over long time spans the backend lowers the resolution of the returned data, perhaps only returning one data point for every minute, five minutes, or even an entire hour in the case of the 30 day view. - -- Options: -
|
-
| - Aggregator - | -
- - Used to combine data points from different nodes. It has the same operations available as the Downsampler. - -- Options: -
|
-
| - Rate - | -
- - Determines how to display the rate of change during the selected time period. - -- Options: - -
|
-
| - Source - | -
- The set of nodes being queried, which is either:
-
|
-
| - Per Node - | -- If checked, the chart will show a line for each node's value of this metric. - | -
-
-Metric | Description
---------|----
-Total Nodes | The total number of nodes in the cluster. [Decommissioned nodes](remove-nodes.html) are not included in this count.
-Capacity Used | The storage capacity used as a percentage of [usable capacity](admin-ui-cluster-overview-page.html#capacity-metrics) allocated across all nodes.
-Unavailable Ranges | The number of unavailable ranges in the cluster. A non-zero number indicates an unstable cluster.
-Queries per second | The total number of `SELECT`, `UPDATE`, `INSERT`, and `DELETE` queries executed per second across the cluster.
-P99 Latency | The 99th percentile of service latency.
-
-{{site.data.alerts.callout_info}}
-{% include {{ page.version.version }}/misc/available-capacity-metric.md %}
-{{site.data.alerts.end}}
-
-### Events panel
-
-Underneath the [Summary](#summary-panel) panel, the **Events** panel lists the 5 most recent events logged for all nodes across the cluster. To list all events, click **View all events**.
-
-
-
-The following types of events are listed:
-
-- Database created
-- Database dropped
-- Table created
-- Table dropped
-- Table altered
-- Index created
-- Index dropped
-- View created
-- View dropped
-- Schema change reversed
-- Schema change finished
-- Node joined
-- Node decommissioned
-- Node restarted
-- Cluster setting changed
\ No newline at end of file
diff --git a/src/current/_includes/v20.1/admin-ui/logical-bytes.md b/src/current/_includes/v20.1/admin-ui/logical-bytes.md
deleted file mode 100644
index e85f04cea92..00000000000
--- a/src/current/_includes/v20.1/admin-ui/logical-bytes.md
+++ /dev/null
@@ -1 +0,0 @@
-Logical bytes reflect the approximate number of bytes stored in the database. This value may deviate from the number of physical bytes on disk, due to factors such as compression and [write amplification](https://en.wikipedia.org/wiki/Write_amplification).
\ No newline at end of file
diff --git a/src/current/_includes/v20.1/alerts/warning-a58932.md b/src/current/_includes/v20.1/alerts/warning-a58932.md
deleted file mode 100644
index 03920fa18ee..00000000000
--- a/src/current/_includes/v20.1/alerts/warning-a58932.md
+++ /dev/null
@@ -1,3 +0,0 @@
-A denial-of-service (DoS) vulnerability is present in CockroachDB v20.1.0 - v20.1.10 due to a bug in [protobuf](https://github.com/gogo/protobuf). This is resolved in CockroachDB [v20.1.11](../releases/v20.1.html#v20-1-11) and [later releases](../releases/#production-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](../advisories/a58932.html).
\ No newline at end of file
diff --git a/src/current/_includes/v20.1/alerts/warning-a63162.md b/src/current/_includes/v20.1/alerts/warning-a63162.md
deleted file mode 100644
index 6f328a46fe3..00000000000
--- a/src/current/_includes/v20.1/alerts/warning-a63162.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Cockroach Labs has discovered a bug relating to incremental backups, for CockroachDB v20.1.0 - v20.1.13. If a backup coincides with an in-progress index creation (backfill), `RESTORE`, or `IMPORT`, it is possible that a subsequent incremental backup will not include all of the indexed, restored or imported data.
-
-Users are advised to upgrade to v20.1.15 or later, which includes resolutions.
-
-For more information, including other affected versions, see [Technical Advisory 63162](../advisories/a63162.html).
\ No newline at end of file
diff --git a/src/current/_includes/v20.1/app/BasicExample.java b/src/current/_includes/v20.1/app/BasicExample.java
deleted file mode 100644
index f9737ff4a43..00000000000
--- a/src/current/_includes/v20.1/app/BasicExample.java
+++ /dev/null
@@ -1,438 +0,0 @@
-import java.util.*;
-import java.time.*;
-import java.sql.*;
-import javax.sql.DataSource;
-
-import org.postgresql.ds.PGSimpleDataSource;
-
-/*
- Download the Postgres JDBC driver jar from https://jdbc.postgresql.org.
-
- Then, compile and run this example like so:
-
- $ export CLASSPATH=.:/path/to/postgresql.jar
- $ javac BasicExample.java && java BasicExample
-
- To build the javadoc:
-
- $ javadoc -package -cp .:./path/to/postgresql.jar BasicExample.java
-
- At a high level, this code consists of two classes:
-
- 1. BasicExample, which is where the application logic lives.
-
- 2. BasicExampleDAO, which is used by the application to access the
- data store.
-
-*/
-
-public class BasicExample {
-
- public static void main(String[] args) {
-
- // Configure the database connection.
- PGSimpleDataSource ds = new PGSimpleDataSource();
- ds.setServerName("localhost");
- ds.setPortNumber(26257);
- ds.setDatabaseName("bank");
- ds.setUser("maxroach");
- ds.setPassword(null);
- ds.setSsl(true);
- ds.setSslMode("require");
- ds.setSslRootCert("certs/client.root.crt");
- ds.setSslCert("certs/client.maxroach.crt");
- ds.setSslKey("certs/client.maxroach.key.pk8");
- ds.setReWriteBatchedInserts(true); // add `rewriteBatchedInserts=true` to pg connection string
- ds.setApplicationName("BasicExample");
-
- // Create DAO.
- BasicExampleDAO dao = new BasicExampleDAO(ds);
-
- // Test our retry handling logic if FORCE_RETRY is true. This
- // method is only used to test the retry logic. It is not
- // necessary in production code.
- dao.testRetryHandling();
-
- // Set up the 'accounts' table.
- dao.createAccounts();
-
- // Insert a few accounts "by hand", using INSERTs on the backend.
- Map
- * This is enforced by the REQUIRES_NEW propagation attribute of @Transactional annotated
- * controller methods. Between the web container's HTTP listener and the transaction proxy,
- * there's yet another transparent proxy in the form of a retry loop advice with exponential
- * backoff. It takes care of retrying transactions that are aborted by transient SQL errors,
- * rather than having these propagate all the way over the wire to the client / user agent.
- *
- * @see RetryableTransactionAspect
- */
-@RestController
-public class AccountController {
- @Autowired
- private AccountRepository accountRepository;
-
- @Autowired
- private PagedResourcesAssembler
- * This advice needs to runs in a non-transactional context, which is before the underlying
- * transaction advisor (@Order ensures that).
- */
-@Component
-@Aspect
-// Before TX advisor
-@Order(Ordered.LOWEST_PRECEDENCE - 2)
-public class RetryableTransactionAspect {
- protected final Logger logger = LoggerFactory.getLogger(getClass());
-
- @Pointcut("execution(* io.roach..*(..)) && @annotation(transactional)")
- public void anyTransactionBoundaryOperation(Transactional transactional) {
- }
-
- @Around(value = "anyTransactionBoundaryOperation(transactional)",
- argNames = "pjp,transactional")
- public Object retryableOperation(ProceedingJoinPoint pjp, Transactional transactional)
- throws Throwable {
- final int totalRetries = 30;
- int numAttempts = 0;
- AtomicLong backoffMillis = new AtomicLong(150);
-
- Assert.isTrue(!TransactionSynchronizationManager.isActualTransactionActive(), "TX active");
-
- do {
- try {
- numAttempts++;
- return pjp.proceed();
- } catch (TransientDataAccessException | TransactionSystemException ex) {
- handleTransientException(ex, numAttempts, totalRetries, pjp, backoffMillis);
- } catch (UndeclaredThrowableException ex) {
- Throwable t = ex.getUndeclaredThrowable();
- if (t instanceof TransientDataAccessException) {
- handleTransientException(t, numAttempts, totalRetries, pjp, backoffMillis);
- } else {
- throw ex;
- }
- }
- } while (numAttempts < totalRetries);
-
- throw new ConcurrencyFailureException("Too many transient errors (" + numAttempts + ") for method ["
- + pjp.getSignature().toLongString() + "]. Giving up!");
- }
-
- private void handleTransientException(Throwable ex, int numAttempts, int totalAttempts,
- ProceedingJoinPoint pjp, AtomicLong backoffMillis) {
- if (logger.isWarnEnabled()) {
- logger.warn("Transient data access exception (" + numAttempts + " of max " + totalAttempts + ") "
- + "detected (retry in " + backoffMillis + " ms) "
- + "in method '" + pjp.getSignature().getDeclaringTypeName() + "." + pjp.getSignature().getName()
- + "': " + ex.getMessage());
- }
- if (backoffMillis.get() >= 0) {
- try {
- Thread.sleep(backoffMillis.get());
- } catch (InterruptedException e) {
- Thread.currentThread().interrupt();
- }
- backoffMillis.set(Math.min((long) (backoffMillis.get() * 1.5), 1500));
- }
- }
-}
diff --git a/src/current/_includes/v20.1/app/spring-data-jdbc/TransactionHintsAspect.java b/src/current/_includes/v20.1/app/spring-data-jdbc/TransactionHintsAspect.java
deleted file mode 100644
index 0eae2cba3ba..00000000000
--- a/src/current/_includes/v20.1/app/spring-data-jdbc/TransactionHintsAspect.java
+++ /dev/null
@@ -1,63 +0,0 @@
-package io.roach.data.jdbc;
-
-import org.aspectj.lang.ProceedingJoinPoint;
-import org.aspectj.lang.annotation.Around;
-import org.aspectj.lang.annotation.Aspect;
-import org.aspectj.lang.annotation.Pointcut;
-import org.slf4j.Logger;
-import org.slf4j.LoggerFactory;
-import org.springframework.beans.factory.annotation.Autowired;
-import org.springframework.core.Ordered;
-import org.springframework.core.annotation.Order;
-import org.springframework.jdbc.core.JdbcTemplate;
-import org.springframework.stereotype.Component;
-import org.springframework.transaction.TransactionDefinition;
-import org.springframework.transaction.annotation.Transactional;
-import org.springframework.transaction.support.TransactionSynchronizationManager;
-import org.springframework.util.Assert;
-
-/**
- * Aspect with an around advice that intercepts and sets transaction attributes.
- *
- * This advice needs to runs in a transactional context, which is after the underlying
- * transaction advisor.
- */
-@Component
-@Aspect
-// After TX advisor
-@Order(Ordered.LOWEST_PRECEDENCE)
-public class TransactionHintsAspect {
- protected final Logger logger = LoggerFactory.getLogger(getClass());
-
- @Autowired
- private JdbcTemplate jdbcTemplate;
-
- private String applicationName = "roach-data";
-
- @Pointcut("execution(* io.roach..*(..)) && @annotation(transactional)")
- public void anyTransactionBoundaryOperation(Transactional transactional) {
- }
-
- @Around(value = "anyTransactionBoundaryOperation(transactional)",
- argNames = "pjp,transactional")
- public Object setTransactionAttributes(ProceedingJoinPoint pjp, Transactional transactional)
- throws Throwable {
- Assert.isTrue(TransactionSynchronizationManager.isActualTransactionActive(), "TX not active");
-
- // https://www.cockroachlabs.com/docs/v19.2/set-vars.html
- jdbcTemplate.update("SET application_name=?", applicationName);
-
- if (transactional.timeout() != TransactionDefinition.TIMEOUT_DEFAULT) {
- logger.info("Setting statement time {} for {}", transactional.timeout(),
- pjp.getSignature().toShortString());
- jdbcTemplate.update("SET statement_timeout=?", transactional.timeout() * 1000);
- }
-
- if (transactional.readOnly()) {
- logger.info("Setting transaction read only for {}", pjp.getSignature().toShortString());
- jdbcTemplate.execute("SET transaction_read_only=true");
- }
-
- return pjp.proceed();
- }
-}
diff --git a/src/current/_includes/v20.1/app/spring-data-jdbc/changelog-master.xml b/src/current/_includes/v20.1/app/spring-data-jdbc/changelog-master.xml
deleted file mode 100644
index 05915165a00..00000000000
--- a/src/current/_includes/v20.1/app/spring-data-jdbc/changelog-master.xml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
- * This advice needs to runs in a non-transactional context, which is before the underlying
- * transaction advisor (@Order ensures that).
- */
-@Component
-@Aspect
-// Before TX advisor
-@Order(Ordered.LOWEST_PRECEDENCE - 1)
-public class RetryableTransactionAspect {
- protected final Logger logger = LoggerFactory.getLogger(getClass());
-
- @Pointcut("@annotation(transactional)")
- public void anyTransactionBoundaryOperation(Transactional transactional) {
- }
-
- @Around(value = "anyTransactionBoundaryOperation(transactional)",
- argNames = "pjp,transactional")
- public Object retryableOperation(ProceedingJoinPoint pjp, Transactional transactional)
- throws Throwable {
- final int totalRetries = 30;
- int numAttempts = 0;
- AtomicLong backoffMillis = new AtomicLong(150);
-
- Assert.isTrue(!TransactionSynchronizationManager.isActualTransactionActive(), "TX active");
-
- do {
- try {
- numAttempts++;
- return pjp.proceed();
- } catch (TransientDataAccessException | TransactionSystemException ex) {
- handleTransientException(ex, numAttempts, totalRetries, pjp, backoffMillis);
- } catch (UndeclaredThrowableException ex) {
- Throwable t = ex.getUndeclaredThrowable();
- if (t instanceof TransientDataAccessException) {
- handleTransientException(t, numAttempts, totalRetries, pjp, backoffMillis);
- } else {
- throw ex;
- }
- }
- } while (numAttempts < totalRetries);
-
- throw new ConcurrencyFailureException("Too many transient errors (" + numAttempts + ") for method ["
- + pjp.getSignature().toLongString() + "]. Giving up!");
- }
-
- private void handleTransientException(Throwable ex, int numAttempts, int totalAttempts,
- ProceedingJoinPoint pjp, AtomicLong backoffMillis) {
- if (logger.isWarnEnabled()) {
- logger.warn("Transient data access exception (" + numAttempts + " of max " + totalAttempts + ") "
- + "detected (retry in " + backoffMillis + " ms) "
- + "in method '" + pjp.getSignature().getDeclaringTypeName() + "." + pjp.getSignature().getName()
- + "': " + ex.getMessage());
- }
- if (backoffMillis.get() >= 0) {
- try {
- Thread.sleep(backoffMillis.get());
- } catch (InterruptedException e) {
- Thread.currentThread().interrupt();
- }
- backoffMillis.set(Math.min((long) (backoffMillis.get() * 1.5), 1500));
- }
- }
-}
\ No newline at end of file
diff --git a/src/current/_includes/v20.1/app/spring-mybatis/application.yml b/src/current/_includes/v20.1/app/spring-mybatis/application.yml
deleted file mode 100644
index baca47cd1ef..00000000000
--- a/src/current/_includes/v20.1/app/spring-mybatis/application.yml
+++ /dev/null
@@ -1,5 +0,0 @@
-spring:
- datasource:
- driver-class-name: org.postgresql.Driver
- url: jdbc:postgresql://localhost:26257/bank?ssl=true&sslmode=require&sslrootcert=/certs/ca.crt&sslkey=/certs/client.maxroach.key.pk8&sslcert=/certs/client.maxroach.crt
- username: maxroach
diff --git a/src/current/_includes/v20.1/app/spring-mybatis/batchmapper/BatchAccountMapper.java b/src/current/_includes/v20.1/app/spring-mybatis/batchmapper/BatchAccountMapper.java
deleted file mode 100644
index 1115f1ad606..00000000000
--- a/src/current/_includes/v20.1/app/spring-mybatis/batchmapper/BatchAccountMapper.java
+++ /dev/null
@@ -1,19 +0,0 @@
-package com.example.cockroachdemo.batchmapper;
-
-import java.util.List;
-
-import com.example.cockroachdemo.model.Account;
-
-import org.apache.ibatis.annotations.Flush;
-import org.apache.ibatis.annotations.Insert;
-import org.apache.ibatis.annotations.Mapper;
-import org.apache.ibatis.executor.BatchResult;
-
-@Mapper
-public interface BatchAccountMapper {
- @Insert("upsert into accounts(id, balance) values(#{id}, #{balance})")
- void insertAccount(Account account);
-
- @Flush
- List The CockroachDB binary for Linux requires
From a SQL perspective, a table and its secondary indexes initially map to a single range, where each key-value pair in the range represents a single row in the table (also called the primary index because the table is sorted by the primary key) or a single row in a secondary index. As soon as that range reaches 512 MiB in size, it splits into two ranges. This process continues for these new ranges as the table and its indexes continue growing.
-**Replica** | CockroachDB replicates each range (3 times by default) and stores each replica on a different node.
-**Leaseholder** | For each range, one of the replicas holds the "range lease". This replica, referred to as the "leaseholder", is the one that receives and coordinates all read and write requests for the range.
Unlike writes, read requests access the leaseholder and send the results to the client without needing to coordinate with any of the other range replicas. This reduces the network round trips involved and is possible because the leaseholder is guaranteed to be up-to-date due to the fact that all write requests also go to the leaseholder.
-**Raft Leader** | For each range, one of the replicas is the "leader" for write requests. Via the [Raft consensus protocol](replication-layer.html#raft), this replica ensures that a majority of replicas (the leader and enough followers) agree, based on their Raft logs, before committing the write. The Raft leader is almost always the same replica as the leaseholder.
-**Raft Log** | For each range, a time-ordered log of writes to the range that its replicas have agreed on. This log exists on-disk with each replica and is the range's source of truth for consistent replication.
diff --git a/src/current/_includes/v20.1/misc/chrome-localhost.md b/src/current/_includes/v20.1/misc/chrome-localhost.md
deleted file mode 100644
index 24f9bb159a3..00000000000
--- a/src/current/_includes/v20.1/misc/chrome-localhost.md
+++ /dev/null
@@ -1,3 +0,0 @@
-{{site.data.alerts.callout_info}}
-If you are using Google Chrome, and you are getting an error about not being able to reach `localhost` because its certificate has been revoked, go to chrome://flags/#allow-insecure-localhost, enable "Allow invalid certificates for resources loaded from localhost", and then restart the browser. Enabling this Chrome feature degrades security for all sites running on `localhost`, not just CockroachDB's Admin UI, so be sure to enable the feature only temporarily.
-{{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/misc/client-side-intervention-example.md b/src/current/_includes/v20.1/misc/client-side-intervention-example.md
deleted file mode 100644
index d0bbfc33695..00000000000
--- a/src/current/_includes/v20.1/misc/client-side-intervention-example.md
+++ /dev/null
@@ -1,28 +0,0 @@
-The Python-like pseudocode below shows how to implement an application-level retry loop; it does not require your driver or ORM to implement [advanced retry handling logic](advanced-client-side-transaction-retries.html), so it can be used from any programming language or environment. In particular, your retry loop must:
-
-- Raise an error if the `max_retries` limit is reached
-- Retry on `40001` error codes
-- [`COMMIT`](commit-transaction.html) at the end of the `try` block
-- Implement [exponential backoff](https://en.wikipedia.org/wiki/Exponential_backoff) logic as shown below for best performance
-
-~~~ python
-while true:
- n++
- if n == max_retries:
- throw Error("did not succeed within N retries")
- try:
- # add logic here to run all your statements
- conn.exec('COMMIT')
- break
- catch error:
- if error.code != "40001":
- throw error
- else:
- # This is a retry error, so we roll back the current transaction
- # and sleep for a bit before retrying. The sleep time increases
- # for each failed transaction. Adapted from
- # https://colintemple.com/2017/03/java-exponential-backoff/
- conn.exec('ROLLBACK');
- sleep_ms = int(((2**n) * 100) + rand( 100 - 1 ) + 1)
- sleep(sleep_ms) # Assumes your sleep() takes milliseconds
-~~~
diff --git a/src/current/_includes/v20.1/misc/csv-import-callout.md b/src/current/_includes/v20.1/misc/csv-import-callout.md
deleted file mode 100644
index 60555c5d0b6..00000000000
--- a/src/current/_includes/v20.1/misc/csv-import-callout.md
+++ /dev/null
@@ -1,3 +0,0 @@
-{{site.data.alerts.callout_info}}
-The column order in your schema must match the column order in the file being imported.
-{{site.data.alerts.end}}
\ No newline at end of file
diff --git a/src/current/_includes/v20.1/misc/customizing-the-savepoint-name.md b/src/current/_includes/v20.1/misc/customizing-the-savepoint-name.md
deleted file mode 100644
index ed895f906f3..00000000000
--- a/src/current/_includes/v20.1/misc/customizing-the-savepoint-name.md
+++ /dev/null
@@ -1,5 +0,0 @@
-Set the `force_savepoint_restart` [session variable](set-vars.html#supported-variables) to `true` to enable using a custom name for the [retry savepoint](advanced-client-side-transaction-retries.html#retry-savepoints).
-
-Once this variable is set, the [`SAVEPOINT`](savepoint.html) statement will accept any name for the retry savepoint, not just `cockroach_restart`. In addition, it causes every savepoint name to be equivalent to `cockroach_restart`, therefore disallowing the use of [nested transactions](transactions.html#nested-transactions).
-
-This feature exists to support applications that want to use the [advanced client-side transaction retry protocol](advanced-client-side-transaction-retries.html), but cannot customize the name of savepoints to be `cockroach_restart`. For example, this may be necessary because you are using an ORM that requires its own names for savepoints.
diff --git a/src/current/_includes/v20.1/misc/debug-subcommands.md b/src/current/_includes/v20.1/misc/debug-subcommands.md
deleted file mode 100644
index 379047a6441..00000000000
--- a/src/current/_includes/v20.1/misc/debug-subcommands.md
+++ /dev/null
@@ -1,3 +0,0 @@
-While the `cockroach debug` command has a few subcommands, users are expected to use only the [`zip`](cockroach-debug-zip.html), [`encryption-active-key`](cockroach-debug-encryption-active-key.html), [`merge-logs`](cockroach-debug-merge-logs.html), and [`ballast`](cockroach-debug-ballast.html) subcommands.
-
-The other `debug` subcommands are useful only to CockroachDB's developers and contributors.
diff --git a/src/current/_includes/v20.1/misc/delete-statistics.md b/src/current/_includes/v20.1/misc/delete-statistics.md
deleted file mode 100644
index a850a1ed654..00000000000
--- a/src/current/_includes/v20.1/misc/delete-statistics.md
+++ /dev/null
@@ -1,17 +0,0 @@
-To delete statistics for all tables in all databases:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> DELETE FROM system.table_statistics WHERE true;
-~~~
-
-To delete a named set of statistics (e.g, one named "users_stats"), run a query like the following:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> DELETE FROM system.table_statistics WHERE name = 'users_stats';
-~~~
-
-After deleting statistics, restart the nodes in your cluster to clear the statistics caches.
-
-For more information about the `DELETE` statement, see [`DELETE`](delete.html).
diff --git a/src/current/_includes/v20.1/misc/diagnostics-callout.html b/src/current/_includes/v20.1/misc/diagnostics-callout.html
deleted file mode 100644
index a969a8cf152..00000000000
--- a/src/current/_includes/v20.1/misc/diagnostics-callout.html
+++ /dev/null
@@ -1 +0,0 @@
-{{site.data.alerts.callout_info}}By default, each node of a CockroachDB cluster periodically shares anonymous usage details with Cockroach Labs. For an explanation of the details that get shared and how to opt-out of reporting, see Diagnostics Reporting.{{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/misc/drivers.md b/src/current/_includes/v20.1/misc/drivers.md
deleted file mode 100644
index 680422e13ce..00000000000
--- a/src/current/_includes/v20.1/misc/drivers.md
+++ /dev/null
@@ -1,18 +0,0 @@
-{{site.data.alerts.callout_info}}
-Applications may encounter incompatibilities when using advanced or obscure features of a driver or ORM with **beta-level** support. If you encounter problems, please [open an issue](https://github.com/cockroachdb/cockroach/issues/new) with details to help us make progress toward full support.
-{{site.data.alerts.end}}
-
-| App Language | Drivers | ORMs | Support level |
-|--------------+-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+---------------------------------------------------------------------+------|
-| Python | [psycopg2](build-a-python-app-with-cockroachdb.html) | [SQLAlchemy](build-a-python-app-with-cockroachdb-sqlalchemy.html)
[Django](build-a-python-app-with-cockroachdb-django.html)
[peewee](http://docs.peewee-orm.com/en/latest/peewee/playhouse.html#cockroach-database) | Full |
-| Java | [JDBC](build-a-java-app-with-cockroachdb.html) | [Hibernate](build-a-java-app-with-cockroachdb-hibernate.html)
[jOOQ](build-a-java-app-with-cockroachdb-jooq.html) | Full |
-| Go | [pgx](build-a-go-app-with-cockroachdb.html)
[pq](build-a-go-app-with-cockroachdb-pq.html) | [GORM](build-a-go-app-with-cockroachdb-gorm.html)
[upper/db](build-a-go-app-with-cockroachdb-upperdb.html) | Full |
-| Ruby | [pg](build-a-ruby-app-with-cockroachdb.html) | [ActiveRecord](build-a-ruby-app-with-cockroachdb-activerecord.html) | Full |
-| Node.js | [pg](build-a-nodejs-app-with-cockroachdb.html) | [Sequelize](build-a-nodejs-app-with-cockroachdb-sequelize.html) | Beta |
-| C | [libpq](http://www.postgresql.org/docs/9.5/static/libpq.html) | No ORMs tested | Beta |
-| C++ | [libpqxx](build-a-c++-app-with-cockroachdb.html) | No ORMs tested | Beta |
-| C# (.NET) | [Npgsql](build-a-csharp-app-with-cockroachdb.html) | No ORMs tested | Beta |
-| Clojure | [java.jdbc](build-a-clojure-app-with-cockroachdb.html) | No ORMs tested | Beta |
-| PHP | [php-pgsql](build-a-php-app-with-cockroachdb.html) | No ORMs tested | Beta |
-| Rust | postgres {% comment %} This link is in HTML instead of Markdown because HTML proofer dies bc of https://github.com/rust-lang/crates.io/issues/163 {% endcomment %} | No ORMs tested | Beta |
-| TypeScript | No drivers tested | [TypeORM](https://typeorm.io/#/) | Beta |
diff --git a/src/current/_includes/v20.1/misc/enterprise-features.md b/src/current/_includes/v20.1/misc/enterprise-features.md
deleted file mode 100644
index 704a3d32e34..00000000000
--- a/src/current/_includes/v20.1/misc/enterprise-features.md
+++ /dev/null
@@ -1,12 +0,0 @@
-Feature | Description
---------+-------------------------
-[Geo-Partitioning](topology-geo-partitioned-replicas.html) | This feature gives you row-level control of how and where your data is stored to dramatically reduce read and write latencies and assist in meeting regulatory requirements in multi-region deployments.
-[Follower Reads](follower-reads.html) | This feature reduces read latency in multi-region deployments by using the closest replica at the expense of reading slightly historical data.
-[`BACKUP`](backup.html) | This feature creates full or incremental backups of your cluster's schema and data that are consistent as of a given timestamp, stored on a service such as AWS S3, Google Cloud Storage, NFS, or HTTP storage.
Backups can be locality-aware such that each node writes files only to the backup destination that matches the node's [locality](cockroach-start.html#locality). This is useful for reducing cloud storage data transfer costs by keeping data within cloud regions and complying with data domiciling requirements.
-[`RESTORE`](restore.html) | This feature restores your cluster's schemas and data from an enterprise `BACKUP`.
-[Change Data Capture](change-data-capture.html) (CDC) | This feature provides efficient, distributed, row-level [change feeds into Apache Kafka](create-changefeed.html) for downstream processing such as reporting, caching, or full-text indexing.
-[Node Map](enable-node-map.html) | This feature visualizes the geographical configuration of a cluster by plotting node localities on a world map.
-[Locality-Aware Index Selection](cost-based-optimizer.html#preferring-the-nearest-index) | Given [multiple identical indexes](topology-duplicate-indexes.html) that have different locality constraints using [replication zones](configure-replication-zones.html), the cost-based optimizer will prefer the index that is closest to the gateway node that is planning the query. In multi-region deployments, this can lead to performance improvements due to improved data locality and reduced network traffic.
-[Encryption at Rest](encryption.html#encryption-at-rest-enterprise) | Supplementing CockroachDB's encryption in flight capabilities, this feature provides transparent encryption of a node's data on the local disk. It allows encryption of all files on disk using AES in counter mode, with all key sizes allowed.
-[GSSAPI with Kerberos Authentication](gssapi_authentication.html) | CockroachDB supports the Generic Security Services API (GSSAPI) with Kerberos authentication, which lets you use an external enterprise directory system that supports Kerberos, such as Active Directory.
-[`EXPORT`](export.html) | This feature uses the CockroachDB distributed execution engine to quickly get large sets of data out of CockroachDB in a CSV format that can be ingested by downstream systems.
diff --git a/src/current/_includes/v20.1/misc/experimental-warning.md b/src/current/_includes/v20.1/misc/experimental-warning.md
deleted file mode 100644
index d38a9755593..00000000000
--- a/src/current/_includes/v20.1/misc/experimental-warning.md
+++ /dev/null
@@ -1,3 +0,0 @@
-{{site.data.alerts.callout_danger}}
-**This is an experimental feature**. The interface and output are subject to change.
-{{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/misc/explore-benefits-see-also.md b/src/current/_includes/v20.1/misc/explore-benefits-see-also.md
deleted file mode 100644
index 6b1a3afed71..00000000000
--- a/src/current/_includes/v20.1/misc/explore-benefits-see-also.md
+++ /dev/null
@@ -1,7 +0,0 @@
-- [Replication & Rebalancing](demo-replication-and-rebalancing.html)
-- [Fault Tolerance & Recovery](demo-fault-tolerance-and-recovery.html)
-- [Low Latency Multi-Region Deployment](demo-low-latency-multi-region-deployment.html)
-- [Serializable Transactions](demo-serializable.html)
-- [Cross-Cloud Migration](demo-automatic-cloud-migration.html)
-- [Orchestration](orchestrate-a-local-cluster-with-kubernetes-insecure.html)
-- [JSON Support](demo-json-support.html)
diff --git a/src/current/_includes/v20.1/misc/external-urls.md b/src/current/_includes/v20.1/misc/external-urls.md
deleted file mode 100644
index 12789956364..00000000000
--- a/src/current/_includes/v20.1/misc/external-urls.md
+++ /dev/null
@@ -1,48 +0,0 @@
-~~~
-[scheme]://[host]/[path]?[parameters]
-~~~
-
-Location | Scheme | Host | Parameters |
-|-------------------------------------------------------------+-------------+--------------------------------------------------+----------------------------------------------------------------------------
-Amazon | `s3` | Bucket name | `AUTH` [1](#considerations) (optional; can be `implicit` or `specified`), `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_SESSION_TOKEN`
-Azure | `azure` | N/A (see [Example file URLs](#example-file-urls) | `AZURE_ACCOUNT_KEY`, `AZURE_ACCOUNT_NAME`
-Google Cloud [2](#considerations) | `gs` | Bucket name | `AUTH` (optional; can be `default`, `implicit`, or `specified`), `CREDENTIALS`
-HTTP [3](#considerations) | `http` | Remote host | N/A
-NFS/Local [4](#considerations) | `nodelocal` | `nodeID` or `self` [5](#considerations) (see [Example file URLs](#example-file-urls)) | N/A
-S3-compatible services [6](#considerations) | `s3` | Bucket name | `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_SESSION_TOKEN`, `AWS_REGION` [7](#considerations) (optional), `AWS_ENDPOINT`
-
-{{site.data.alerts.callout_info}}
-The location parameters often contain special characters that need to be URI-encoded. Use Javascript's [encodeURIComponent](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/encodeURIComponent) function or Go language's [url.QueryEscape](https://golang.org/pkg/net/url/#QueryEscape) function to URI-encode the parameters. Other languages provide similar functions to URI-encode special characters.
-{{site.data.alerts.end}}
-
-{{site.data.alerts.callout_info}}
-If your environment requires an HTTP or HTTPS proxy server for outgoing connections, you can set the standard `HTTP_PROXY` and `HTTPS_PROXY` environment variables when starting CockroachDB.
-
-New in v20.1: If you cannot run a full proxy, you can disable external HTTP(S) access (as well as custom HTTP(S) endpoints) when performing bulk operations (e.g., `BACKUP`, `RESTORE`, etc.) by using the [`--external-io-disable-http` flag](cockroach-start.html#security). You can also disable the use of implicit credentials when accessing external cloud storage services for various bulk operations by using the [`--external-io-disable-implicit-credentials` flag](cockroach-start.html#security).
-{{site.data.alerts.end}}
-
-
-
-- 1 If the `AUTH` parameter is not provided, AWS connections default to `specified` and the access keys must be provided in the URI parameters. If the `AUTH` parameter is `implicit`, the access keys can be omitted and [the credentials will be loaded from the environment](https://docs.aws.amazon.com/sdk-for-go/api/aws/session/).
-
-- 2 If the `AUTH` parameter is not specified, the `cloudstorage.gs.default.key` [cluster setting](cluster-settings.html) will be used if it is non-empty, otherwise the `implicit` behavior is used. If the `AUTH` parameter is `implicit`, all GCS connections use Google's [default authentication strategy](https://cloud.google.com/docs/authentication/production#providing_credentials_to_your_application). If the `AUTH` parameter is `default`, the `cloudstorage.gs.default.key` [cluster setting](cluster-settings.html) must be set to the contents of a [service account file](https://cloud.google.com/docs/authentication/production#obtaining_and_providing_service_account_credentials_manually) which will be used during authentication. If the `AUTH` parameter is `specified`, GCS connections are authenticated on a per-statement basis, which allows the JSON key object to be sent in the `CREDENTIALS` parameter. The JSON key object should be base64-encoded (using the standard encoding in [RFC 4648](https://tools.ietf.org/html/rfc4648)).
-
-- 3 You can create your own HTTP server with [Caddy or nginx](create-a-file-server.html). A custom root CA can be appended to the system's default CAs by setting the `cloudstorage.http.custom_ca` [cluster setting](cluster-settings.html), which will be used when verifying certificates from HTTPS URLs.
-
-- 4 The file system backup location on the NFS drive is relative to the path specified by the `--external-io-dir` flag set while [starting the node](cockroach-start.html). If the flag is set to `disabled`, then imports from local directories and NFS drives are disabled.
-
-- 5 New in v20.1: Using a `nodeID` is required and the data files will be in the `extern` directory of the specified node. In most cases (including single-node clusters), using `nodelocal://1/
`timeout client`
`timeout server` | Timeout values that should be suitable for most deployments.
- `bind` | The port that HAProxy listens on. This is the port clients will connect to and thus needs to be allowed by your network configuration.
This tutorial assumes HAProxy is running on a separate machine from CockroachDB nodes. If you run HAProxy on the same machine as a node (not recommended), you'll need to change this port, as `26257` is likely already being used by the CockroachDB node.
- `balance` | The balancing algorithm. This is set to `roundrobin` to ensure that connections get rotated amongst nodes (connection 1 on node 1, connection 2 on node 2, etc.). Check the [HAProxy Configuration Manual](http://cbonte.github.io/haproxy-dconv/1.7/configuration.html#4-balance) for details about this and other balancing algorithms.
- `option httpchk` | The HTTP endpoint that HAProxy uses to check node health. [`/health?ready=1`](monitoring-and-alerting.html#health-ready-1) ensures that HAProxy doesn't direct traffic to nodes that are live but not ready to receive requests.
- `server` | For each included node, this field specifies the address the node advertises to other nodes in the cluster, i.e., the addressed pass in the [`--advertise-addr` flag](cockroach-start.html#networking) on node startup. Make sure hostnames are resolvable and IP addresses are routable from HAProxy.
-
- {{site.data.alerts.callout_info}}
- For full details on these and other configuration settings, see the [HAProxy Configuration Manual](http://cbonte.github.io/haproxy-dconv/1.7/configuration.html).
- {{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/misc/import-perf.md b/src/current/_includes/v20.1/misc/import-perf.md
deleted file mode 100644
index b0520a9c392..00000000000
--- a/src/current/_includes/v20.1/misc/import-perf.md
+++ /dev/null
@@ -1,3 +0,0 @@
-{{site.data.alerts.callout_success}}
-For best practices for optimizing import performance in CockroachDB, see [Import Performance Best Practices](import-performance-best-practices.html).
-{{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/misc/install-next-steps.html b/src/current/_includes/v20.1/misc/install-next-steps.html
deleted file mode 100644
index 1b00fba3410..00000000000
--- a/src/current/_includes/v20.1/misc/install-next-steps.html
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
diff --git a/src/current/_includes/v20.1/misc/linux-binary-prereqs.md b/src/current/_includes/v20.1/misc/linux-binary-prereqs.md
deleted file mode 100644
index 541183fe71b..00000000000
--- a/src/current/_includes/v20.1/misc/linux-binary-prereqs.md
+++ /dev/null
@@ -1 +0,0 @@
-
-
- glibc, libncurses, and tzdata, which are found by default on nearly all Linux distributions, with Alpine as the notable exception.
Setting `--log-dir` to a blank directory (`--log-dir=`) disables logging to files. Do not use `--log-dir=""`; this creates a new directory named `""` and stores log files in that directory.
-`--log-dir-max-size` | After the log directory reaches the specified size, delete the oldest log file. The flag's argument takes standard file sizes, such as `--log-dir-max-size=1GiB`.
**Default**: 100MiB
-`--log-file-max-size` | After logs reach the specified size, begin writing logs to a new file. The flag's argument takes standard file sizes, such as `--log-file-max-size=2MiB`.
**Default**: 10MiB
-`--log-file-verbosity` | Only writes messages to log files if they are at or above the specified [severity level](debug-and-error-logs.html#severity-levels), such as `--log-file-verbosity=WARNING`. **Requires** logging to files.
**Default**: `INFO`
-`--logtostderr` | Enable logging to `stderr` for messages at or above the specified [severity level](debug-and-error-logs.html#severity-levels), such as `--logtostderr=ERROR`
If you use this flag without specifying the severity level (e.g., `cockroach start --logtostderr`), it prints messages of *all* severities to `stderr`.
Setting `--logtostderr=NONE` disables logging to `stderr`.
-`--no-color` | Do not colorize `stderr`. Possible values: `true` or `false`.
When set to `false`, messages logged to `stderr` are colorized based on [severity level](debug-and-error-logs.html#severity-levels).
**Default:** `false`
-`--sql-audit-dir` | If non-empty, create a SQL audit log in this directory. By default, SQL audit logs are written in the same directory as the other logs generated by CockroachDB.
Note that enabling SQL audit logs can negatively impact performance. As a result, we recommend using SQL audit logs for security purposes only. For more information, see the [`EXPERIMENTAL_AUDIT`](experimental-audit.html) reference page.
diff --git a/src/current/_includes/v20.1/misc/mitigate-contention-note.md b/src/current/_includes/v20.1/misc/mitigate-contention-note.md
deleted file mode 100644
index ffe3cff554a..00000000000
--- a/src/current/_includes/v20.1/misc/mitigate-contention-note.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{{site.data.alerts.callout_info}}
-It's possible to mitigate read-write contention and reduce transaction retries using the following techniques:
-1. By performing reads using [`AS OF SYSTEM TIME`](performance-best-practices-overview.html#use-as-of-system-time-to-decrease-conflicts-with-long-running-queries).
-2. By using [`SELECT FOR UPDATE`](select-for-update.html) to order transactions by controlling concurrent access to one or more rows of a table. This reduces retries in scenarios where a transaction performs a read and then updates the same row it just read.
-{{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/misc/movr-flask-211.md b/src/current/_includes/v20.1/misc/movr-flask-211.md
deleted file mode 100644
index 0dbe6c6550e..00000000000
--- a/src/current/_includes/v20.1/misc/movr-flask-211.md
+++ /dev/null
@@ -1,7 +0,0 @@
-{{site.data.alerts.callout_info}}
-CockroachDB versions v21.1 and above support [new multi-region capabilities, with different SQL syntax](../v21.1/multiregion-overview.html).
-
-For the latest version of the application and database schema built on v21.1 multi-region features, see the [`movr-flask` repository](https://github.com/cockroachlabs/movr-flask).
-
-For the latest version of the tutorial, see the [v21.1 docs](../v21.1/movr-flask-overview.html).
-{{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/misc/movr-live-demo.md b/src/current/_includes/v20.1/misc/movr-live-demo.md
deleted file mode 100644
index bcf4667692f..00000000000
--- a/src/current/_includes/v20.1/misc/movr-live-demo.md
+++ /dev/null
@@ -1,5 +0,0 @@
-{{site.data.alerts.callout_success}}
-For a live demo of the deployed MovR Flask application, see [https://movr.cloud](https://movr.cloud).
-
-Note that the backend for the live demo uses a newer version of the application, built on the [multi-region syntax introduced in v21.1](../v21.1/multiregion-overview.html). This newer application is also deployed using a simplified, serverless workflow. For more details, see the [`movr-flask` repository's README](https://github.com/cockroachlabs/movr-flask).
-{{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/misc/movr-schema.md b/src/current/_includes/v20.1/misc/movr-schema.md
deleted file mode 100644
index a8f57a2acae..00000000000
--- a/src/current/_includes/v20.1/misc/movr-schema.md
+++ /dev/null
@@ -1,12 +0,0 @@
-The six tables in the `movr` database store user, vehicle, and ride data for MovR:
-
-Table | Description
---------|----------------------------
-`users` | People registered for the service.
-`vehicles` | The pool of vehicles available for the service.
-`rides` | When and where users have rented a vehicle.
-`promo_codes` | Promotional codes for users.
-`user_promo_codes` | Promotional codes in use by users.
-`vehicle_location_histories` | Vehicle location history.
-
-
diff --git a/src/current/_includes/v20.1/misc/movr-workflow.md b/src/current/_includes/v20.1/misc/movr-workflow.md
deleted file mode 100644
index 1127ebd2a62..00000000000
--- a/src/current/_includes/v20.1/misc/movr-workflow.md
+++ /dev/null
@@ -1,76 +0,0 @@
-The workflow for MovR is as follows:
-
-1. A user loads the app and sees the 25 closest vehicles.
-
- For example:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > SELECT id, city, status FROM vehicles WHERE city='amsterdam' limit 25;
- ~~~
-
-2. The user signs up for the service.
-
- For example:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > INSERT INTO users (id, name, address, city, credit_card)
- VALUES ('66666666-6666-4400-8000-00000000000f', 'Mariah Lam', '88194 Angela Gardens Suite 60', 'amsterdam', '123245696');
- ~~~
-
- {{site.data.alerts.callout_info}}Usually for Universally Unique Identifier (UUID) you would need to generate it automatically but for the sake of this follow up we will use predetermined UUID to keep track of them in our examples.{{site.data.alerts.end}}
-
-3. In some cases, the user adds their own vehicle to share.
-
- For example:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > INSERT INTO vehicles (id, city, type, owner_id,creation_time,status, current_location, ext)
- VALUES ('ffffffff-ffff-4400-8000-00000000000f', 'amsterdam', 'skateboard', '66666666-6666-4400-8000-00000000000f', current_timestamp(), 'available', '88194 Angela Gardens Suite 60', '{"color": "blue"}');
- ~~~
-4. More often, the user reserves a vehicle and starts a ride, applying a promo code, if available and valid.
-
- For example:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > SELECT code FROM user_promo_codes WHERE user_id ='66666666-6666-4400-8000-00000000000f';
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > UPDATE vehicles SET status = 'in_use' WHERE id='bbbbbbbb-bbbb-4800-8000-00000000000b';
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > INSERT INTO rides (id, city, vehicle_city, rider_id, vehicle_id, start_address,end_address, start_time, end_time, revenue)
- VALUES ('cd032f56-cf1a-4800-8000-00000000066f', 'amsterdam', 'amsterdam', '66666666-6666-4400-8000-00000000000f', 'bbbbbbbb-bbbb-4800-8000-00000000000b', '70458 Mary Crest', '', TIMESTAMP '2020-10-01 10:00:00.123456', NULL, 0.0);
- ~~~
-
-5. During the ride, MovR tracks the location of the vehicle.
-
- For example:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > INSERT INTO vehicle_location_histories (city, ride_id, timestamp, lat, long)
- VALUES ('amsterdam', 'cd032f56-cf1a-4800-8000-00000000066f', current_timestamp(), -101, 60);
- ~~~
-
-6. The user ends the ride and releases the vehicle.
-
- For example:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > UPDATE vehicles SET status = 'available' WHERE id='bbbbbbbb-bbbb-4800-8000-00000000000b';
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > UPDATE rides SET end_address ='33862 Charles Junctions Apt. 49', end_time=TIMESTAMP '2020-10-01 10:30:00.123456', revenue=88.6
- WHERE id='cd032f56-cf1a-4800-8000-00000000066f';
- ~~~
diff --git a/src/current/_includes/v20.1/misc/multi-store-nodes.md b/src/current/_includes/v20.1/misc/multi-store-nodes.md
deleted file mode 100644
index 01642597169..00000000000
--- a/src/current/_includes/v20.1/misc/multi-store-nodes.md
+++ /dev/null
@@ -1,3 +0,0 @@
-{{site.data.alerts.callout_danger}}
-In the absence of [special replication constraints](configure-replication-zones.html), CockroachDB rebalances replicas to take advantage of available storage capacity. However, in a 3-node cluster with multiple stores per node, CockroachDB is **not** able to rebalance replicas from one store to another store on the same node because this would temporarily result in the node having multiple replicas of the same range, which is not allowed. This is due to the mechanics of rebalancing, where the cluster first creates a copy of the replica at the target destination before removing the source replica. To allow this type of cross-store rebalancing, the cluster must have 4 or more nodes; this allows the cluster to create a copy of the replica on a node that doesn't already have a replica of the range before removing the source replica and then migrating the new replica to the store with more capacity on the original node.
-{{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/misc/schema-change-stmt-note.md b/src/current/_includes/v20.1/misc/schema-change-stmt-note.md
deleted file mode 100644
index b522b658652..00000000000
--- a/src/current/_includes/v20.1/misc/schema-change-stmt-note.md
+++ /dev/null
@@ -1,3 +0,0 @@
-{{site.data.alerts.callout_info}}
-This statement performs a schema change. For more information about how online schema changes work in CockroachDB, see [Online Schema Changes](online-schema-changes.html).
-{{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/misc/schema-change-view-job.md b/src/current/_includes/v20.1/misc/schema-change-view-job.md
deleted file mode 100644
index 8861174d621..00000000000
--- a/src/current/_includes/v20.1/misc/schema-change-view-job.md
+++ /dev/null
@@ -1 +0,0 @@
-This schema change statement is registered as a job. You can view long-running jobs with [`SHOW JOBS`](show-jobs.html).
diff --git a/src/current/_includes/v20.1/misc/session-vars.html b/src/current/_includes/v20.1/misc/session-vars.html
deleted file mode 100644
index 1c7532d314d..00000000000
--- a/src/current/_includes/v20.1/misc/session-vars.html
+++ /dev/null
@@ -1,585 +0,0 @@
-
-
-
-
diff --git a/src/current/_includes/v20.1/misc/sorting-delete-output.md b/src/current/_includes/v20.1/misc/sorting-delete-output.md
deleted file mode 100644
index fa0d6e54be7..00000000000
--- a/src/current/_includes/v20.1/misc/sorting-delete-output.md
+++ /dev/null
@@ -1,9 +0,0 @@
-To sort the output of a `DELETE` statement, use:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> WITH a AS (DELETE ... RETURNING ...)
- SELECT ... FROM a ORDER BY ...
-~~~
-
-For an example, see [Sort and return deleted rows](delete.html#sort-and-return-deleted-rows).
diff --git a/src/current/_includes/v20.1/misc/tooling.md b/src/current/_includes/v20.1/misc/tooling.md
deleted file mode 100644
index 9c45c3d13c5..00000000000
--- a/src/current/_includes/v20.1/misc/tooling.md
+++ /dev/null
@@ -1,73 +0,0 @@
-## Support levels
-
-We’ve partnered with open-source projects, vendors, and individuals to offer the following levels of support with third-party tools.
-
-- **Full support** indicates that the vast majority of the tool's features should work without issue with CockroachDB. CockroachDB is regularly tested against the recommended version documented here.
-- **Partial support** indicates that the tool has been tried with CockroachDB, but its integration might require additional steps, lack support for all features, or exhibit unexpected behavior.
-
-If you encounter problems, please [open an issue](https://github.com/cockroachdb/cockroach/issues/new) with details to help us make progress toward better support.
-
-## Drivers
-
-| Language | Driver | Recommended version | Support level |
-|----------+--------+---------------------+---------------|
-| C | [libpq](http://www.postgresql.org/docs/9.5/static/libpq.html) | [PostgreSQL 9.5](http://www.postgresql.org/docs/9.5/static/libpq.html) | Beta |
-| C++ | [libpqxx](build-a-c++-app-with-cockroachdb.html) | [7.1.1](https://github.com/jtv/libpqxx/releases) (Windows)
-
-
-
-
-
- Variable name
- Description
- Initial value
- Modify with
-
- SET
- ?View with
-
- SHOW
- ?
-
-
-
-
- application_name
- The current application name for statistics collection.
- Empty string, or
- cockroach for sessions from the built-in SQL client.Yes
- Yes
-
-
-
-
-
- bytea_output
- The mode for conversions from
- STRING to BYTES.hex
- Yes
- Yes
-
-
-
-
-
- crdb_version
- The version of CockroachDB.
- `CockroachDB OSS version`
- No
- Yes
-
-
-
-
-
- database
- The current database.
- Database in connection string, or empty if not specified.
- Yes
- Yes
-
-
-
-
-
- default_int_size
- The size, in bytes, of an
- INT type.
-
- 8
- Yes
- Yes
-
-
-
-
-
- default_transaction_isolation
- All transactions execute with
- SERIALIZABLE isolation. See Transactions: Isolation levels.
-
- SERIALIZABLE
- No
- Yes
-
-
-
-
-
- default_transaction_read_only
- The default transaction access mode for the current session. If set to
- on, only read operations are allowed in transactions in the current session; if set to off, both read and write operations are allowed. See SET TRANSACTION
- for more details.
-
- off
- Yes
- Yes
-
-
-
-
-
- distsql
- The query distribution mode for the session. By default, CockroachDB determines which queries are faster to execute if distributed across multiple nodes, and all other queries are run through the gateway node.
-
-
- auto
- Yes
- Yes
-
-
-
-
-
-
- enable_implicit_select_for_update
- New in v20.1: Indicates whether
- UPDATE statements acquire locks using the FOR UPDATE locking mode during their initial row scan, which improves performance for contended workloads. For more information about how FOR UPDATE locking works, see the documentation for SELECT FOR UPDATE.
-
- on
- Yes
- Yes
-
-
-
-
-
- enable_insert_fast_path
- Indicates whether CockroachDB will use a specialized execution operator for inserting into a table. We recommend leaving this setting
- on.
-
- on
- Yes
- Yes
-
-
-
-
-
- enable_zigzag_join
- Indicates whether the cost-based optimizer will plan certain queries using a zig-zag merge join algorithm, which searches for the desired intersection by jumping back and forth between the indexes based on the fact that after constraining indexes, they share an ordering.
-
-
- on
- Yes
- Yes
-
-
-
-
-
- extra_float_digits
- The number of digits displayed for floating-point values. Only values between
- -15 and 3 are supported.
-
- 0
- Yes
- Yes
-
-
-
-
-
- reorder_joins_limit
- Maximum number of joins that the optimizer will attempt to reorder when searching for an optimal query execution plan. For more information, see Join reordering.
-
-
- 4
- Yes
- Yes
-
-
-
- force_savepoint_restartWhen set to
- true, allows the SAVEPOINT statement to accept any name for a savepoint.
-
- off
- Yes
- Yes
-
-
-
-
-
- locality
- The location of the node. For more information, see Locality.
- Node-dependent
- No
- Yes
-
-
-
-
-
- node_id
- The ID of the node currently connected to.
-
-
This variable is particularly useful for verifying load balanced connections.Node-dependent
- No
- Yes
-
-
-
-
-
- optimizer_foreign_keys
- New in v20.1: If
- off, disables optimizer-driven foreign key checks.
- onYes
- Yes
-
-
-
-
-
- results_buffer_size
- The default size of the buffer that accumulates results for a statement or a batch of statements before they are sent to the client. This can also be set for all connections using the 'sql.defaults.results_buffer_size' cluster setting. Note that auto-retries generally only happen while no results have been delivered to the client, so reducing this size can increase the number of retriable errors a client receives. On the other hand, increasing the buffer size can increase the delay until the client receives the first result row. Setting to 0 disables any buffering.
-
-
- 16384
- Yes
- Yes
-
-
-
-
-
- require_explicit_primary_keys
- New in v20.1: If
- on, CockroachDB throws on error for all tables created without an explicit primary key defined.
-
-
- off
- Yes
- Yes
-
-
-
-
-
- search_path
- A list of schemas that will be searched to resolve unqualified table or function names. For more details, see SQL name resolution.
-
-
- public
- Yes
- Yes
-
-
-
-
-
- server_version
- The version of PostgreSQL that CockroachDB emulates.
- Version-dependent
- No
- Yes
-
-
-
-
-
- server_version_num
- The version of PostgreSQL that CockroachDB emulates.
- Version-dependent
- Yes
- Yes
-
-
-
-
-
- session_id
- The ID of the current session.
- Session-dependent
- No
- Yes
-
-
-
-
-
- session_user
- The user connected for the current session.
- User in connection string
- No
- Yes
-
-
-
-
-
- sql_safe_updates
- If
- false, potentially unsafe SQL statements are allowed, including DROP of a non-empty database and all dependent objects, DELETE without a WHERE clause, UPDATE without a WHERE clause, and ALTER TABLE .. DROP COLUMN. See Allow Potentially Unsafe SQL Statements for more details.
-
- true for interactive sessions from the built-in SQL client,false for sessions from other clientsYes
- Yes
-
-
-
-
-
- statement_timeout
- The amount of time a statement can run before being stopped.
-
-
This value can be an int (e.g., 10) and will be interpreted as milliseconds. It can also be an interval or string argument, where the string can be parsed as a valid interval (e.g., '4s'). A value of 0 turns it off.
-
- 0s
- Yes
- Yes
-
-
-
-
-
- timezone
- The default time zone for the current session.
-
-
This session variable was named "time zone" (with a space) in CockroachDB 1.x. It has been renamed for compatibility with PostgreSQL.
-
- UTC
- Yes
- Yes
-
-
-
-
-
- tracing
- The trace recording state.
-
-
- off
-
-
- Yes
-
-
-
-
-
- transaction_isolation
- All transactions execute with
- SERIALIZABLE isolation. See Transactions: Isolation levels.
-
This session variable was called transaction isolation level (with spaces) in CockroachDB 1.x. It has been renamed for compatibility with PostgreSQL.
-
- SERIALIZABLE
- No
- Yes
-
-
-
-
-
- transaction_priority
- The priority of the current transaction. See Transactions: Transaction priorities for more details.
-
-
This session variable was called transaction priority (with a space) in CockroachDB 1.x. It has been renamed for compatibility with PostgreSQL.
-
- NORMAL
- Yes
- Yes
-
-
-
-
-
- transaction_read_only
- The access mode of the current transaction. See Set Transaction for more details.
-
-
- off
- Yes
- Yes
-
-
-
-
-
- transaction_status
- The state of the current transaction. See Transactions for more details.
-
-
This session variable was called transaction status (with a space) in CockroachDB 1.x. It has been renamed for compatibility with PostgreSQL.
-
- NoTxn
- No
- Yes
-
-
-
-
-
- vectorize
- The vectorized execution engine mode. Options include
- auto, on, and off.
- For more details, see Configuring vectorized execution for CockroachDB.
-
-
- auto
- Yes
- Yes
-
-
-
-
-
- vectorize_row_count_threshold
- The minimum number of rows required to use the vectorized engine to execute a query plan.
-
-
-
- 1000
- Yes
- Yes
-
-
-
-
-
- client_encoding
- (Reserved; exposed only for ORM compatibility.)
-
-
- UTF8
- No
- Yes
-
-
-
-
-
- client_min_messages
- (Reserved; exposed only for ORM compatibility.)
-
-
- notice
- No
- Yes
-
-
-
-
-
- datestyle
- (Reserved; exposed only for ORM compatibility.)
-
-
- ISO
- No
- Yes
-
-
-
-
-
- default_tablespace
- (Reserved; exposed only for ORM compatibility.)
-
-
-
- No
- Yes
-
-
-
-
-
- idle_in_transaction_session_timeout
- (Reserved; exposed only for ORM compatibility.)
-
-
- 0
- No
- Yes
-
-
-
-
-
- integer_datetimes
- (Reserved; exposed only for ORM compatibility.)
-
-
- on
- No
- Yes
-
-
-
-
-
- intervalstyle
- (Reserved; exposed only for ORM compatibility.)
-
-
- postgres
- No
- Yes
-
-
-
-
-
- lock_timeout
- (Reserved; exposed only for ORM compatibility.)
-
-
- 0
- No
- Yes
-
-
-
-
-
- max_identifier_length
- (Reserved; exposed only for ORM compatibility.)
-
-
- 128
- No
- Yes
-
-
-
-
-
- max_index_keys
- (Reserved; exposed only for ORM compatibility.)
-
-
- 32
- No
- Yes
-
-
-
-
-
- row_security
- (Reserved; exposed only for ORM compatibility.)
-
-
- off
- No
- Yes
-
-
-
-
-
- standard_conforming_strings
- (Reserved; exposed only for ORM compatibility.)
-
-
- on
- No
- Yes
-
-
-
-
-
- server_encoding
- (Reserved; exposed only for ORM compatibility.)
-
-
- UTF8
- Yes
- Yes
-
-
-
-
-
-
- synchronize_seqscans
- (Reserved; exposed only for ORM compatibility.)
-
-
- on
- No
- Yes
-
[4.0.1](https://github.com/jtv/libpqxx/releases) or higher (macOS) | Beta |
-| C# (.NET) | [Npgsql](build-a-csharp-app-with-cockroachdb.html) | [4.1.3.1](https://www.nuget.org/packages/Npgsql/) | Beta |
-| Clojure | [java.jdbc](build-a-clojure-app-with-cockroachdb.html) | [0.7.11](https://search.maven.org/search?q=g:org.clojure%20AND%20a:java.jdbc) | Beta |
-| Go | [pgx](build-a-go-app-with-cockroachdb.html)
[pq](build-a-go-app-with-cockroachdb-pq.html) | [4.6.0](https://github.com/jackc/pgx/releases)
[1.5.2](https://github.com/lib/pq/releases) | Full
Full |
-| Java | [JDBC](build-a-java-app-with-cockroachdb.html) | [42.2.9](https://jdbc.postgresql.org/download/) | Full |
-| Node.js | [pg](build-a-nodejs-app-with-cockroachdb.html) | [8.2.1](https://www.npmjs.com/package/pg) | Beta |
-| PHP | [php-pgsql](build-a-php-app-with-cockroachdb.html) | [PHP 7.4.6](https://www.php.net/downloads) | Beta |
-| Python | [psycopg2](build-a-python-app-with-cockroachdb.html) | [2.8.6](https://www.psycopg.org/docs/install.html) | Full |
-| Ruby | [pg](build-a-ruby-app-with-cockroachdb.html) | [1.2.3](https://rubygems.org/gems/pg) | Full |
-| Rust | postgres {% comment %} This link is in HTML instead of Markdown because HTML proofer dies bc of https://github.com/rust-lang/crates.io/issues/163 {% endcomment %} | 0.17.3 | Beta |
-
-## Data access frameworks (e.g., ORMs)
-
-| Language | ORM | Recommended version | Support level |
-|----------+-----+---------------------+---------------|
-| Go | [GORM](build-a-go-app-with-cockroachdb-gorm.html)
[upper/db](build-a-go-app-with-cockroachdb-upperdb.html) | [1.9.11](https://github.com/jinzhu/gorm/releases)
[v4](https://github.com/upper/db/releases) | Full
Full |
-| Java | [Hibernate](build-a-java-app-with-cockroachdb-hibernate.html)
[jOOQ](build-a-java-app-with-cockroachdb-jooq.html)
[MyBatis](build-a-spring-app-with-cockroachdb-mybatis.html) | [5.4.19](https://hibernate.org/orm/releases/)
[3.13.2](https://www.jooq.org/download/versions) (must be 3.13.0 or higher)
[3.5.5 and higher](https://mybatis.org/mybatis-3/) | Full
Full |
-| Node.js | [Sequelize](build-a-nodejs-app-with-cockroachdb-sequelize.html) | [sequelize 5.21.9](https://www.npmjs.com/package/sequelize)
[sequelize-cockroachdb 1.1.0](https://www.npmjs.com/package/sequelize-cockroachdb) | Beta |
-| Ruby | [ActiveRecord](build-a-ruby-app-with-cockroachdb-activerecord.html) | [activerecord 5.2](https://rubygems.org/gems/activerecord/versions)
[activerecord-cockroachdb-adpater 5.2.2](https://rubygems.org/gems/activerecord-cockroachdb-adapter/versions)
[activerecord 6.0](https://rubygems.org/gems/activerecord/versions)
[activerecord-cockroachdb-adpater 6.0.0beta3](https://rubygems.org/gems/activerecord-cockroachdb-adapter/versions) | Full
Beta |
-| Python | [Django](build-a-python-app-with-cockroachdb-django.html)
[peewee](http://docs.peewee-orm.com/en/latest/peewee/playhouse.html#cockroach-database)
[SQLAlchemy](build-a-python-app-with-cockroachdb-sqlalchemy.html) | [Django 3.0.6](https://pypi.org/project/Django/)
[django-cockroachdb 3.0.1](https://pypi.org/project/django-cockroachdb/)
[3.13.3](https://pypi.org/project/peewee/)
[SQLAlchemy 1.3.17](https://pypi.org/project/SQLAlchemy/)
[sqlalchemy-cockroachdb 1.3.0](https://pypi.org/project/sqlalchemy-cockroachdb/) | Full
Full
Full
Full |
-| Typescript | [TypeORM](https://typeorm.io/#/) | [0.2.24](https://www.npmjs.com/package/typeorm) | Full |
-
-## Application frameworks
-
-| Framework | Data access | Recommended version | Support level |
-|-----------+-------------+---------------------+---------------|
-| Spring | [JDBC](build-a-spring-app-with-cockroachdb-jdbc.html)
[JPA (Hibernate)](build-a-spring-app-with-cockroachdb-jpa.html)
jOOQ
[MyBatis](build-a-spring-app-with-cockroachdb-mybatis.html) | See individual Java ORM or [driver](#drivers) for data access version support. | See individual Java ORM or [driver](#drivers) for data access support level. |
-
-## Graphical user interfaces (GUIs)
-
-| GUI | Recommended version | Support level |
-|-----+---------------------+---------------|
-| [Beekeeper Studio](https://beekeeperstudio.io) | [1.6.10 or higher](https://www.beekeeperstudio.io/get) | Full |
-| [DBeaver](https://dbeaver.com/) | [5.2.3 or higher](https://dbeaver.com/download/) | Full |
-| [DbVisualizer](https://www.dbvis.com/) | [10.0.22 or higher](https://www.dbvis.com/download/) | Beta |
-| [Navicat for PostgreSQL](https://www.navicat.com/en/products/navicat-for-postgresql)/[Navicat Premium](https://www.navicat.com/en/products/navicat-premium) | [12.1.25 or higher](https://www.navicat.com/en/download/navicat-for-postgresql) | Beta |
-| [Pgweb](http://sosedoff.github.io/pgweb/) | [0.9.12 or higher](https://github.com/sosedoff/pgweb/releases/latest) | Beta |
-| [Postico](https://eggerapps.at/postico/) | 1.5.8 or higher | Beta |
-| [TablePlus](https://tableplus.com/) | [Build 222 or higher](https://tableplus.com/download) | Beta |
-| [Vault](https://www.vaultproject.io/docs/configuration/storage/cockroachdb) | 1.3.9 or higher | Beta |
-
-## Integrated development environments (IDEs)
-
-| IDE | Recommended version | Support level |
-|-----+---------------------+---------------|
-| [DataGrip](https://www.jetbrains.com/datagrip/) | [2021.1 or higher](https://www.jetbrains.com/datagrip/download) | Full |
-| [IntelliJ IDEA](https://www.jetbrains.com/idea/) | [2021.1 or higher](https://www.jetbrains.com/idea/download) | Beta |
-
-## Schema migration tools
-
-| Tool | Recommended version | Support level |
-|-----+---------------------+---------------|
-| [Flyway](flyway.html) | [6.4.2](https://flywaydb.org/documentation/commandline/#download-and-installation) or higher | Full |
-
-## Other tools
-
-| Tool | Recommended version | Support level |
-|-----+---------------------+---------------|
-| [Flowable](https://blog.flowable.org/2019/07/11/getting-started-with-flowable-and-cockroachdb/) | [6.4.2](https://github.com/flowable/flowable-engine/releases/tag/flowable-6.4.2) or higher | Full |
diff --git a/src/current/_includes/v20.1/orchestration/kubernetes-expand-disk-size.md b/src/current/_includes/v20.1/orchestration/kubernetes-expand-disk-size.md
deleted file mode 100644
index 5f5f77b4962..00000000000
--- a/src/current/_includes/v20.1/orchestration/kubernetes-expand-disk-size.md
+++ /dev/null
@@ -1,184 +0,0 @@
-You can expand certain [types of persistent volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#types-of-persistent-volumes
-) (including GCE Persistent Disk and Amazon Elastic Block Store) by editing their persistent volume claims. Increasing disk size is often beneficial for CockroachDB performance. Read our [Kubernetes performance guide](kubernetes-performance.html#disk-size) for guidance on disks.
-
-1. Get the persistent volume claims for the volumes:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl get pvc
- ~~~
-
- 
-
- 4. To verify that data is being collected, go to **Graph**, enter the `sys_uptime` variable in the field, click **Execute**, and then click the **Graph** tab. The screen should like this:
-
- 
-
- {{site.data.alerts.callout_success}}
- Prometheus auto-completes CockroachDB time series metrics for you, but if you want to see a full listing, with descriptions, port-forward as described in {% if page.secure == true %}[Access the Admin UI](#step-4-access-the-admin-ui){% else %}[Access the Admin UI](#step-4-access-the-admin-ui){% endif %} and then point your browser to http://localhost:8080/_status/vars.
-
- For more details on using the Prometheus UI, see their [official documentation](https://prometheus.io/docs/introduction/getting_started/).
- {{site.data.alerts.end}}
-
-### Configure Alertmanager
-
-Active monitoring helps you spot problems early, but it is also essential to send notifications when there are events that require investigation or intervention. This section shows you how to use [Alertmanager](https://prometheus.io/docs/alerting/alertmanager/) and CockroachDB's starter [alerting rules](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/prometheus/alert-rules.yaml) to do this.
-
-1. Download our alertmanager-config.yaml configuration file:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ curl -OOOOOOOOO \
- https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/prometheus/alertmanager-config.yaml
- ~~~
-
-2. Edit the `alertmanager-config.yaml` file to [specify the desired receivers for notifications](https://prometheus.io/docs/alerting/configuration/#receiver). Initially, the file contains a placeholder web hook.
-
-3. Add this configuration to the Kubernetes cluster as a secret, renaming it to `alertmanager.yaml` and labelling it to make it easier to find:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl create secret generic alertmanager-cockroachdb \
- --from-file=alertmanager.yaml=alertmanager-config.yaml
- ~~~
-
- ~~~
- secret/alertmanager-cockroachdb created
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl label secret alertmanager-cockroachdb app=cockroachdb
- ~~~
-
- ~~~
- secret/alertmanager-cockroachdb labeled
- ~~~
-
- {{site.data.alerts.callout_danger}}
- The name of the secret, `alertmanager-cockroachdb`, must match the name used in the `alertmanager.yaml` file. If they differ, the Alertmanager instance will start without configuration, and nothing will happen.
- {{site.data.alerts.end}}
-
-4. Use our [`alertmanager.yaml`](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/prometheus/alertmanager.yaml) file to create the various objects necessary to run an Alertmanager instance, including a ClusterIP service so that Prometheus can forward alerts:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl apply \
- -f https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/prometheus/alertmanager.yaml
- ~~~
-
- ~~~
- alertmanager.monitoring.coreos.com/cockroachdb created
- service/alertmanager-cockroachdb created
- ~~~
-
-5. Verify that Alertmanager is running:
-
- 1. Port-forward from your local machine to the pod running Alertmanager:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl port-forward alertmanager-cockroachdb-0 9093
- ~~~
-
- 2. Go to http://localhost:9093 in your browser. The screen should look like this:
-
- 
-
-6. Ensure that the Alertmanagers are visible to Prometheus by opening http://localhost:9090/status. The screen should look like this:
-
- 
-
-7. Add CockroachDB's starter [alerting rules](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/prometheus/alert-rules.yaml):
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl apply \
- -f https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/prometheus/alert-rules.yaml
- ~~~
-
- ~~~
- prometheusrule.monitoring.coreos.com/prometheus-cockroachdb-rules created
- ~~~
-
-8. Ensure that the rules are visible to Prometheus by opening http://localhost:9090/rules. The screen should look like this:
-
- 
-
-9. Verify that the `TestAlertManager` example alert is firing by opening http://localhost:9090/alerts. The screen should look like this:
-
- 
-
-10. To remove the example alert:
-
- 1. Use the `kubectl edit` command to open the rules for editing:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl edit prometheusrules prometheus-cockroachdb-rules
- ~~~
-
- 2. Remove the `dummy.rules` block and save the file:
-
- ~~~
- - name: rules/dummy.rules
- rules:
- - alert: TestAlertManager
- expr: vector(1)
- ~~~
diff --git a/src/current/_includes/v20.1/orchestration/kubernetes-remove-nodes-insecure.md b/src/current/_includes/v20.1/orchestration/kubernetes-remove-nodes-insecure.md
deleted file mode 100644
index c983a4c85ab..00000000000
--- a/src/current/_includes/v20.1/orchestration/kubernetes-remove-nodes-insecure.md
+++ /dev/null
@@ -1,130 +0,0 @@
-To safely remove a node from your cluster, you must first decommission the node and only then adjust the `spec.replicas` value of your StatefulSet configuration to permanently remove it. This sequence is important because the decommissioning process lets a node finish in-flight requests, rejects any new requests, and transfers all range replicas and range leases off the node.
-
-{{site.data.alerts.callout_danger}}
-If you remove nodes without first telling CockroachDB to decommission them, you may cause data or even cluster unavailability. For more details about how this works and what to consider before removing nodes, see [Decommission Nodes](remove-nodes.html).
-{{site.data.alerts.end}}
-
-1. Launch a temporary interactive pod and use the `cockroach node status` command to get the internal IDs of nodes:
-
-
When using `minikube`, persistent volumes are external temporary directories that endure until they are manually deleted or until the entire Kubernetes cluster is deleted.
-[persistent volume claim](http://kubernetes.io/docs/user-guide/persistent-volumes/#persistentvolumeclaims) | When pods are created (one per CockroachDB node), each pod will request a persistent volume claim to “claim” durable storage for its node.
-
-## Step 1. Start Kubernetes
-
-1. Follow Kubernetes' [documentation](https://kubernetes.io/docs/tasks/tools/install-minikube/) to install `minikube`, the tool used to run Kubernetes locally, for your OS. This includes installing a hypervisor and `kubectl`, the command-line tool used to manage Kubernetes from your local workstation.
-
- {{site.data.alerts.callout_info}}Make sure you install minikube version 0.21.0 or later. Earlier versions do not include a Kubernetes server that supports the maxUnavailability field and PodDisruptionBudget resource type used in the CockroachDB StatefulSet configuration.{{site.data.alerts.end}}
-
-2. Start a local Kubernetes cluster:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ minikube start
- ~~~
diff --git a/src/current/_includes/v20.1/orchestration/monitor-cluster.md b/src/current/_includes/v20.1/orchestration/monitor-cluster.md
deleted file mode 100644
index 60ff410378f..00000000000
--- a/src/current/_includes/v20.1/orchestration/monitor-cluster.md
+++ /dev/null
@@ -1,69 +0,0 @@
-To access the cluster's [Admin UI](admin-ui-overview.html):
-
-{% if page.secure == true %}
-
-1. On secure clusters, [certain pages of the Admin UI](admin-ui-overview.html#admin-ui-access) can only be accessed by `admin` users.
-
- Get a shell into the pod and start the CockroachDB [built-in SQL client](cockroach-sql.html):
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl exec -it cockroachdb-client-secure \
- -- ./cockroach sql \
- --certs-dir=/cockroach-certs \
- --host=cockroachdb-public
- ~~~
-
-1. Assign `roach` to the `admin` role (you only need to do this once):
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > GRANT admin TO roach;
- ~~~
-
-1. Exit the SQL shell and pod:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > \q
- ~~~
-
-{% endif %}
-
-1. In a new terminal window, port-forward from your local machine to the `cockroachdb-public` service:
-
- port-forward command must be run on the same machine as the web browser in which you want to view the Admin UI. If you have been running these commands from a cloud instance or other non-local shell, you will not be able to view the UI without configuring kubectl locally and running the above port-forward command on your local machine.{{site.data.alerts.end}}
-
-{% if page.secure == true %}
-
-1. Go to https://localhost:8080 and log in with the username and password you created earlier.
-
- {% include {{ page.version.version }}/misc/chrome-localhost.md %}
-
-{% else %}
-
-1. Go to http://localhost:8080.
-
-{% endif %}
-
-1. In the UI, verify that the cluster is running as expected:
- - Click **View nodes list** on the right to ensure that all nodes successfully joined the cluster.
- - Click the **Databases** tab on the left to verify that `bank` is listed.
diff --git a/src/current/_includes/v20.1/orchestration/start-cockroachdb-helm-insecure.md b/src/current/_includes/v20.1/orchestration/start-cockroachdb-helm-insecure.md
deleted file mode 100644
index fea5a620b2a..00000000000
--- a/src/current/_includes/v20.1/orchestration/start-cockroachdb-helm-insecure.md
+++ /dev/null
@@ -1,94 +0,0 @@
-1. [Install the Helm client](https://helm.sh/docs/intro/install) (version 3.0 or higher) and add the `cockroachdb` chart repository:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ helm repo add cockroachdb https://charts.cockroachdb.com/
- ~~~
-
- ~~~
- "cockroachdb" has been added to your repositories
- ~~~
-
-2. Update your Helm chart repositories to ensure that you're using the [latest CockroachDB chart](https://github.com/cockroachdb/helm-charts/blob/master/cockroachdb/Chart.yaml):
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ helm repo update
- ~~~
-
-3. Modify our Helm chart's [`values.yaml`](https://github.com/cockroachdb/helm-charts/blob/master/cockroachdb/values.yaml) parameters for your deployment scenario.
-
- Create a `my-values.yaml` file to override the defaults in `values.yaml`, substituting your own values in this example based on the guidelines below.
-
- {% include copy-clipboard.html %}
- ~~~
- statefulset:
- resources:
- limits:
- memory: "8Gi"
- requests:
- memory: "8Gi"
- conf:
- cache: "2Gi"
- max-sql-memory: "2Gi"
- ~~~
-
- 1. To avoid running out of memory when CockroachDB is not the only pod on a Kubernetes node, you *must* set memory limits explicitly. This is because CockroachDB does not detect the amount of memory allocated to its pod when run in Kubernetes. We recommend setting `conf.cache` and `conf.max-sql-memory` each to 1/4 of the `memory` allocation specified in `statefulset.resources.requests` and `statefulset.resources.limits`.
-
- {{site.data.alerts.callout_success}}
- For example, if you are allocating 8Gi of `memory` to each CockroachDB node, allocate 2Gi to `cache` and 2Gi to `max-sql-memory`.
- {{site.data.alerts.end}}
-
- 2. You may want to modify `storage.persistentVolume.size` and `storage.persistentVolume.storageClass` for your use case. This chart defaults to 100Gi of disk space per pod. For more details on customizing disks for performance, see [these instructions](kubernetes-performance.html#disk-type).
-
- {{site.data.alerts.callout_info}}
- If necessary, you can [expand disk size](orchestrate-cockroachdb-with-kubernetes.html#expand-disk-size) after the cluster is live.
- {{site.data.alerts.end}}
-
-4. Install the CockroachDB Helm chart.
-
- Provide a "release" name to identify and track this particular deployment of the chart, and override the default values with those in `my-values.yaml`.
-
- {{site.data.alerts.callout_info}}
- This tutorial uses `my-release` as the release name. If you use a different value, be sure to adjust the release name in subsequent commands. Also be sure to start and end the name with an alphanumeric character and otherwise use lowercase alphanumeric characters, `-`, or `.` so as to comply with [CSR naming requirements](orchestrate-cockroachdb-with-kubernetes.html#csr-names).
- {{site.data.alerts.end}}
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ helm install my-release --values my-values.yaml cockroachdb/cockroachdb
- ~~~
-
- Behind the scenes, this command uses our `cockroachdb-statefulset.yaml` file to create the StatefulSet that automatically creates 3 pods, each with a CockroachDB node running inside it, where each pod has distinguishable network identity and always binds back to the same persistent storage on restart.
-
-5. Confirm that CockroachDB cluster initialization has completed successfully, with the pods for CockroachDB showing `1/1` under `READY` and the pod for initialization showing `COMPLETED` under `STATUS`:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl get pods
- ~~~
-
- ~~~
- NAME READY STATUS RESTARTS AGE
- my-release-cockroachdb-0 1/1 Running 0 8m
- my-release-cockroachdb-1 1/1 Running 0 8m
- my-release-cockroachdb-2 1/1 Running 0 8m
- my-release-cockroachdb-init-hxzsc 0/1 Completed 0 1h
- ~~~
-
-6. Confirm that the persistent volumes and corresponding claims were created successfully for all three pods:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl get pv
- ~~~
-
- ~~~
- NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
- pvc-71019b3a-fc67-11e8-a606-080027ba45e5 100Gi RWO Delete Bound default/datadir-my-release-cockroachdb-0 standard 11m
- pvc-7108e172-fc67-11e8-a606-080027ba45e5 100Gi RWO Delete Bound default/datadir-my-release-cockroachdb-1 standard 11m
- pvc-710dcb66-fc67-11e8-a606-080027ba45e5 100Gi RWO Delete Bound default/datadir-my-release-cockroachdb-2 standard 11m
- ~~~
-
-{{site.data.alerts.callout_success}}
-The StatefulSet configuration sets all CockroachDB nodes to log to `stderr`, so if you ever need access to a pod/node's logs to troubleshoot, use `kubectl logs 
-
-To check at a more granular level, SSH to one of the instances not running CockroachDB and run the `SHOW EXPERIMENTAL_RANGES` statement on the `vehicles` table:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach sql \
-{{page.certs}} \
---host= \
---database=movr \
---execute="SELECT * FROM \
-[SHOW EXPERIMENTAL_RANGES FROM TABLE vehicles] \
-WHERE \"start_key\" IS NOT NULL \
- AND \"start_key\" NOT LIKE '%Prefix%';"
-~~~
-
-~~~
- start_key | end_key | range_id | replicas | lease_holder
-+------------------+----------------------------+----------+----------+--------------+
- /"boston" | /"boston"/PrefixEnd | 105 | {1,2,3} | 3
- /"los angeles" | /"los angeles"/PrefixEnd | 121 | {7,8,9} | 8
- /"new york" | /"new york"/PrefixEnd | 101 | {1,2,3} | 3
- /"san francisco" | /"san francisco"/PrefixEnd | 117 | {7,8,9} | 8
- /"seattle" | /"seattle"/PrefixEnd | 113 | {4,5,6} | 5
- /"washington dc" | /"washington dc"/PrefixEnd | 109 | {1,2,3} | 1
-(6 rows)
-~~~
-
-For reference, here's how the nodes map to zones:
-
-Node IDs | Zone
----------|-----
-1-3 | `us-east1-b` (South Carolina)
-4-6 | `us-west1-a` (Oregon)
-7-9 | `us-west2-a` (Los Angeles)
-
-We can see that, after partitioning, the replicas for New York, Boston, and Washington DC are located on nodes 1-3 in `us-east1-b`, replicas for Seattle are located on nodes 4-6 in `us-west1-a`, and replicas for San Francisco and Los Angeles are located on nodes 7-9 in `us-west2-a`.
diff --git a/src/current/_includes/v20.1/performance/check-rebalancing.md b/src/current/_includes/v20.1/performance/check-rebalancing.md
deleted file mode 100644
index a5e5e5b3005..00000000000
--- a/src/current/_includes/v20.1/performance/check-rebalancing.md
+++ /dev/null
@@ -1,33 +0,0 @@
-Since you started each node with the `--locality` flag set to its GCE zone, over the next minutes, CockroachDB will rebalance data evenly across the zones.
-
-To check this, access the Admin UI on any node at `
-
-For reference, here's how the nodes map to zones:
-
-Node IDs | Zone
----------|-----
-1-3 | `us-east1-b` (South Carolina)
-4-6 | `us-west1-a` (Oregon)
-7-9 | `us-west2-a` (Los Angeles)
-
-To verify even balancing at range level, SSH to one of the instances not running CockroachDB and run the `SHOW EXPERIMENTAL_RANGES` statement:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach sql \
-{{page.certs}} \
---host= \
---database=movr \
---execute="SHOW EXPERIMENTAL_RANGES FROM TABLE vehicles;"
-~~~
-
-~~~
- start_key | end_key | range_id | replicas | lease_holder
-+-----------+---------+----------+----------+--------------+
- NULL | NULL | 33 | {3,4,7} | 7
-(1 row)
-~~~
-
-In this case, we can see that, for the single range containing `vehicles` data, one replica is in each zone, and the leaseholder is in the `us-west2-a` zone.
diff --git a/src/current/_includes/v20.1/performance/configure-network.md b/src/current/_includes/v20.1/performance/configure-network.md
deleted file mode 100644
index 7cd3e3cbcc6..00000000000
--- a/src/current/_includes/v20.1/performance/configure-network.md
+++ /dev/null
@@ -1,18 +0,0 @@
-CockroachDB requires TCP communication on two ports:
-
-- **26257** (`tcp:26257`) for inter-node communication (i.e., working as a cluster)
-- **8080** (`tcp:8080`) for accessing the Admin UI
-
-Since GCE instances communicate on their internal IP addresses by default, you do not need to take any action to enable inter-node communication. However, to access the Admin UI from your local network, you must [create a firewall rule for your project](https://cloud.google.com/vpc/docs/using-firewalls):
-
-Field | Recommended Value
-------|------------------
-Name | **cockroachweb**
-Source filter | IP ranges
-Source IP ranges | Your local network's IP ranges
-Allowed protocols | **tcp:8080**
-Target tags | `cockroachdb`
-
-{{site.data.alerts.callout_info}}
-The **tag** feature will let you easily apply the rule to your instances.
-{{site.data.alerts.end}}
diff --git a/src/current/_includes/v20.1/performance/import-movr.md b/src/current/_includes/v20.1/performance/import-movr.md
deleted file mode 100644
index a0fe2dc710a..00000000000
--- a/src/current/_includes/v20.1/performance/import-movr.md
+++ /dev/null
@@ -1,160 +0,0 @@
-Now you'll import Movr data representing users, vehicles, and rides in 3 eastern US cities (New York, Boston, and Washington DC) and 3 western US cities (Los Angeles, San Francisco, and Seattle).
-
-1. Still on the fourth instance, start the [built-in SQL shell](cockroach-sql.html), pointing it at one of the CockroachDB nodes:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ cockroach sql {{page.certs}} --host=
- ~~~
-
-2. Create the `movr` database and set it as the default:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > CREATE DATABASE movr;
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > SET DATABASE = movr;
- ~~~
-
-3. Use the [`IMPORT`](import.html) statement to create and populate the `users`, `vehicles,` and `rides` tables:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > IMPORT TABLE users (
- id UUID NOT NULL,
- city STRING NOT NULL,
- name STRING NULL,
- address STRING NULL,
- credit_card STRING NULL,
- CONSTRAINT "primary" PRIMARY KEY (city ASC, id ASC)
- )
- CSV DATA (
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/users/n1.0.csv'
- );
- ~~~
-
- ~~~
- job_id | status | fraction_completed | rows | index_entries | system_records | bytes
- +--------------------+-----------+--------------------+------+---------------+----------------+--------+
- 390345990764396545 | succeeded | 1 | 1998 | 0 | 0 | 241052
- (1 row)
-
- Time: 2.882582355s
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > IMPORT TABLE vehicles (
- id UUID NOT NULL,
- city STRING NOT NULL,
- type STRING NULL,
- owner_id UUID NULL,
- creation_time TIMESTAMP NULL,
- status STRING NULL,
- ext JSON NULL,
- mycol STRING NULL,
- CONSTRAINT "primary" PRIMARY KEY (city ASC, id ASC),
- INDEX vehicles_auto_index_fk_city_ref_users (city ASC, owner_id ASC)
- )
- CSV DATA (
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/vehicles/n1.0.csv'
- );
- ~~~
-
- ~~~
- job_id | status | fraction_completed | rows | index_entries | system_records | bytes
- +--------------------+-----------+--------------------+-------+---------------+----------------+---------+
- 390346109887250433 | succeeded | 1 | 19998 | 19998 | 0 | 3558767
- (1 row)
-
- Time: 5.803841493s
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > IMPORT TABLE rides (
- id UUID NOT NULL,
- city STRING NOT NULL,
- vehicle_city STRING NULL,
- rider_id UUID NULL,
- vehicle_id UUID NULL,
- start_address STRING NULL,
- end_address STRING NULL,
- start_time TIMESTAMP NULL,
- end_time TIMESTAMP NULL,
- revenue DECIMAL(10,2) NULL,
- CONSTRAINT "primary" PRIMARY KEY (city ASC, id ASC),
- INDEX rides_auto_index_fk_city_ref_users (city ASC, rider_id ASC),
- INDEX rides_auto_index_fk_vehicle_city_ref_vehicles (vehicle_city ASC, vehicle_id ASC),
- CONSTRAINT check_vehicle_city_city CHECK (vehicle_city = city)
- )
- CSV DATA (
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/rides/n1.0.csv',
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/rides/n1.1.csv',
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/rides/n1.2.csv',
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/rides/n1.3.csv',
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/rides/n1.4.csv',
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/rides/n1.5.csv',
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/rides/n1.6.csv',
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/rides/n1.7.csv',
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/rides/n1.8.csv',
- 'https://s3-us-west-1.amazonaws.com/cockroachdb-movr/datasets/perf-tuning/rides/n1.9.csv'
- );
- ~~~
-
- ~~~
- job_id | status | fraction_completed | rows | index_entries | system_records | bytes
- +--------------------+-----------+--------------------+--------+---------------+----------------+-----------+
- 390346325693792257 | succeeded | 1 | 999996 | 1999992 | 0 | 339741841
- (1 row)
-
- Time: 44.620371424s
- ~~~
-
- {{site.data.alerts.callout_success}}
- You can observe the progress of imports as well as all schema change operations (e.g., adding secondary indexes) on the [**Jobs** page](admin-ui-jobs-page.html) of the Admin UI.
- {{site.data.alerts.end}}
-
-7. Logically, there should be a number of [foreign key](foreign-key.html) relationships between the tables:
-
- Referencing columns | Referenced columns
- --------------------|-------------------
- `vehicles.city`, `vehicles.owner_id` | `users.city`, `users.id`
- `rides.city`, `rides.rider_id` | `users.city`, `users.id`
- `rides.vehicle_city`, `rides.vehicle_id` | `vehicles.city`, `vehicles.id`
-
- As mentioned earlier, it wasn't possible to put these relationships in place during `IMPORT`, but it was possible to create the required secondary indexes. Now, let's add the foreign key constraints:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > ALTER TABLE vehicles
- ADD CONSTRAINT fk_city_ref_users
- FOREIGN KEY (city, owner_id)
- REFERENCES users (city, id);
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > ALTER TABLE rides
- ADD CONSTRAINT fk_city_ref_users
- FOREIGN KEY (city, rider_id)
- REFERENCES users (city, id);
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > ALTER TABLE rides
- ADD CONSTRAINT fk_vehicle_city_ref_vehicles
- FOREIGN KEY (vehicle_city, vehicle_id)
- REFERENCES vehicles (city, id);
- ~~~
-
-4. Exit the built-in SQL shell:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > \q
- ~~~
diff --git a/src/current/_includes/v20.1/performance/overview.md b/src/current/_includes/v20.1/performance/overview.md
deleted file mode 100644
index 66c28ede405..00000000000
--- a/src/current/_includes/v20.1/performance/overview.md
+++ /dev/null
@@ -1,38 +0,0 @@
-### Topology
-
-You'll start with a 3-node CockroachDB cluster in a single Google Compute Engine (GCE) zone, with an extra instance for running a client application workload:
-
-
-
-{{site.data.alerts.callout_info}}
-Within a single GCE zone, network latency between instances should be sub-millisecond.
-{{site.data.alerts.end}}
-
-You'll then scale the cluster to 9 nodes running across 3 GCE regions, with an extra instance in each region for a client application workload:
-
-
-
-{{site.data.alerts.callout_info}}
-Network latencies will increase with geographic distance between nodes. You can observe this in the [Network Latency page](admin-ui-network-latency-page.html) of the Admin UI.
-{{site.data.alerts.end}}
-
-To reproduce the performance demonstrated in this tutorial:
-
-- For each CockroachDB node, you'll use the [`n2-standard-4`](https://cloud.google.com/compute/docs/machine-types#standard_machine_types) machine type (4 vCPUs, 16 GB memory) with the Ubuntu 16.04 OS image and a [local SSD](https://cloud.google.com/compute/docs/disks/#localssds) disk.
-- For running the client application workload, you'll use smaller instances, such as `n2-standard-2`.
-
-### Schema
-
-Your schema and data will be based on our open-source, fictional peer-to-peer vehicle-sharing application, [MovR](movr.html).
-
-
-
-A few notes about the schema:
-
-- There are just three self-explanatory tables: In essence, `users` represents the people registered for the service, `vehicles` represents the pool of vehicles for the service, and `rides` represents when and where users have participated.
-- Each table has a composite primary key, with `city` being first in the key. Although not necessary initially in the single-region deployment, once you scale the cluster to multiple regions, these compound primary keys will enable you to [geo-partition data at the row level](partitioning.html#partition-using-primary-key) by `city`. As such, this tutorial demonstrates a schema designed for future scaling.
-- The [`IMPORT`](import.html) feature you'll use to import the data does not support foreign keys, so you'll import the data without [foreign key constraints](foreign-key.html). However, the import will create the secondary indexes required to add the foreign keys later.
-
-### Important concepts
-
-To understand the techniques in this tutorial, and to be able to apply them in your own scenarios, it's important to first understand [how reads and writes work in CockroachDB](architecture/reads-and-writes-overview.html). Review that document before getting started here.
diff --git a/src/current/_includes/v20.1/performance/partition-by-city.md b/src/current/_includes/v20.1/performance/partition-by-city.md
deleted file mode 100644
index 0a29ac78d89..00000000000
--- a/src/current/_includes/v20.1/performance/partition-by-city.md
+++ /dev/null
@@ -1,419 +0,0 @@
-For this service, the most effective technique for improving read and write latency is to [geo-partition](partitioning.html) the data by city. In essence, this means changing the way data is mapped to ranges. Instead of an entire table and its indexes mapping to a specific range or set of ranges, all rows in the table and its indexes with a given city will map to a range or set of ranges. Once ranges are defined in this way, we can then use the [replication zone](configure-replication-zones.html) feature to pin partitions to specific locations, ensuring that read and write requests from users in a specific city do not have to leave that region.
-
-1. Partitioning is an enterprise feature, so start off by [registering for a 30-day trial license](https://www.cockroachlabs.com/get-cockroachdb/enterprise/).
-
-2. Once you've received the trial license, SSH to any node in your cluster and [apply the license](licensing-faqs.html#set-a-license):
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ cockroach sql \
- {{page.certs}} \
- --host= \
- --execute="SET CLUSTER SETTING cluster.organization = '
This value must route to an IP address the node is listening on (with `--listen-addr` unspecified, the node listens on all IP addresses).
In some networking scenarios, you may need to use `--advertise-addr` and/or `--listen-addr` differently. For more details, see [Networking](recommended-production-settings.html#networking).
-`--join` | Identifies the address of 3-5 of the initial nodes of the cluster. These addresses should match the addresses that the target nodes are advertising.
diff --git a/src/current/_includes/v20.1/prod-deployment/aws-inbound-rules.md b/src/current/_includes/v20.1/prod-deployment/aws-inbound-rules.md
deleted file mode 100644
index b44a170c6f2..00000000000
--- a/src/current/_includes/v20.1/prod-deployment/aws-inbound-rules.md
+++ /dev/null
@@ -1,22 +0,0 @@
-#### Inter-node and load balancer-node communication
-
- Field | Value
--------|-------------------
- Port Range | **26257**
- Source | The ID of your security group (e.g., *sg-07ab277a*)
-
-#### Application data
-
- Field | Value
--------|-------------------
- Port Range | **26257**
- Source | Your application's IP ranges
-
-#### Admin UI
-
- Field | Value
--------|-------------------
- Port Range | **8080**
- Source | Your network's IP ranges
-
-You can set your network IP by selecting "My IP" in the Source field.
\ No newline at end of file
diff --git a/src/current/_includes/v20.1/prod-deployment/backup.sh b/src/current/_includes/v20.1/prod-deployment/backup.sh
deleted file mode 100644
index efcbd4c7041..00000000000
--- a/src/current/_includes/v20.1/prod-deployment/backup.sh
+++ /dev/null
@@ -1,21 +0,0 @@
-#!/bin/bash
-
-set -euo pipefail
-
-# This script creates full backups when run on the configured
-# day of the week and incremental backups when run on other days, and tracks
-# recently created backups in a file to pass as the base for incremental backups.
-
-what="" # Leave empty for cluster backup, or add "DATABASE database_name" to backup a database.
-base="