Command-Line Interface Changes
- -- New commands `cockroach node decommission` and `cockroach quit --decommission` can be used to permanently and safely remove nodes from a cluster. [#17272](https://github.com/cockroachdb/cockroach/pull/17272) -- The [`cockroach node status`](https://www.cockroachlabs.com/docs/v1.1/view-node-details) command now supports several new flags to return subsets of a node's information. [#17555](https://github.com/cockroachdb/cockroach/pull/17555) - -Admin UI Changes
- -- Running jobs (schema changes and enterprise backup/restore) now show their estimated time remaining, instead of estimated total running time. [#17559](https://github.com/cockroachdb/cockroach/pull/17559) -- Decommissioned nodes are now reflected in the UI. [#17553](https://github.com/cockroachdb/cockroach/pull/17553) - -Bug Fixes
- -- [View](https://www.cockroachlabs.com/docs/v1.1/views) dependency analysis (which prevents `DROP` of tables that are used by views) is more accurate for newly-created views. [#17310](https://github.com/cockroachdb/cockroach/pull/17310) -- Range splits are no longer allowed in the `meta2` range; this limits the scalability of a cluster but prevents certain panics in large clusters. [#17565](https://github.com/cockroachdb/cockroach/pull/17565) -- 3DES has been removed from the list of supported TLS cipher suites (it would never be selected because we require TLS 1.2, but it could be reported as a false positive by security scanners). [#17237](https://github.com/cockroachdb/cockroach/pull/17237) -- Fixed a panic in destroyed replicas. [#17303](https://github.com/cockroachdb/cockroach/pull/17303) -- `ALTER TABLE ... SCATTER` once again returns information about the affected ranges. [#17409](https://github.com/cockroachdb/cockroach/pull/17409) -- Fixed a data race in table leases. [#17510](https://github.com/cockroachdb/cockroach/pull/17510) -- [Time-travel queries](https://www.cockroachlabs.com/docs/v1.1/select#select-historical-data-time-travel) can no longer read tables before they were created. [#17378](https://github.com/cockroachdb/cockroach/pull/17378) - -Performance Improvements
- -- The `rocksdb.min_wal_sync_interval` [cluster setting](https://www.cockroachlabs.com/docs/v1.1/cluster-settings) now defaults to zero, improving write performance in most cases. [#17601](https://github.com/cockroachdb/cockroach/pull/17601) -- Results are now streamed back to the client as they are produced instead of being buffered. [#17019](https://github.com/cockroachdb/cockroach/pull/17019) -- Query processing can now take advantage of on-disk storage, rather than erroring out when the working set of the query is too large to fit in memory. This is turned off by default in this release, but can be enabled by setting the `sql.defaults.distsql.tempstorage` [cluster setting](https://www.cockroachlabs.com/docs/v1.1/cluster-settings) to true. -- Improved diversity-based rebalancing of replicas. [#17570](https://github.com/cockroachdb/cockroach/pull/17570) -- Stats-based rebalancing handles empty stores and ranges better. [#17593](https://github.com/cockroachdb/cockroach/pull/17593) - -Doc Updates
- -- Updated the [Go-specific transaction code sample](https://www.cockroachlabs.com/docs/v1.1/build-a-go-app-with-cockroachdb#transaction-with-retry-logic). [#1816](https://github.com/cockroachdb/docs/pull/1816) -- Updated the flag and response field definitions for the [`cockroach version`](https://www.cockroachlabs.com/docs/v1.1/view-version-details) command. diff --git a/src/current/_includes/releases/v1.1/v1.1-beta.20170907.md b/src/current/_includes/releases/v1.1/v1.1-beta.20170907.md deleted file mode 100644 index 3e8bb0ea722..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1-beta.20170907.md +++ /dev/null @@ -1,128 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -Backwards-Incompatible Changes
- -- [`DROP DATABASE`](https://www.cockroachlabs.com/docs/v1.1/drop-database) no longer drops non-empty databases unless the `CASCADE` modifier is added. [#17926](https://github.com/cockroachdb/cockroach/pull/17926) -- The `--cache` and `--max-sql-memory` flags for the [`cockroach start`](https://www.cockroachlabs.com/docs/v1.1/start-a-node) command now default to 128MiB instead of 25% of physical memory to avoid using too much memory by default. Production deployments are encouraged to set `--cache` explicitly to 25-50% of the memory allocated to CockroachDB for best performance. [#18040](https://github.com/cockroachdb/cockroach/pull/18040) - -SQL Language Changes
- -- The new [`IMPORT`](https://www.cockroachlabs.com/docs/v1.1/import) statement provides a fast way to import an entire table's data into CockroachDB by loading CSV files. Although this feature uses [CCL-licensed code](https://www.cockroachlabs.com/cockroachdb-community-license/), and is therefore available only in builds that include CCL-licensed code, using it is free and does not require an enterprise license. [#17539](https://github.com/cockroachdb/cockroach/pull/17539) -- The [`DELETE`](https://www.cockroachlabs.com/docs/v1.1/delete) and [`UPDATE`](https://www.cockroachlabs.com/docs/v1.1/update) statements now support `ORDER BY` and `LIMIT` clauses. [#18023](https://github.com/cockroachdb/cockroach/pull/18023) -- The `sql_safe_updates` [session variable](https://www.cockroachlabs.com/docs/v1.1/set-vars) can be set to disable certain "dangerous" SQL statements, such as `DELETE` or `UPDATE` without a `WHERE` clause. This is set by default in the `cockroach sql` shell. [#17604](https://github.com/cockroachdb/cockroach/pull/17604) [#17889](https://github.com/cockroachdb/cockroach/pull/17889) -- Parsing of the [`DATE`](https://www.cockroachlabs.com/docs/v1.1/date) type is no longer affected by the session time zone. [#18164](https://github.com/cockroachdb/cockroach/pull/18164) -- Type hints are now permitted even when they are imprecise, improving compatibility with some drivers and frameworks. [#16672](https://github.com/cockroachdb/cockroach/pull/16672) -- Untyped string literals can now be implicitly cast to numbers, improving compatibility with Javascript clients. [#15903](https://github.com/cockroachdb/cockroach/pull/15903) -- [Query cancellation](https://www.cockroachlabs.com/docs/v1.1/cancel-query) is now supported for queries using the distributed SQL engine. [#17527](https://github.com/cockroachdb/cockroach/pull/17527) -- The output of [`SHOW SESSIONS`](https://www.cockroachlabs.com/docs/v1.1/show-sessions) now includes a `last_active_query` column. [#17579](https://github.com/cockroachdb/cockroach/pull/17579) -- The [`SET TRANSACTION`](https://www.cockroachlabs.com/docs/v1.1/set-transaction) statement no longer requires commas when multiple directives are given. [#17723](https://github.com/cockroachdb/cockroach/pull/17723) -- The PostgreSQL-compatible `e'\x0d0a...'` syntax for hex-encoded byte literals is now supported. [#17693](https://github.com/cockroachdb/cockroach/pull/17693) -- Star expansion is now supported in more cases. [#17833](https://github.com/cockroachdb/cockroach/pull/17833) -- The [`information_schema.sequences`](https://www.cockroachlabs.com/docs/v1.1/information-schema) table is now supported; it is always empty as sequences are not yet supported. [#17804](https://github.com/cockroachdb/cockroach/pull/17804) -- Improved support for `GROUP BY` and `ORDER BY` with tuples. [#17888](https://github.com/cockroachdb/cockroach/pull/17888) -- Statements that spawn jobs ([`BACKUP`](https://www.cockroachlabs.com/docs/v1.1/backup), [`RESTORE`](https://www.cockroachlabs.com/docs/v1.1/restore), schema changes) no longer appear in [`SHOW QUERIES`](https://www.cockroachlabs.com/docs/v1.1/show-queries). [#17786](https://github.com/cockroachdb/cockroach/pull/17786) -- The `CANCEL`, `RESUME`, `PAUSE`, `BACKUP`, `RESTORE`, and `IMPORT` statements are now valid in prepared statements. The `SET` statement now supports placeholders for values in prepared statements. [#17805](https://github.com/cockroachdb/cockroach/pull/17805) [#17591](https://github.com/cockroachdb/cockroach/pull/17591) - -Command-Line Interface Changes
- -- Fatal error messages are now printed to both `stderr` and the logs. [#17588](https://github.com/cockroachdb/cockroach/pull/17588) -- The [`cockroach dump`](https://www.cockroachlabs.com/docs/v1.1/sql-dump) command now understands [views](https://www.cockroachlabs.com/docs/v1.1/views) and orders tables to satisfy [foreign key constraints](https://www.cockroachlabs.com/docs/v1.1/foreign-key) (as long as there are no cycles). [#17581](https://github.com/cockroachdb/cockroach/pull/17581) -- The [`cockroach dump`](https://www.cockroachlabs.com/docs/v1.1/sql-dump) command correctly represents values such as `NaN` and `Inf`. [#18031](https://github.com/cockroachdb/cockroach/pull/18031) -- The [`cockroach sql`](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client) shell now supports a `h` command for "help". Context-sensitive syntax help is available by typing a question mark followed by the tab key while typing a command. [#13540](https://github.com/cockroachdb/cockroach/pull/13540) -- The [`cockroach sql`](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client) shell now sets a default `application_name` of `cockroach`. [#17602](https://github.com/cockroachdb/cockroach/pull/17602) -- The [`cockroach sql`](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client) shell now prints hints and warnings when available from the server. [#17604](https://github.com/cockroachdb/cockroach/pull/17604) -- The [`cockroach sql`](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client) shell has new debugging options `set echo` (and an equivalent command-line flag `--echo-sql`) and `unset smart_prompt`. [#18127](https://github.com/cockroachdb/cockroach/pull/18127) - -Admin UI Changes
- -- Various debugging pages are now available at `/#/debug`. [#17635](https://github.com/cockroachdb/cockroach/pull/17635) -- Changes to [cluster settings](https://www.cockroachlabs.com/docs/v1.1/cluster-settings) are now recorded in the event log. [#17619](https://github.com/cockroachdb/cockroach/pull/17619) [#17866](https://github.com/cockroachdb/cockroach/pull/17866) -- The **Live Bytes per Store** graph has been replaced with **Logical Bytes per Store**, which includes the size of old MVCC values waiting to be garbage collected. [#17782](https://github.com/cockroachdb/cockroach/pull/17782) -- The `/debug/vmodule/` endpoint has been removed; use the SQL function `crdb_internal.set_vmodule()` instead. [#17792](https://github.com/cockroachdb/cockroach/pull/17792) [#17914](https://github.com/cockroachdb/cockroach/pull/17914) -- When [diagnostic reporting](https://www.cockroachlabs.com/docs/v1.1/diagnostics-reporting) is enabled, anonymous web analytics are also collected in the admin UI. [#17937](https://github.com/cockroachdb/cockroach/pull/17937) [#18046](https://github.com/cockroachdb/cockroach/pull/18046) [#18125](https://github.com/cockroachdb/cockroach/pull/18125) -- Local tracing is now always enabled when nodes start up (even though it will be disabled by default when the node is fully initialized). This helps diagnose problems that keep a node from joining its cluster. [#17944](https://github.com/cockroachdb/cockroach/pull/17944) -- Various adjustments to fonts and margins. [#16773](https://github.com/cockroachdb/cockroach/pull/16773) [#17673](https://github.com/cockroachdb/cockroach/pull/17673) - -Bug Fixes
- -- Fixed a regression in the command queue (introduced in `alpha-20170810`) that could result in data inconsistencies. [#17939](https://github.com/cockroachdb/cockroach/pull/17939) -- Fixed a bug in range quiescence that could result in some ranges getting stuck indefinitely. [#18184](https://github.com/cockroachdb/cockroach/pull/18184) -- [Foreign keys](https://www.cockroachlabs.com/docs/v1.1/foreign-key) that point to a prefix of an existing index now work correctly. Previously, rows could be deleted from the referenced table without recognizing the constraint violation if rows in the referring table pointed to them. These foreign keys are also now shown correctly in [`SHOW CREATE TABLE`](https://www.cockroachlabs.com/docs/v1.1/show-create-table). [#17638](https://github.com/cockroachdb/cockroach/pull/17638) -- Fixed a bug in `ReverseScan` that could cause data to be missing from query results. [#17868](https://github.com/cockroachdb/cockroach/pull/17868) -- Fixed a build error on FreeBSD. [#17650](https://github.com/cockroachdb/cockroach/pull/17650) -- Windows builds no longer fail with `SyncWAL` errors. [#17735](https://github.com/cockroachdb/cockroach/pull/17735) -- Improved error handling to reduce panics when unsupported SQL features are attempted. [#17521](https://github.com/cockroachdb/cockroach/pull/17521) -- Corrected computation of lease type metrics. [#17615](https://github.com/cockroachdb/cockroach/pull/17615) -- More errors now return the correct PostgreSQL error code, and use the protocol's "hint" and "detail" fields. [#17630](https://github.com/cockroachdb/cockroach/pull/17630) [#17708](https://github.com/cockroachdb/cockroach/pull/17708) [#18028](https://github.com/cockroachdb/cockroach/pull/18028) [#13540](https://github.com/cockroachdb/cockroach/pull/13540) -- Improved error message for parse errors containing funny characters like carriage returns. [#18095](https://github.com/cockroachdb/cockroach/pull/18095) -- Queries are not removed from [`SHOW QUERIES`](https://www.cockroachlabs.com/docs/v1.1/show-queries) or [`SHOW SESSIONS`](https://www.cockroachlabs.com/docs/v1.1/show-sessions) until all their results have been sent to the client. [#17579](https://github.com/cockroachdb/cockroach/pull/17579) -- The crash reporter will now time out instead of waiting indefinitely to reach the server. [#17683](https://github.com/cockroachdb/cockroach/pull/17683) -- gRPC no longer closes inter-node connections unnecessarily. [#17706](https://github.com/cockroachdb/cockroach/pull/17706) -- Fixed `duplicate key value` errors when performing large number of splits. [#17763](https://github.com/cockroachdb/cockroach/pull/17763) -- Fixed a deadlock in `quotaPool`. [#17796](https://github.com/cockroachdb/cockroach/pull/17796) -- Fixed a deadlock in `RangeLookup` during `SCATTER`. [#17760](https://github.com/cockroachdb/cockroach/pull/17760) -- The distributed SQL engine avoids scheduling work on nodes running an incompatible version. [#17747](https://github.com/cockroachdb/cockroach/pull/17747) -- `AS OF SYSTEM TIME 0` is now a normal error instead of a panic. [#17680](https://github.com/cockroachdb/cockroach/pull/17680) -- Fixed a panic in `distSQLPlanner`. [#17852](https://github.com/cockroachdb/cockroach/pull/17852) -- Fixed a flow control leak that could lead to deadlock. [#17856](https://github.com/cockroachdb/cockroach/pull/17856) -- Parallelized queries now handle retryable errors correctly. [#17627](https://github.com/cockroachdb/cockroach/pull/17627) -- Nodes now panic if they fail a consistency check. The `server.consistency_check.interval` [cluster setting](https://www.cockroachlabs.com/docs/v1.1/cluster-settings) replaces the `COCKROACH_CONSISTENCY_CHECK_INTERVAL` environment variable for configuring the consistency checker. [#17853](https://github.com/cockroachdb/cockroach/pull/17853) -- [Dropping an interleaved index](https://www.cockroachlabs.com/docs/v1.1/drop-index) no longer leaves the table in a broken state. [#17860](https://github.com/cockroachdb/cockroach/pull/17860) -- Changed "flow already registered" from a panic to a regular error. [#17876](https://github.com/cockroachdb/cockroach/pull/17876) -- Certain code paths that used to panic on invalid UTF-8 inputs now return an error instead. [#17935](https://github.com/cockroachdb/cockroach/pull/17935) -- Fixed a memory accounting panic in top-K sorting. [#17984](https://github.com/cockroachdb/cockroach/pull/17984) -- It is no longer possible to set the `kv.raft.command.max_size` cluster setting to a very low value (which could make the cluster inoperable). [#17991](https://github.com/cockroachdb/cockroach/pull/17991) - -Performance Improvements
- -- Stats-based rebalancing is now disabled by default. [#17968](https://github.com/cockroachdb/cockroach/pull/17968) -- Reduced unnecessary rebalancing. [#17613](https://github.com/cockroachdb/cockroach/pull/17613) -- The rebalancer now avoids removing the most recently-added replica. [#17930](https://github.com/cockroachdb/cockroach/pull/17930) -- Increased the size of the leaseholder cache. [#17623](https://github.com/cockroachdb/cockroach/pull/17623) -- The new `kv.range_descriptor_cache.size` [cluster setting](https://www.cockroachlabs.com/docs/v1.1/cluster-settings) can be used to control the size of the range descriptor and leaseholder caches. [#17940](https://github.com/cockroachdb/cockroach/pull/17940) -- Reduced the size of the timestamp cache by 50%. [#17983](https://github.com/cockroachdb/cockroach/pull/17983) -- Replaced several `sync.Maps` with a faster specialized `IntMap`. [#17625](https://github.com/cockroachdb/cockroach/pull/17625) -- Improved job recovery after node restarts. [#17590](https://github.com/cockroachdb/cockroach/pull/17590) -- Reduced synchronization overhead for quiesced replicas. [#17617](https://github.com/cockroachdb/cockroach/pull/17617) -- Increased the number of allowed gossip connections to reduce thrashing. [#17633](https://github.com/cockroachdb/cockroach/pull/17633) -- The `ALTER TABLE ... SCATTER` statement is more efficient. [#17644](https://github.com/cockroachdb/cockroach/pull/17644) -- Attempting to [add a column](https://www.cockroachlabs.com/docs/v1.1/add-column) with the `NOT NULL` constraint but no default value now fails earlier. [#17634](https://github.com/cockroachdb/cockroach/pull/17634) -- The `sql.defaults.distsql.tempstorage` [cluster setting](https://www.cockroachlabs.com/docs/v1.1/cluster-settings) now defaults to true. [#17665](https://github.com/cockroachdb/cockroach/pull/17665) -- Improved rebalancing on clusters with little data. [#17733](https://github.com/cockroachdb/cockroach/pull/17733) -- Improved performance of raft log truncation. [#17818](https://github.com/cockroachdb/cockroach/pull/17818) -- The "node liveness" span is now split by default to minimize interactions with the timeseries span. [#17810](https://github.com/cockroachdb/cockroach/pull/17810) -- "Slow timer" log messages are no longer repeated. [#17828](https://github.com/cockroachdb/cockroach/pull/17828) -- Set-returning functions used without a `FROM` clause no longer generate a cross-join. [#17835](https://github.com/cockroachdb/cockroach/pull/17835) -- Memory needed for the RocksDB memtable now counts towards the cache memory budget. [#17865](https://github.com/cockroachdb/cockroach/pull/17865) -- Reduced log spam for distSQL memory usage. [#17807](https://github.com/cockroachdb/cockroach/pull/17807) -- Tracing no longer records the transaction ID multiple times. [#17954](https://github.com/cockroachdb/cockroach/pull/17954) -- MVCC garbage collection is now faster when there are many records to collect. [#17986](https://github.com/cockroachdb/cockroach/pull/17986) -- Reduced occurrence of `AmbiguousResultError` due to RPC failures. [#18000](https://github.com/cockroachdb/cockroach/pull/18000) -- Outer joins with filters are now more efficient. [#18017](https://github.com/cockroachdb/cockroach/pull/18017) -- Added a timeout to heartbeat requests. [#18005](https://github.com/cockroachdb/cockroach/pull/18005) -- Sideloaded data is now correctly accounted for in raft log truncation decisions, reducing disk usage after a `RESTORE` completes. [#18090](https://github.com/cockroachdb/cockroach/pull/18090) -- Sideloaded raft log storage avoids creating too many subdirectories in one parent directory. [#17787](https://github.com/cockroachdb/cockroach/pull/17787) -- Fixed integer overflow in `generate_series()`. [#18066](https://github.com/cockroachdb/cockroach/pull/18066) -- `INSERT` statements using `RETURNING NOTHING` that target different rows in the same table can now be parallelized. [#17757](https://github.com/cockroachdb/cockroach/pull/17757) -- The timeout used for intent resolution has been increased to reduce the probability of failed resolutions that need to be retried. [#18155](https://github.com/cockroachdb/cockroach/pull/18155) - -Doc Updates
- -- Documented why and how to use `RETURNING NOTHING` to [execute statements within a transaction in parallel](https://www.cockroachlabs.com/docs/v1.1/parallel-statement-execution). [#1790](https://github.com/cockroachdb/docs/pull/1790) -- Documented SQL statements for managing queries and sessions: [`SHOW QUERIES`](https://www.cockroachlabs.com/docs/v1.1/show-queries), [`CANCEL QUERY`](https://www.cockroachlabs.com/docs/v1.1/cancel-query), [`SHOW SESSIONS`](https://www.cockroachlabs.com/docs/v1.1/show-sessions). [#1828](https://github.com/cockroachdb/docs/pull/1828) -- Added a quick reference on [Managing Long-Running Queries](https://www.cockroachlabs.com/docs/v1.1/manage-long-running-queries). [#1828](https://github.com/cockroachdb/docs/pull/1828) -- Documented the [`SHOW BACKUP`](https://www.cockroachlabs.com/docs/v1.1/show-backup) statement. [#1869](https://github.com/cockroachdb/docs/pull/1869) -- Added overview pages for the [`ALTER DATABASE`](https://www.cockroachlabs.com/docs/v1.1/alter-database) and [`ALTER INDEX`](https://www.cockroachlabs.com/docs/v1.1/alter-index) statements that point to pages for relevant subcommands, e.g., `RENAME DATABASE` and `RENAME INDEX`. [#1869](https://github.com/cockroachdb/docs/pull/1869) -- Documented the [`ARRAY`](https://www.cockroachlabs.com/docs/v1.1/array) and [`UUID`](https://www.cockroachlabs.com/docs/v1.1/uuid) data types. [#1837](https://github.com/cockroachdb/docs/pull/1837) [#1834](https://github.com/cockroachdb/docs/pull/1834) -- The RFC process has been updated. [#17568](https://github.com/cockroachdb/cockroach/pull/17568) -- Updated the [Contribute to CockroachDB](https://wiki.crdb.io/wiki/spaces/CRDB/pages/73204033/Contributing+to+CockroachDB) page to provide guidelines on finding a project, determining its complexity, and learning what to expect in your collaboration with the Cockroach Labs team. [#1881](https://github.com/cockroachdb/docs/pull/1881) - -Enterprise Edition Changes
- -- The initial split/scatter phase of large [`RESTORE`](https://www.cockroachlabs.com/docs/v1.1/restore) jobs is now much faster. [#18043](https://github.com/cockroachdb/cockroach/pull/18043) -- End times are now recorded correctly in backup descriptors. [#17908](https://github.com/cockroachdb/cockroach/pull/17908) -- Avoided slowdowns when multiple backup/restore goroutines attempt to update their progress simultaneously. [#17934](https://github.com/cockroachdb/cockroach/pull/17934) -- [`RESTORE`](https://www.cockroachlabs.com/docs/v1.1/restore) now uses larger SSTables to avoid running out of file descriptors. [#17991](https://github.com/cockroachdb/cockroach/pull/17991) [#18037](https://github.com/cockroachdb/cockroach/pull/18037) -- Fixed a deadlock in `RESTORE`. [#18101](https://github.com/cockroachdb/cockroach/pull/18101) diff --git a/src/current/_includes/releases/v1.1/v1.1-beta.20170921.md b/src/current/_includes/releases/v1.1/v1.1-beta.20170921.md deleted file mode 100644 index 97bf186a580..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1-beta.20170921.md +++ /dev/null @@ -1,37 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -Admin UI Changes
- -- New debug endpoint `/debug/logspy` can be used to access verbose logging remotely (when remote debugging is enabled). [#18221](https://github.com/cockroachdb/cockroach/pull/18221) [#18415](https://github.com/cockroachdb/cockroach/pull/18415) -- Improvements to debug pages. [#18411](https://github.com/cockroachdb/cockroach/pull/18411) [#18498](https://github.com/cockroachdb/cockroach/pull/18498) - -Bug Fixes
- -- Improve diagnostic messages for nodes incorrectly restarted without the `--join` flag. [#18203](https://github.com/cockroachdb/cockroach/pull/18203) -- Ranges can no longer become quiescent while a leadership transfer is in progress. [#18217](https://github.com/cockroachdb/cockroach/pull/18217) -- Fixed an issue with cached raft terms that could result in unavailable ranges. [#18338](https://github.com/cockroachdb/cockroach/pull/18338) -- Fixed serialization of negative integers in the distributed SQL engine. [#18323](https://github.com/cockroachdb/cockroach/pull/18323) -- Fixed bugs in reverse scans. [#18383](https://github.com/cockroachdb/cockroach/pull/18383) -- Fixed bugs in sideloaded raft storage (used by [`RESTORE`](https://www.cockroachlabs.com/docs/v1.1/restore) and [`IMPORT`](https://www.cockroachlabs.com/docs/v1.1/import)). [#18409](https://github.com/cockroachdb/cockroach/pull/18409) [#18466](https://github.com/cockroachdb/cockroach/pull/18466) [#18481](https://github.com/cockroachdb/cockroach/pull/18481) -- Improved implementation of the `COPY` protocol. [#18259](https://github.com/cockroachdb/cockroach/pull/18259) -- Failure to find a table name no longer aborts the current transaction. [#18373](https://github.com/cockroachdb/cockroach/pull/18373) -- `pg_table_is_visible` now qualifies table names correctly. [#18373](https://github.com/cockroachdb/cockroach/pull/18373) -- Fixed an interaction between RocksDB DeleteRange operations and snapshots. [#18380](https://github.com/cockroachdb/cockroach/pull/18380) [#18446](https://github.com/cockroachdb/cockroach/pull/18446) - -Performance Improvements
- -- Prevented rapid retries of non-queueable "push transaction" operations. [#18196](https://github.com/cockroachdb/cockroach/pull/18196) -- Fixed busy loop in the replication queue. [#18465](https://github.com/cockroachdb/cockroach/pull/18465) -- Rebalancing is no longer disabled temporarily after a lease transfer. [#18230](https://github.com/cockroachdb/cockroach/pull/18230) - -Doc Updates
- -- Documented how to [perform a rolling upgrade from v1.0.x to v1.1](https://www.cockroachlabs.com/docs/v1.1/upgrade-cockroach-version). [#1899](https://github.com/cockroachdb/docs/pull/1899) -- Documented how to [decommission and permanently remove nodes](https://www.cockroachlabs.com/docs/v1.1/remove-nodes) from a cluster. [#1876](https://github.com/cockroachdb/docs/pull/1876) -- Added an explanation of [what happens when a node is temporarily stopped](https://www.cockroachlabs.com/docs/v1.1/stop-a-node#how-it-works), and improved the [examples for stopping nodes](https://www.cockroachlabs.com/docs/v1.1/stop-a-node#examples). [#1899](https://github.com/cockroachdb/docs/pull/1899) -- Updated the [default `--cache` and `--max-sql-memory` size](https://www.cockroachlabs.com/docs/v1.1/start-a-node#flags-changed-in-v1-1) for nodes, and added guidance on [increasing the cache and SQL memory size](https://www.cockroachlabs.com/docs/v1.1/recommended-production-settings#cache-and-sql-memory-size-changed-in-v1-1) for production deployments. [#1906](https://github.com/cockroachdb/docs/pull/1906) -- Documented the new `--unsafe-updates` flag and new SQL shell options for the [`cockroach sql`](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client) command. [#1905](https://github.com/cockroachdb/docs/pull/1905) -- Documented the new `--echo-sql` flag for the [`cockroach sql`](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client), [`cockroach dump`](https://www.cockroachlabs.com/docs/v1.1/sql-dump), [`cockroach user`](https://www.cockroachlabs.com/docs/v1.1/create-and-manage-users), and [`cockroach zone`](https://www.cockroachlabs.com/docs/v1.1/configure-replication-zones) commands. [#1905](https://github.com/cockroachdb/docs/pull/1905) -- Added the `CASCADE` and `RESTRICT` options to the [`DROP DATABASE`](https://www.cockroachlabs.com/docs/v1.1/drop-database) documentation. [#1903](https://github.com/cockroachdb/docs/pull/1903) diff --git a/src/current/_includes/releases/v1.1/v1.1-beta.20170928.md b/src/current/_includes/releases/v1.1/v1.1-beta.20170928.md deleted file mode 100644 index cb77897127e..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1-beta.20170928.md +++ /dev/null @@ -1,67 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -Build Changes
- -- The release docker images now use Debian 8.9 (instead of 8.7) [#18755](https://github.com/cockroachdb/cockroach/pull/18755) - -SQL Language Changes
- -- The [`IMPORT`](https://www.cockroachlabs.com/docs/v1.1/import) command is now considered an experimental feature and must be enabled before use with the cluster setting `experimental.importcsv.enabled`. [#18753](https://github.com/cockroachdb/cockroach/pull/18753) -- The [cluster settings](https://www.cockroachlabs.com/docs/v1.1/cluster-settings) beginning with `sql.defaults.distsql.tempstorage` have been renamed to begin with `sql.distsql.temp_storage`. [#18487](https://github.com/cockroachdb/cockroach/pull/18487) -- The new `sql.distsql.temp_storage.workmem` [cluster setting](https://www.cockroachlabs.com/docs/v1.1/cluster-settings) sets the memory threshold at which a DistSQL processor falls back to on-disk storage. Defaults to 64MiB. [#18487](https://github.com/cockroachdb/cockroach/pull/18487) -- The [`SHOW JOBS`](https://www.cockroachlabs.com/docs/v1.1/show-jobs) statement no longer shows numeric descriptor IDs. [#18797](https://github.com/cockroachdb/cockroach/pull/18797) - -Command-Line Interface Changes
- -- The new `--max-disk-temp-storage` flag for the [`cockroach start`](https://www.cockroachlabs.com/docs/v1.1/start-a-node) command controls how much disk space can be used for temporary storage. [#18761](https://github.com/cockroachdb/cockroach/pull/18761) -- The `cockroach load csv` command now increases its soft limit on the number of open file descriptors when possible. [#18678](https://github.com/cockroachdb/cockroach/pull/18678) -- The `cockroach init` command now provides a better error message when run on an already-initialized cluster. [#18548](https://github.com/cockroachdb/cockroach/pull/18548) - -Admin UI Changes
- -- Reduced false positives when marking nodes as "suspect". [#18563](https://github.com/cockroachdb/cockroach/pull/18563) -- The **Jobs** page can now be limited to import jobs. [#18615](https://github.com/cockroachdb/cockroach/pull/18615) -- The **Keys Written per Second per Store** graph on the **Replication** dashboard is now accurate. [#18800](https://github.com/cockroachdb/cockroach/pull/18800) -- Fixed the display of the number of indexes per table. [#18769](https://github.com/cockroachdb/cockroach/pull/18769) - -Bug Fixes
- -- Fixed a bug in which queries using [`DISTINCT`](https://www.cockroachlabs.com/docs/v1.1/select#select-distinct-rows) or [`GROUP BY`](https://www.cockroachlabs.com/docs/v1.1/select#create-aggregate-groups) could return incorrect results. [#18727](https://github.com/cockroachdb/cockroach/pull/18727) -- After some results have been streamed to the client, queries are no longer auto-retried. [#18515](https://github.com/cockroachdb/cockroach/pull/18515) [#18569](https://github.com/cockroachdb/cockroach/pull/18569) -- Tables with no columns now work correctly. [#18532](https://github.com/cockroachdb/cockroach/pull/18532) -- The [`cockroach dump`](https://www.cockroachlabs.com/docs/v1.1/sql-dump) command now supports values of type `UUID`. [#18543](https://github.com/cockroachdb/cockroach/pull/18543) -- The distributed SQL engine now avoids scheduling work on nodes running version 1.0.x in a mixed-version cluster. [#18546](https://github.com/cockroachdb/cockroach/pull/18546) -- The distributed SQL engine no longer attempts to schedule work on [decommissioned nodes](https://www.cockroachlabs.com/docs/v1.1/remove-nodes). [#18698](https://github.com/cockroachdb/cockroach/pull/18698) -- The [`TRUNCATE`](https://www.cockroachlabs.com/docs/v1.1/truncate) statement now works correctly on tables in the middle of a schema change (the schema change finishes immediately on the now-empty table). [#18549](https://github.com/cockroachdb/cockroach/pull/18549) -- Fixed a panic in `tableState.findForTimestamp` [#18557](https://github.com/cockroachdb/cockroach/pull/18557) -- Fixed a bug in which importing a CSV would fail to report unique constraint violations. [#18563](https://github.com/cockroachdb/cockroach/pull/18563) -- Fixed a bug when importing a CSV into a table with multiple column families. [#18563](https://github.com/cockroachdb/cockroach/pull/18563) -- [`SHOW TRACE`](https://www.cockroachlabs.com/docs/v1.1/show-trace) now works correctly when ipv6 is used. [#18567](https://github.com/cockroachdb/cockroach/pull/18567) -- Foreign key checks are now included in [`SHOW KV TRACE`](https://www.cockroachlabs.com/docs/v1.1/show-trace). [#18568](https://github.com/cockroachdb/cockroach/pull/18568) -- Fixed the display of version numbers. [#18562](https://github.com/cockroachdb/cockroach/pull/18562) -- Improved tracing of range lookups [#18613](https://github.com/cockroachdb/cockroach/pull/18613) -- Fixed an overflow check in key decoding. [#18639](https://github.com/cockroachdb/cockroach/pull/18639) -- Fixed a trace use-after-finish panic. [#18645](https://github.com/cockroachdb/cockroach/pull/18645) -- Fixed a panic in `disk_row_container`. [#18685](https://github.com/cockroachdb/cockroach/pull/18685) -- Improved some error reporting. [#18708](https://github.com/cockroachdb/cockroach/pull/18708) -- Fixed [zone config](https://www.cockroachlabs.com/docs/v1.1/configure-replication-zones) problems after dropping or truncating a table. [#18781](https://github.com/cockroachdb/cockroach/pull/18781) -- [`SHOW CLUSTER QUERIES`](https://www.cockroachlabs.com/docs/v1.1/show-queries) and [`SHOW CLUSTER SESSIONS`](https://www.cockroachlabs.com/docs/v1.1/show-sessions) no longer panic when a node is down. [#18802](https://github.com/cockroachdb/cockroach/pull/18802) -- Fixed a bug with queries using `COUNT(*)` and tables containing multiple column families. [#18805](https://github.com/cockroachdb/cockroach/pull/18805) - -Performance Improvements
- -- Improved performance of [foreign key](https://www.cockroachlabs.com/docs/v1.1/foreign-key) checks. [#18597](https://github.com/cockroachdb/cockroach/pull/18597) -- Table leases are now refreshed asynchronously when near expiration. [#18824](https://github.com/cockroachdb/cockroach/pull/18824) -- Improved performance of `COUNT(*)` queries. [#18524](https://github.com/cockroachdb/cockroach/pull/18524) -- Reduced some noisy log messages. [#18589](https://github.com/cockroachdb/cockroach/pull/18589) -- Distributed CSV import is now aware of the target range size. [#18634](https://github.com/cockroachdb/cockroach/pull/18634) -- The GC queue now gives up earlier after a timeout. [#18672](https://github.com/cockroachdb/cockroach/pull/18672) -- The distributed SQL engine now supports array values. [#18792](https://github.com/cockroachdb/cockroach/pull/18792) -- Improved load-based lease rebalancing for distributed SQL queries. [#18794](https://github.com/cockroachdb/cockroach/pull/18794) - -Doc Updates
- -- In the [`cockroach dump`](https://www.cockroachlabs.com/docs/v1.1/sql-dump) documentation, clarified that table and view schemas are dumped in the order in which they can successfully be recreated. Also added this as a [known limitation in CockroachDB v1.0](https://www.cockroachlabs.com/docs/v1.0/known-limitations#order-of-dumped-schemas-and-incorrect-schemas-of-dumped-views). [#1923](https://github.com/cockroachdb/docs/pull/1923) -- Added a message when searches of the documentation return no results. [#1927](https://github.com/cockroachdb/docs/pull/1927) diff --git a/src/current/_includes/releases/v1.1/v1.1.0-rc.1.md b/src/current/_includes/releases/v1.1/v1.1.0-rc.1.md deleted file mode 100644 index 20d89ac7826..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1.0-rc.1.md +++ /dev/null @@ -1,34 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -Build Changes
- -- Docker images now contain root CA certificates, permitting the use of `BACKUP` and `RESTORE` on cloud storage. [#18959](https://github.com/cockroachdb/cockroach/pull/18959) -- Docker images are now built without caching to ensure they contain the latest packages at the time of release. [#18999](https://github.com/cockroachdb/cockroach/pull/18999) - -Command-Line Interface Changes
- -- Timestamps in logs now use UTC regardless of the system time zone. [#18764](https://github.com/cockroachdb/cockroach/pull/18764) -- Added an explanatory message when `--background` is used and the node is waiting to join an existing cluster or for `cockroach init` to be run. [#18840](https://github.com/cockroachdb/cockroach/pull/18840) - -Bug Fixes
- -- [`SERIALIZABLE`](https://www.cockroachlabs.com/docs/v1.1/transactions#serializable-isolation) transactions should no longer return "transaction deadline exceeded". [#18852](https://github.com/cockroachdb/cockroach/pull/18852) -- Transaction deadlines are now updated properly when a transaction restarts. [#18943](https://github.com/cockroachdb/cockroach/pull/18943) -- Fixed a panic when an error was generated in [`COMMIT`](https://www.cockroachlabs.com/docs/v1.1/commit-transaction) or [`ROLLBACK`](https://www.cockroachlabs.com/docs/v1.1/rollback-transaction). [#18937](https://github.com/cockroachdb/cockroach/pull/18937) -- Fixed a panic in queries with `JOIN` using the distributed SQL engine. [#18975](https://github.com/cockroachdb/cockroach/pull/18975) -- Reverted a change in [beta-20170928](#v1-1-beta-20170928) to asynchronously refresh table leases when near expiration. [#18862](https://github.com/cockroachdb/cockroach/pull/18862) -- Casting `TIMESTAMP WITH TIME ZONE` to `TIMESTAMP` respects the [session time zone](https://www.cockroachlabs.com/docs/v1.1/set-vars#set-time-zone). [#18764](https://github.com/cockroachdb/cockroach/pull/18764) -- Range debug pages now work when a replica is awaiting garbage collection. [#18941](https://github.com/cockroachdb/cockroach/pull/18941) -- Temporary directory cleanup now works correctly on `overlayfs`. [#19000](https://github.com/cockroachdb/cockroach/pull/19000) - -Doc Updates
- -- Documented the [`cockroach init`](https://www.cockroachlabs.com/docs/v1.1/initialize-a-cluster) command and updated the [manual](https://www.cockroachlabs.com/docs/v1.1/manual-deployment) and [cloud](https://www.cockroachlabs.com/docs/v1.1/manual-deployment) deployment tutorials to use the new cluster initialization workflow. [#1942](https://github.com/cockroachdb/docs/pull/1942) -- Updated various diagrams in our [SQL statement documentation](https://www.cockroachlabs.com/docs/v1.1/sql-statements). [#1946](https://github.com/cockroachdb/docs/pull/1946) -- Documented the [`DROP USER`](https://www.cockroachlabs.com/docs/v1.1/drop-user) statement, and updated related docs to clarify that removing a user does not automatically remove the user's privileges; that must be done manually. [#1954](https://github.com/cockroachdb/docs/pull/1954) -- Updated the [Rust transaction code sample](https://www.cockroachlabs.com/docs/v1.1/build-a-rust-app-with-cockroachdb#transaction-with-retry-logic) to work against PostgreSQL v0.15.1. [#1941](https://github.com/cockroachdb/docs/pull/1941) -- Updated the [ActiveRecord tutorial](https://www.cockroachlabs.com/docs/v1.1/build-a-ruby-app-with-cockroachdb-activerecord#step-1-install-the-activerecord-orm) to clarify the dependency between the ActiveRecord version and the CockroachDB Ruby adapter. [#1949](https://github.com/cockroachdb/docs/pull/1949) -- Clarified that [window functions](https://www.cockroachlabs.com/docs/v1.1/window-functions) are supported by CockroachDB (more docs coming soon). [#1948](https://github.com/cockroachdb/docs/pull/1948) -- Updated the [`SHOW CREATE TABLE` example](https://www.cockroachlabs.com/docs/v1.1/show-create-table#example) to show improved output for foreign key dependencies. [#1953](https://github.com/cockroachdb/docs/pull/1953) diff --git a/src/current/_includes/releases/v1.1/v1.1.0.md b/src/current/_includes/releases/v1.1/v1.1.0.md deleted file mode 100644 index 3b99fa75b4d..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1.0.md +++ /dev/null @@ -1,96 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -With the release of CockroachDB v1.1.0, we’ve included support for faster migrations from other databases for developers, simplified cluster management for operators, and improved performance in real-world environments. - -- Read more about these changes in the [v1.1 blog post](https://www.cockroachlabs.com/blog/cockroachdb-1dot1/). -- Check out a [summary of backwards-incompatible changes and new features](#v1-1-0-summary). -- Then [upgrade to CockroachDB v1.1.0](https://www.cockroachlabs.com/docs/v1.1/upgrade-cockroach-version). The process of upgrading from v1.0.x to v1.1.0 is different than upgrading within the v1.0.x series, so please follow the upgrade instructions carefully. - -Summary
- -This section summarizes the most significant user-facing changes in v1.1.0. For a complete list of changes, including bug fixes and performance improvements, see the [release notes]({% link releases/index.md %}#testing-releases) for previous testing releases. - -- [Backwards-Incompatible Changes](#v1-1-0-backwards-incompatible-changes) -- [SQL Statements](#v1-1-0-sql-statements) -- [SQL Types](#v1-1-0-sql-types) -- [Cockroach Commands](#v1-1-0-cockroach-commands) -- [Admin UI](#v1-1-0-admin-ui) -- [Documentation](#v1-1-0-documentation) -- [Known Limitations](#v1-1-0-known-limitations) - - - -Backwards-Incompatible Changes
- -Change | Description --------|------------ -[`DROP DATABASE`](https://www.cockroachlabs.com/docs/v1.1/drop-database) | This statement no longer drops non-empty databases unless the `CASCADE` modifier is added. -[`cockroach start`](https://www.cockroachlabs.com/docs/v1.1/start-a-node) | The `--max-sql-memory` and `--cache` flags now default to 128MiB instead of 25% of physical memory. These new defaults are reasonable for local development clusters. However, for production deployments, they should be increased to 25% or higher. See [Recommended Production Settings](https://www.cockroachlabs.com/docs/v1.1/recommended-production-settings#cache-and-sql-memory-size-changed-in-v1-1) for more details.Also, if the server's own hostname cannot be resolved, CockroachDB reports an error at startup instead of starting a node that will be unable to participate in a cluster. Local test clusters may need to pass `--host=localhost` to avoid this error. -[Various names](https://www.cockroachlabs.com/docs/v1.1/keywords-and-identifiers#rules-for-identifiers) | Database, table, view, and column names in double quotes are now case-sensitive (as in PostgreSQL). -[`DROP COLUMN`](https://www.cockroachlabs.com/docs/v1.1/drop-column) | It is no longer possible to drop columns in tables depended on by [views](https://www.cockroachlabs.com/docs/v1.1/views). This is an overly-broad change to avoid schema changes that might break views; it will be narrowed in the future. -`EXPLAIN (DEBUG)`
`EXPLAIN(TRACE)` | These [`EXPLAIN`](https://www.cockroachlabs.com/docs/v1.1/explain) options have been removed. They have been replaced by the new [`SHOW TRACE`](https://www.cockroachlabs.com/docs/v1.1/show-trace) statement. - -
SQL Statements
- -Statement | Description -----------|------------ -[`IMPORT`](https://www.cockroachlabs.com/docs/v1.1/import) | Use this new statement to import an entire table's data into a running cluster by loading CSV files. -[`SHOW QUERIES`](https://www.cockroachlabs.com/docs/v1.1/show-queries)[`CANCEL QUERY`](https://www.cockroachlabs.com/docs/v1.1/cancel-query) | Use these new statements to monitor the progress of active queries, and, if necessary, cancel long-running queries causing unwanted resource consumption. -[`SHOW SESSIONS`](https://www.cockroachlabs.com/docs/v1.1/show-sessions) | Use this new statement to monitor the overall state of client connections and identify those that may need investigation or adjustment. -[`SHOW JOBS`](https://www.cockroachlabs.com/docs/v1.1/show-jobs) | Use this new statement to monitor the progress of schema changes and enterprise backups and restores. -[`CANCEL JOB`](https://www.cockroachlabs.com/docs/v1.1/cancel-job)
[`PAUSE JOB`](https://www.cockroachlabs.com/docs/v1.1/pause-job)
[`RESUME JOB`](https://www.cockroachlabs.com/docs/v1.1/resume-job) | Use these new statements to cancel, pause, or resume enterprise backups and restores. -[`SHOW BACKUP`](https://www.cockroachlabs.com/docs/v1.1/show-backup) | Use this new statement to list the contents of an enterprise backup. -[`SHOW TRACE`](https://www.cockroachlabs.com/docs/v1.1/show-trace) | Use this new statement to execute a target statement and then return a trace of its actions through all of CockroachDB's software layers. -[`DROP USER`](https://www.cockroachlabs.com/docs/v1.1/drop-user) | Use this new statement to remove one or more SQL users. This features is equivalent to the existing [`cockroach user rm`](https://www.cockroachlabs.com/docs/v1.1/create-and-manage-users) command. -[`RESET`](https://www.cockroachlabs.com/docs/v1.1/reset-vars)
| Use this new statement to reset a session variable to its default value. You can also use the new [`SET .. TO DEFAULT`](https://www.cockroachlabs.com/docs/v1.1/set-vars#reset-a-variable-to-its-default-value) option. -[`RESET CLUSTER SETTING`](https://www.cockroachlabs.com/docs/v1.1/reset-cluster-setting) | Use this new statement to reset a cluster setting to its default value. You can also use the new [`SET CLUSTER SETTING .. TO DEFAULT`](https://www.cockroachlabs.com/docs/v1.1/set-cluster-setting#reset-a-setting-to-its-default-value) option. -[`DROP DATABASE`](https://www.cockroachlabs.com/docs/v1.1/drop-database) | Use the new `CASCADE` option to drop all tables and views in a database as well as all objects that depend on those tables, such as [constraints](https://www.cockroachlabs.com/docs/v1.1/constraints) and [views](https://www.cockroachlabs.com/docs/v1.1/views). This option does not list objects it drops, so should be used cautiously. -[`INSERT`](https://www.cockroachlabs.com/docs/v1.1/insert#update-values-on-conflict) | Use a `WHERE` clause with `ON CONFLICT` to conditionally apply updates that conflict with a Unique constraint on one or more columns. - -
SQL Types
- -Type | Description ------|------------ -[`ARRAY`](https://www.cockroachlabs.com/docs/v1.1/array) | Use this new data type to store 1-dimensional, 1-indexed, homogeneous arrays of any non-array data type. -[`UUID`](https://www.cockroachlabs.com/docs/v1.1/uuid) | Use this new data type to store 128-bit values that are globally unique. This type is recommended for [auto-generating unique row IDs](https://www.cockroachlabs.com/docs/v1.1/uuid#create-a-table-with-auto-generated-unique-row-ids). - -Cockroach Commands
- -Command | Description ---------|------------ -[`init`](https://www.cockroachlabs.com/docs/v1.1/initialize-a-cluster) | Use this new command to perform a one-time initialization of a new multi-node cluster. For a full walk-through of the cluster startup and initialization process, see [Manual Deployment](https://www.cockroachlabs.com/docs/v1.1/manual-deployment) or one of the [Cloud Deployment](https://www.cockroachlabs.com/docs/v1.1/manual-deployment) tutorials. -[`node decommission`](https://www.cockroachlabs.com/docs/v1.1/view-node-details)[`node recommission`](https://www.cockroachlabs.com/docs/v1.1/view-node-details) | Use these new subcommands of `cockroach node` to decommission nodes for permanent removal or recommission nodes that were accidentally decommissioned. See [Remove Nodes](https://www.cockroachlabs.com/docs/v1.1/remove-nodes) for more details. -[`start`](https://www.cockroachlabs.com/docs/v1.1/start-a-node) | When starting a node, the new `--max-disk-temp-storage` flag lets you set the maximum on-disk storage capacity available to store temporary data for SQL queries that exceed the memory budget. This ensures that JOINs, sorts, and other memory-intensive SQL operations are able to spill intermediate results to disk. -[`sql`](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client) | When starting the built-in SQL client, the new `--echo-sql` flag reveals the SQL statements sent implicitly by the command-line utility, and the new `--unsafe-updates` flag allows potentially unsafe statements, such as `DELETE` without a `WHERE` clause.
Within the interactive SQL shell, you can now get [interactive help about statements and functions](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client#sql-shell-help-new-in-v1-1) and you can set [new SQL shell options](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client#sql-shell-options-changed-in-v1-1) to control how table rows get printed, to reveal the statements sent implicitly by the SQL shell, to reveal the time a query takes to complete, and to return the current status of a transaction.
Also, when the built-in SQL client connects or reconnects to a node, the [welcome text](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client#sql-shell-welcome-changed-in-v1-1) it prints now includes version and cluster ID details. -[`dump`](https://www.cockroachlabs.com/docs/v1.1/sql-dump) | Table and view schemas are now dumped in the order in which they can successfully be recreated.
Also, the new `--echo-sql` flag reveals the SQL statements sent implicitly by the command-line utility. -[`zone`](https://www.cockroachlabs.com/docs/v1.1/configure-replication-zones) | The new `--echo-sql` flag reveals the SQL statements sent implicitly by the command-line utility. - -
Admin UI
- -Area | Description ------|------------ -[Jobs Page](https://www.cockroachlabs.com/docs/v1.1/admin-ui-jobs-page) | This new page in the Admin UI shows the user, description, creation time, and status of each backup and restore job, as well as schema changes performed across all nodes in the cluster. -[Nodes List](https://www.cockroachlabs.com/docs/v1.1/admin-ui-access-and-navigate#decommissioned-nodes) | Nodes that have been decommissioned for permanent removal are now listed in a separate table. - -Documentation
- -Topic | Description -------|------------ -[CockroachDB Architecture](https://www.cockroachlabs.com/docs/v1.1/architecture/overview) | This new section of the documentation provides an introduction to CockroachDB internals, with detailed explanations of each layer of the software. -[Admin UI](https://www.cockroachlabs.com/docs/v1.1/admin-ui-overview) | This new section of the documentation explains how to understand and use the Admin UI to monitor and optimize cluster performance. -[Parallel Statement Execution](https://www.cockroachlabs.com/docs/v1.1/parallel-statement-execution) | CockroachDB supports parallel execution of independent `INSERT`, `UPDATE`, `UPSERT`, and `DELETE` statements within a single transaction. This new topic explains why, how, and when to use this feature. -[Cross-Cloud Migration](https://www.cockroachlabs.com/docs/v1.1/demo-automatic-cloud-migration) | This new topic walks you through a local simulation of migrating data from one cloud to another without any service interruption. An accompanying [blog post](https://www.cockroachlabs.com/blog/cross-cloud-migration/) features a live demonstration of the process. -[Recommended Production Settings](https://www.cockroachlabs.com/docs/v1.1/recommended-production-settings) | This topic now provides improved hardware recommendations for a CockroachDB cluster and expanded details on how CockroachDB handles unsynchronized clocks. -[Rotate Security Certificates](https://www.cockroachlabs.com/docs/v1.1/rotate-certificates) | This new topic shows you how to rotate security certificates without restarting nodes. -[Stop a Node](https://www.cockroachlabs.com/docs/v1.1/stop-a-node#how-it-works) | This topic now explains what happens when a node is temporarily stopped. -[Contribute to CockroachDB](https://wiki.crdb.io/wiki/spaces/CRDB/pages/73204033/Contributing+to+CockroachDB) | This topic now gives external contributors guidelines on finding a project, determining its complexity, and learning what to expect in collaborations with the Cockroach Labs team. - -Known Limitations
- -For information about limitations we've identified in CockroachDB v1.1, with suggested workarounds where applicable, see [Known Limitations](https://www.cockroachlabs.com/docs/v1.1/known-limitations). diff --git a/src/current/_includes/releases/v1.1/v1.1.1.md b/src/current/_includes/releases/v1.1/v1.1.1.md deleted file mode 100644 index 02d2a4aee29..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1.1.md +++ /dev/null @@ -1,18 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -SQL Language Changes
- -- [`ARRAY`](https://www.cockroachlabs.com/docs/v1.1/array) values are now more compatible with certain client drivers. [#19273](https://github.com/cockroachdb/cockroach/pull/19273) [#19285](https://github.com/cockroachdb/cockroach/pull/19285) - -Bug Fixes
- -- `SET CLUSTER SETTING version = '1.1'` now works correctly. You issue this command when [finalizing a cluster upgrade from 1.0.x to 1.1.1](https://www.cockroachlabs.com/docs/v1.1/upgrade-cockroach-version). [#19225](https://github.com/cockroachdb/cockroach/pull/19225) -- Created, dropped, or truncated tables no longer result in non-restorable backups. [#19067](https://github.com/cockroachdb/cockroach/pull/19067) -- Some issues that could cause non-restorable backups are now detected during the backup process. [#19286](https://github.com/cockroachdb/cockroach/pull/19286) -- Fixed a deadlock in the crash reporting code, making more information available about certain fatal errors. [#19287](https://github.com/cockroachdb/cockroach/pull/19287) -- Very large arguments to the SQL `repeat()` function now return an error instead of panicking. [#19066](https://github.com/cockroachdb/cockroach/pull/19066) -- It is now possible to drop a [foreign key constraint](https://www.cockroachlabs.com/docs/v1.1/foreign-key) on a column that is part of the primary key. [#19092](https://github.com/cockroachdb/cockroach/pull/19092) -- Attempting to use [`SHOW TRACE FOR`](https://www.cockroachlabs.com/docs/v1.1/show-trace) while session tracing is enabled no longer turns off session tracing. [#19099](https://github.com/cockroachdb/cockroach/pull/19099) -- [`SHOW TRACE FOR`](https://www.cockroachlabs.com/docs/v1.1/show-trace) no longer includes detailed KV-level information (these messages are included in the separate `SHOW KV TRACE FOR` command). [#19143](https://github.com/cockroachdb/cockroach/pull/19143) diff --git a/src/current/_includes/releases/v1.1/v1.1.2.md b/src/current/_includes/releases/v1.1/v1.1.2.md deleted file mode 100644 index de4130c2c0b..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1.2.md +++ /dev/null @@ -1,46 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -SQL Language Changes
- -- The new `gen_random_uuid()` [function](https://www.cockroachlabs.com/docs/v1.1/functions-and-operators) generates and returns a random [`UUID`](https://www.cockroachlabs.com/docs/v1.1/uuid) value. [#19585](https://github.com/cockroachdb/cockroach/pull/19585) - -Bug Fixes
- -- Reverted the default behavior of [`DROP DATABASE`](https://www.cockroachlabs.com/docs/v1.1/drop-database) to `CASCADE` for compatibility with PostgreSQL, some schema migration tools, and CockroachDB v1.0. [#19209](https://github.com/cockroachdb/cockroach/pull/19209) - -- Fixed a bug preventing crash reports from being submitted with [anonymous diagnostics details](https://www.cockroachlabs.com/docs/v1.1/diagnostics-reporting). [#19563](https://github.com/cockroachdb/cockroach/pull/19563) - -- Important errors such as "writes: no space left on device" are now included in crash reports. [#19314](https://github.com/cockroachdb/cockroach/pull/19314) - -- The [`cockroach dump`](https://www.cockroachlabs.com/docs/v1.1/sql-dump) command now properly supports [`ARRAY`](https://www.cockroachlabs.com/docs/v1.1/array) values and [primary keys](https://www.cockroachlabs.com/docs/v1.1/primary-key) named other than "primary". [#19526](https://github.com/cockroachdb/cockroach/pull/19526) [#19400](https://github.com/cockroachdb/cockroach/pull/19400) - -- It is now possible to use AWS S3 buckets in any region for [`IMPORT`](https://www.cockroachlabs.com/docs/v1.1/import) and enterprise [`BACKUP`](https://www.cockroachlabs.com/docs/v1.1/backup) and [`RESTORE`](https://www.cockroachlabs.com/docs/v1.1/restore). [#19473](https://github.com/cockroachdb/cockroach/pull/19473) - -- Reduced unnecessary log messages when a cluster becomes temporarily unbalanced, for example, when a new node joins. [#19494](https://github.com/cockroachdb/cockroach/pull/19494) - -- Fixed a bug causing redundant log messages when running [`SHOW TRACE FOR`](https://www.cockroachlabs.com/docs/v1.1/show-trace). [#19469](https://github.com/cockroachdb/cockroach/pull/19469) - -- [`ARRAY`](https://www.cockroachlabs.com/docs/v1.1/array) values containing strings with multiple consecutive escapes are now parsed properly. [#19452](https://github.com/cockroachdb/cockroach/pull/19452) - -- Fixed a bug causing certain queries with [`ORDER BY`](https://www.cockroachlabs.com/docs/v1.1/select#sorting-retrieved-values) to return incorrectly ordered results when the ordering columns contain NULL values. [#19419](https://github.com/cockroachdb/cockroach/pull/19419) - -- Fixed `NATURAL JOIN` operations (where the join clause is implicit based on the common columns in the tables being joined) when one side of the join is a subquery. [#19544](https://github.com/cockroachdb/cockroach/pull/19544) - -- Improved the handling of errors during [range splits](https://www.cockroachlabs.com/docs/v1.1/architecture/distribution-layer#range-splits). [#19448](https://github.com/cockroachdb/cockroach/pull/19448) - -- Fixed a bug causing correctness problems when nodes run out of disk. [#19447](https://github.com/cockroachdb/cockroach/pull/19447) - -- Fixed a bug causing the [decommissioning](https://www.cockroachlabs.com/docs/v1.1/remove-nodes) process to hang when the target node is already decommissioned. [#19279](https://github.com/cockroachdb/cockroach/pull/19279) - -- Fixed a bug preventing aborted [transactions](https://www.cockroachlabs.com/docs/v1.1/transactions) from seeing their own writes. [#19093](https://github.com/cockroachdb/cockroach/pull/19093) - -- Improved performance for some transaction conflicts. [#19093](https://github.com/cockroachdb/cockroach/pull/19093) - -Doc Updates
- -- Added a [known limitation](https://www.cockroachlabs.com/docs/v1.1/known-limitations#downgrading-to-v1-1-0-from-a-later-v1-1-x-patch-release) about downgrading to v1.1.0 from a later v1.1.x patch release. [#2095](https://github.com/cockroachdb/docs/pull/2095) -- Corrected the aliases and allowed widths of various [`INT`](https://www.cockroachlabs.com/docs/v1.1/int) types. [#2116](https://github.com/cockroachdb/docs/pull/2116) -- Corrected the description of the `--host` flag in our insecure [cloud deployment tutorials](https://www.cockroachlabs.com/docs/v1.1/manual-deployment). [#2117](https://github.com/cockroachdb/docs/pull/2117) -- Minor improvements to the [CockroachDB Architecture Overview](https://www.cockroachlabs.com/docs/v1.1/architecture/overview) page. [#2103](https://github.com/cockroachdb/docs/pull/2103) [#2104](https://github.com/cockroachdb/docs/pull/2104) [#2105](https://github.com/cockroachdb/docs/pull/2105) diff --git a/src/current/_includes/releases/v1.1/v1.1.3.md b/src/current/_includes/releases/v1.1/v1.1.3.md deleted file mode 100644 index 6333cbb1daf..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1.3.md +++ /dev/null @@ -1,56 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -SQL Language changes
- -- [`SHOW TRACE FOR SELECT`](https://www.cockroachlabs.com/docs/v1.1/show-trace) now supports [`AS OF SYSTEM TIME`](https://www.cockroachlabs.com/blog/time-travel-queries-select-witty_subtitle-the_future/). [#20187](https://github.com/cockroachdb/cockroach/pull/20187) - -Bug Fixes
- -- [Decommissioned nodes](https://www.cockroachlabs.com/docs/v1.1/remove-nodes) are now excluded from the staggered version warning. [#19626](https://github.com/cockroachdb/cockroach/pull/19626) - -- When an enterprise [`RESTORE`](https://www.cockroachlabs.com/docs/v1.1/restore) fails or is canceled, partially restored data is now properly cleaned up. [#19653](https://github.com/cockroachdb/cockroach/pull/19653) - -- Correctly resume [`RESTORE`](https://www.cockroachlabs.com/docs/v1.1/restore) jobs that skip [foreign keys](https://www.cockroachlabs.com/docs/v1.1/foreign-key). [#20168](https://github.com/cockroachdb/cockroach/pull/20168) - -- Improved memory usage for certain queries that use [`LIMIT`](https://www.cockroachlabs.com/docs/v1.1/select#control-quantity-of-returned-rows) at multiple levels. [#19688](https://github.com/cockroachdb/cockroach/pull/19688) - -- Fixed a rare panic in [`SET`](https://www.cockroachlabs.com/docs/v1.1/set-vars). [#19750](https://github.com/cockroachdb/cockroach/pull/19750) - -- Fixed a panic in distributed SQL. [#19828](https://github.com/cockroachdb/cockroach/pull/19828) - -- Fixed a panic in some [`DELETE`](https://www.cockroachlabs.com/docs/v1.1/delete) statements. [#19830](https://github.com/cockroachdb/cockroach/pull/19830) - -- Fixed grouping of [`ANY/SOME/ALL`](https://www.cockroachlabs.com/docs/v1.1/sql-grammar#sub_type). [#19831](https://github.com/cockroachdb/cockroach/pull/19831) - -- Fixed a panic in [`SHOW KV TRACE`](https://www.cockroachlabs.com/docs/v1.1/show-trace) with `COUNT(*)`. [#19868](https://github.com/cockroachdb/cockroach/pull/19868) - -- Fixed a panic involving the use of the `IN` operator and improperly typed subqueries. [#19878](https://github.com/cockroachdb/cockroach/pull/19878) - -- Fixed a bug leading to incorrect results for some queries with [`IN`](https://www.cockroachlabs.com/docs/v1.1/functions-and-operators#operators) constraints. [#20040](https://github.com/cockroachdb/cockroach/pull/20040) - -- Fixed the encoding of indexes that use [`STORING`](https://www.cockroachlabs.com/docs/v1.1/create-index#store-columns) columns. [#20074](https://github.com/cockroachdb/cockroach/pull/20074) - -- Fixed a panic when updating [`COLLATE`](https://www.cockroachlabs.com/docs/v1.1/collate) and [`DECIMAL`](https://www.cockroachlabs.com/docs/v1.1/decimal) columns. [#20074](https://github.com/cockroachdb/cockroach/pull/20074) - -- Avoid overloading the system during cleanup of large [transactions](https://www.cockroachlabs.com/docs/v1.1/transactions). [#20083](https://github.com/cockroachdb/cockroach/pull/20083) - -- Fixed [`PARTITION BY`](https://www.cockroachlabs.com/docs/v1.1/sql-grammar#opt_partition_clause) multiple columns with [`WINDOW`](https://www.cockroachlabs.com/docs/v1.1/window-functions) functions. [#20156](https://github.com/cockroachdb/cockroach/pull/20156) - -- Fixed a possible crash due to statements finishing execution after the client connection has been closed. [#20183](https://github.com/cockroachdb/cockroach/pull/20183) - -- Write [prometheus vars](https://www.cockroachlabs.com/docs/v1.1/monitor-cockroachdb-with-prometheus) outside the metrics lock. [#20209](https://github.com/cockroachdb/cockroach/pull/20209) - -Doc Updates
- -- Improved Kubernetes guidance: - - Added a tutorial on [orchestrating a secure CockroachDB cluster with Kubernetes](https://www.cockroachlabs.com/docs/v1.1/orchestrate-cockroachdb-with-kubernetes), improved the tutorial for [insecure orchestrations](https://www.cockroachlabs.com/docs/v1.1/orchestrate-cockroachdb-with-kubernetes-insecure), and added a [local cluster tutorial using `minikube`](https://www.cockroachlabs.com/docs/v1.1/orchestrate-a-local-cluster-with-kubernetes-insecure). [#2147](https://github.com/cockroachdb/docs/pull/2147) - - Updated the StatefulSet configurations to support rolling upgrades, and added [initial documentation](https://github.com/cockroachdb/cockroach/tree/master/cloud/kubernetes#doing-a-rolling-upgrade-to-a-different-cockroachdb-version). [#19995](https://github.com/cockroachdb/cockroach/pull/19995) -- Added a tutorial on CockroachDB's [follow-the-workload](https://www.cockroachlabs.com/docs/v1.1/demo-follow-the-workload) capability. [#2194](https://github.com/cockroachdb/docs/pull/2194) -- Documented how to [increase the system-wide file descriptors limit on Linux](https://www.cockroachlabs.com/docs/v1.1/recommended-production-settings#file-descriptors-limit). [#2139](https://github.com/cockroachdb/docs/pull/2139) -- Clarified that multiple transaction options in a single [`SET TRANSACTION`](https://www.cockroachlabs.com/docs/v1.1/set-transaction#set-isolation-priority) statement can be space-separated as well as comma-separated. [#2139](https://github.com/cockroachdb/docs/pull/2139) -- Added `e'\x` to the list of supported [hexadecimal-encoded byte array literals](https://www.cockroachlabs.com/docs/v1.1/sql-constants#hexadecimal-encoded-byte-array-literals) formats. [#2134](https://github.com/cockroachdb/docs/pull/2134) -- Clarified the FAQ on [auto-generating unique row IDs](https://www.cockroachlabs.com/docs/v1.1/sql-faqs#how-do-i-auto-generate-unique-row-ids-in-cockroachdb). [#2128](https://github.com/cockroachdb/docs/pull/2128) -- Corrected the aliases and allowed widths of various [`INT`](https://www.cockroachlabs.com/docs/v1.1/int) types. [#2116](https://github.com/cockroachdb/docs/pull/2116) -- Corrected the description of the `--host` flag in our insecure [cloud deployment tutorials](https://www.cockroachlabs.com/docs/v1.1/manual-deployment). [#2117](https://github.com/cockroachdb/docs/pull/2117) diff --git a/src/current/_includes/releases/v1.1/v1.1.4.md b/src/current/_includes/releases/v1.1/v1.1.4.md deleted file mode 100644 index 437bb03ac0c..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1.4.md +++ /dev/null @@ -1,51 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -SQL Language Changes
- -- For compatibility with PostgreSQL, the `transaction isolation level`, `transaction priority`, and `transaction status` [session variables](https://www.cockroachlabs.com/docs/v1.1/set-vars) have been renamed `transaction_isolation`, `transaction_priority`, and `transaction_status`. [#20301](https://github.com/cockroachdb/cockroach/pull/20301) -- The [`IMPORT`](https://www.cockroachlabs.com/docs/v1.1/import) statement now supports `201` and `204` return codes from HTTP storage. [#20516](https://github.com/cockroachdb/cockroach/pull/20516) - -Command-Line Changes
- -- Client [`cockroach` commands](https://www.cockroachlabs.com/docs/v1.1/cockroach-commands) that use SQL (`cockroach sql`, `cockroach node ls`, etc.) now print a warning if the server is running an older version of CockroachDB than the client. Also, this and other warning messages are now clearly indicated with the "warning:" prefix. [#20945](https://github.com/cockroachdb/cockroach/pull/20945) -- The [`cockroach sql`](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client) command no longer fails when the server is running a version of CockroachDB that does not support the `sql_safe_updates` [session variable](https://www.cockroachlabs.com/docs/v1.1/set-vars#supported-variables). [#20945](https://github.com/cockroachdb/cockroach/pull/20945) -- The [`cockroach sql`](https://www.cockroachlabs.com/docs/v1.1/use-the-built-in-sql-client) command now performs client-side syntax checking automatically only if the client and server are running the same version of CockroachDB. This restriction will be lifted in CockroachDB v2.0. [#21135](https://github.com/cockroachdb/cockroach/pull/21135) -- Reduced temporary disk space usage for the `debug compact` command. [#20502](https://github.com/cockroachdb/cockroach/pull/20502) - -Bug Fixes
- -- Improved rebalancing to make thrashing back and forth between nodes much less likely, including when [localities](https://www.cockroachlabs.com/docs/v1.1/start-a-node#locality) have very different numbers of nodes. [#20934](https://github.com/cockroachdb/cockroach/pull/20934) -- Fixed a scenario where a range that is too big to snapshot can lose availability even with a majority of nodes alive. [#20906](https://github.com/cockroachdb/cockroach/pull/20906) -- Fixed a replica corruption that could occur if a process crashed in the middle of a range split. [#20939](https://github.com/cockroachdb/cockroach/pull/20939) -- Fixed an issue where seemingly irrelevant error messages were being returned for certain [`INSERT`](https://www.cockroachlabs.com/docs/v1.1/insert) statements.[#20855](https://github.com/cockroachdb/cockroach/pull/20855) -- Crash details are now properly copied to the log file even when a node was started with `--logtostderr` as well as in other circumstances when crash details could be lost previously. [#20842](https://github.com/cockroachdb/cockroach/pull/20842) -- Fixed an issue where wildcards (`_`, `%`) and `` escaped characters in `LIKE` patterns were not handled properly. [#20654](https://github.com/cockroachdb/cockroach/pull/20654) -- Fixed the return type signature of the `array_positions()` [built-in function](https://www.cockroachlabs.com/docs/v1.1/functions-and-operators). This caused a crash if the function was used in query execution by the distributed execution engine. [#20652](https://github.com/cockroachdb/cockroach/pull/20652) -- Fixed a crash caused by null [collated strings](https://www.cockroachlabs.com/docs/v1.1/collate). [#20648](https://github.com/cockroachdb/cockroach/pull/20648) -- Fixed a crash caused by `NATURAL JOINS` and `USING` in conjunction with a filter. [#20582](https://github.com/cockroachdb/cockroach/pull/20582) -- Fixed build when new versions of `libgtest` are installed. [#20598](https://github.com/cockroachdb/cockroach/pull/20598) -- Fixed a crash caused by an edge-case when queries are run against a table undergoing a schema change. [#20541](https://github.com/cockroachdb/cockroach/pull/20541) -- Fixed a race condition that would result in some queries hanging after [cancellation](https://www.cockroachlabs.com/docs/v1.1/cancel-query). [#20534](https://github.com/cockroachdb/cockroach/pull/20534) -- Fixed a crash caused by some corner-case queries containing `ORDER BY`. [#20512](https://github.com/cockroachdb/cockroach/pull/20512) -- Prevented generating empty sstables at the [storage layer](https://www.cockroachlabs.com/docs/v1.1/architecture/storage-layer), which could cause corruption. [#20284](https://github.com/cockroachdb/cockroach/pull/20284) -- Fixed a crash caused by [`cockroach dump`](https://www.cockroachlabs.com/docs/v1.1/sql-dump) in the presence of reference cycles. [#20283](https://github.com/cockroachdb/cockroach/pull/20283) -- It is no longer possible to use conflicting `AS OF SYSTEM TIME` clauses in different parts of a query. [#20286](https://github.com/cockroachdb/cockroach/pull/20286) -- Improved S3 resiliency during [`BACKUP`](https://www.cockroachlabs.com/docs/v1.1/backup)/[`RESTORE`](https://www.cockroachlabs.com/docs/v1.1/restore)/[`IMPORT`](https://www.cockroachlabs.com/docs/v1.1/import). [#21003](https://github.com/cockroachdb/cockroach/pull/21003) - -Performance Improvements
- -- Improved garbage collection of very large [transactions](https://www.cockroachlabs.com/docs/v1.1/transactions) and large volumes of abandoned write intents. [#20446](https://github.com/cockroachdb/cockroach/pull/20446) - -Enterprise Edition Changes
- -- [`BACKUP`](https://www.cockroachlabs.com/docs/v1.1/backup)/[`RESTORE`](https://www.cockroachlabs.com/docs/v1.1/restore) jobs now support `201` and `204` return codes from HTTP storage. [#20516](https://github.com/cockroachdb/cockroach/pull/20516) - -Doc Updates
- -- Improved the [initial steps for troubleshooting a problem](https://www.cockroachlabs.com/docs/v1.1/troubleshooting-overview), and added a list of [common errors with recommended solutions](https://www.cockroachlabs.com/docs/v1.1/common-errors). [#2311](https://github.com/cockroachdb/docs/pull/2311) -- Updated docs styling to increase information density. [#2304](https://github.com/cockroachdb/docs/pull/2304) -- Documented how to [request and set trial and enterprise license keys for CockroachDB](https://www.cockroachlabs.com/docs/v1.1/enterprise-licensing). [#2278](https://github.com/cockroachdb/docs/pull/2278) -- Fixed the placement of `AS OF SYSTEM TIME` in enterprise [`BACKUP` examples](https://www.cockroachlabs.com/docs/v1.1/backup#examples). [#2324](https://github.com/cockroachdb/docs/pull/2324) -- Updated the [secure Kubernetes](https://www.cockroachlabs.com/docs/v1.1/orchestrate-cockroachdb-with-kubernetes) tutorial with RBAC support. [#2281](https://github.com/cockroachdb/docs/pull/2281) diff --git a/src/current/_includes/releases/v1.1/v1.1.5.md b/src/current/_includes/releases/v1.1/v1.1.5.md deleted file mode 100644 index 41bbc38eef0..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1.5.md +++ /dev/null @@ -1,40 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -General Changes
- -- Removed error messages from SQL execution statistics included in [diagnostic reporting](https://www.cockroachlabs.com/docs/v1.1/diagnostics-reporting). [#21827][#21827] - -Enterprise Edition Changes
- -- When external storage is not accessible, [`RESTORE`](https://www.cockroachlabs.com/docs/v1.1/restore) jobs no longer loop indefinitely during failure or cancellation. [#21573][#21573] - -Bug Fixes
- -- Errors from DDL statements sent by a client as part of a transaction, but in a different query string than the final commit, are no longer silently swallowed. [#21865][#21865] -- [`DROP INDEX`](https://www.cockroachlabs.com/docs/v1.1/drop-index) with an unqualified index name (without a specific table name) no longer fails if there are [views](https://www.cockroachlabs.com/docs/v1.1/views) in the database. [#21857][#21857] -- Fixed tuple equality to evaluate correctly in the presence of `NULL` elements. [#21237][#21237] -- Fixed an issue with the wire-formatting of [`BYTES`](https://www.cockroachlabs.com/docs/v1.1/bytes) arrays. [#21796][#21796] -- Fixed a stack overflow in the code for shutting down a server when out of disk space. [#21804][#21804] -- Fixed incorrect logic in lease rebalancing that prevented leases from being transferred. [#21442][#21442] - -Doc Updates
- -- Added [best practices for optimizing SQL performance](https://www.cockroachlabs.com/docs/v1.1/performance-best-practices-overview) in CockroachDB. [#2243](https://github.com/cockroachdb/docs/pull/2243) -- Added more detailed [clock synchronization guidance per cloud provider](https://www.cockroachlabs.com/docs/v1.1/recommended-production-settings#clock-synchronization). [#2295](https://github.com/cockroachdb/docs/pull/2295) -- Added a tutorial on using our Kubernetes-orchestrated AWS CloudFormation template for easy deployment and testing of CockroachDB. [#2356](https://github.com/cockroachdb/docs/pull/2356) -- Improved the styling of code samples and page tocs. [#2323](https://github.com/cockroachdb/docs/pull/2323) [#2371](https://github.com/cockroachdb/docs/pull/2371) - -Contributors
- -This release includes 8 merged PRs by 8 authors. - -[#21237]: https://github.com/cockroachdb/cockroach/pull/21237 -[#21442]: https://github.com/cockroachdb/cockroach/pull/21442 -[#21573]: https://github.com/cockroachdb/cockroach/pull/21573 -[#21796]: https://github.com/cockroachdb/cockroach/pull/21796 -[#21804]: https://github.com/cockroachdb/cockroach/pull/21804 -[#21827]: https://github.com/cockroachdb/cockroach/pull/21827 -[#21865]: https://github.com/cockroachdb/cockroach/pull/21865 -[#21857]: https://github.com/cockroachdb/cockroach/pull/21857 diff --git a/src/current/_includes/releases/v1.1/v1.1.6.md b/src/current/_includes/releases/v1.1/v1.1.6.md deleted file mode 100644 index e0c7ccc7a68..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1.6.md +++ /dev/null @@ -1,42 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -This release includes several bug fixes and stability improvements. - -General Changes
- -- Disabling [diagnostics reporting](https://www.cockroachlabs.com/docs/v1.1/diagnostics-reporting) also disables new version notification checks. [#23008][#23008] - -Bug Fixes
- -- Prevented disruptions in performance when gracefully shutting down a node. [#23302][#23302] -- Fixed a zero QPS scenario when gracefully shutting down a node. [#23306][#23306] -- Fixed a panic caused by empty `COCKROACH_UPDATE_CHECK_URL` or `COCKROACH_USAGE_REPORT_URL` environment variables. [#23008][#23008] -- The conversion from [`INTERVAL`](https://www.cockroachlabs.com/docs/v1.1/interval) to [`FLOAT`](https://www.cockroachlabs.com/docs/v1.1/float) now properly returns the number of seconds in the interval. [#22893][#22893] -- Fixed a bug that caused queries of virtual tables with an explicit database name prefix (e.g., `select * from mydb.crdb_internal.tables`) to not get scrubbed properly in [diagnostics reporting](https://www.cockroachlabs.com/docs/v1.1/diagnostics-reporting). [#22815][#22815] -- A `COMMIT` reporting an error generated by a previous parallel statement (i.e., `RETURNING NOTHING`) no longer leaves the connection in an aborted transaction state. Instead, the transaction is considered completed and a `ROLLBACK` is not necessary. [#22814][#22814] -- Fixed an issue with stale buffer data when using the binary format for [`ARRAY`](https://www.cockroachlabs.com/docs/v1.1/array) values. [#22262][#22262] -- Fixed a bug that caused SQL connection errors during node startup. [#22663][#22663] -- Fixed a bug that included [decommissioned nodes](https://www.cockroachlabs.com/docs/v1.1/remove-nodes) in cluster stats aggregates. [#22864][#22864] - -
-
-
-
-[#22262]: https://github.com/cockroachdb/cockroach/pull/22262
-[#22663]: https://github.com/cockroachdb/cockroach/pull/22663
-[#22814]: https://github.com/cockroachdb/cockroach/pull/22814
-[#22815]: https://github.com/cockroachdb/cockroach/pull/22815
-[#22826]: https://github.com/cockroachdb/cockroach/pull/22826
-[#22864]: https://github.com/cockroachdb/cockroach/pull/22864
-[#22893]: https://github.com/cockroachdb/cockroach/pull/22893
-[#23008]: https://github.com/cockroachdb/cockroach/pull/23008
-[#23302]: https://github.com/cockroachdb/cockroach/pull/23302
-[#23306]: https://github.com/cockroachdb/cockroach/pull/23306
diff --git a/src/current/_includes/releases/v1.1/v1.1.7.md b/src/current/_includes/releases/v1.1/v1.1.7.md
deleted file mode 100644
index 5471a18dd37..00000000000
--- a/src/current/_includes/releases/v1.1/v1.1.7.md
+++ /dev/null
@@ -1,22 +0,0 @@
-Contributors
- -This release includes 12 merged PRs by 11 authors. We would like to thank the following contributors from the CockroachDB community: - -- Xudong Zheng - -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -This release includes several bug fixes and stability improvements. - -Build Changes
- -- CockroachDB now builds with go 1.9.4 and higher. [#23639][#23639] - -Bug Fixes
- -- Fixed a deadlock when tables are rapidly [created](https://www.cockroachlabs.com/docs/v1.1/create-table) or [dropped](https://www.cockroachlabs.com/docs/v2.0/drop-table). [#23957][#23957] -- Fixed a rare deadlock for transactions performing schema changes and encountering [retryable errors](https://www.cockroachlabs.com/docs/v1.1/transactions#error-handling). [#23981][#23981] - -Contributors
- -This release includes 3 merged PRs by 2 authors. - -[#23639]: https://github.com/cockroachdb/cockroach/pull/23639 -[#23957]: https://github.com/cockroachdb/cockroach/pull/23957 -[#23981]: https://github.com/cockroachdb/cockroach/pull/23981 diff --git a/src/current/_includes/releases/v1.1/v1.1.8.md b/src/current/_includes/releases/v1.1/v1.1.8.md deleted file mode 100644 index a580423c855..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1.8.md +++ /dev/null @@ -1,18 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -Bug Fixes
- -- Fixed potential cluster unavailability after Raft logs grow too large. [#24889][#24889] -- `ALTER INDEX ... RENAME` can now be used on the primary index. [#24779][#24779] -- Fixed "dangling rows" left over by transactions including both a schema change and `ROLLBACK TO SAVEPOINT`. [#24888][#24888] - -Contributors
- -This release includes 6 merged PRs by 4 authors. - -[#24324]: https://github.com/cockroachdb/cockroach/pull/24324 -[#24779]: https://github.com/cockroachdb/cockroach/pull/24779 -[#24888]: https://github.com/cockroachdb/cockroach/pull/24888 -[#24889]: https://github.com/cockroachdb/cockroach/pull/24889 diff --git a/src/current/_includes/releases/v1.1/v1.1.9.md b/src/current/_includes/releases/v1.1/v1.1.9.md deleted file mode 100644 index f70643dba9b..00000000000 --- a/src/current/_includes/releases/v1.1/v1.1.9.md +++ /dev/null @@ -1,11 +0,0 @@ -{{ include.release }}
- -Release Date: {{ include.release_date | date: "%B %-d, %Y" }} - -Security bug fix
- -- Fixed a vulnerability in which TLS certificates were not validated correctly for internal RPC interfaces. This vulnerability could allow an unauthenticated user with network access to read and write to the cluster. [#30821](https://github.com/cockroachdb/cockroach/issues/30821) - -Contributors
- -This release includes 1 merged PR by 1 author. diff --git a/src/current/_includes/sidebar-data-v1.1.json b/src/current/_includes/sidebar-data-v1.1.json deleted file mode 100644 index e679db97ff4..00000000000 --- a/src/current/_includes/sidebar-data-v1.1.json +++ /dev/null @@ -1,1389 +0,0 @@ -[ - { - "title": "Docs Home", - "is_top_level": true, - "urls": [ - "/" - ] - }, - { - "title": "Quickstart", - "is_top_level": true, - "urls": [ - "/cockroachcloud/quickstart.html" - ] - }, - {% include sidebar-data-cockroachcloud.json %}, - { - "title": "CockroachDB", - "is_top_level": true, - "items": [ - { - "title": "Get Started", - "items": [ - { - "title": "Install CockroachDB", - "urls": [ - "/${VERSION}/install-cockroachdb.html" - ] - }, - { - "title": "Start a Local Cluster", - "items": [ - { - "title": "From Binary", - "urls": [ - "/${VERSION}/start-a-local-cluster.html", - "/${VERSION}/secure-a-cluster.html" - ] - }, - { - "title": "With Docker", - "urls": [ - "/${VERSION}/start-a-local-cluster-in-docker.html" - ] - } - ] - }, - { - "title": "Learn CockroachDB SQL", - "items": [ - { - "title": "Essential SQL Statements", - "urls": [ - "/${VERSION}/learn-cockroachdb-sql.html" - ] - }, - { - "title": "Use the Built-in SQL Client", - "urls": [ - "/${VERSION}/use-the-built-in-sql-client.html" - ] - } - ] - }, - { - "title": "Build an App", - "items": [ - { - "title": "Overview", - "urls": [ - "/${VERSION}/build-an-app-with-cockroachdb.html" - ] - }, - { - "title": "Go", - "urls": [ - "/${VERSION}/build-a-go-app-with-cockroachdb.html", - "/${VERSION}/build-a-go-app-with-cockroachdb-gorm.html" - ] - }, - { - "title": "Python", - "urls": [ - "/${VERSION}/build-a-python-app-with-cockroachdb.html", - "/${VERSION}/build-a-python-app-with-cockroachdb-sqlalchemy.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" - ] - }, - { - "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": "Explore Benefits", - "items": [ - { - "title": "Data Replication", - "urls": [ - "/${VERSION}/demo-data-replication.html" - ] - }, - { - "title": "Fault Tolerance & Recovery", - "urls": [ - "/${VERSION}/demo-fault-tolerance-and-recovery.html" - ] - }, - { - "title": "Automatic Rebalancing", - "urls": [ - "/${VERSION}/demo-automatic-rebalancing.html" - ] - }, - { - "title": "Cross-Cloud Migration", - "urls": [ - "/${VERSION}/demo-automatic-cloud-migration.html" - ] - }, - { - "title": "Follow-the-Workload", - "urls": [ - "/${VERSION}/demo-follow-the-workload.html" - ] - }, - { - "title": "Orchestration", - "urls": [ - "/${VERSION}/orchestrate-a-local-cluster-with-kubernetes-insecure.html" - ] - } - ] - } - ] - }, - { - "title": "Develop", - "items": [ - { - "title": "Install Client Drivers", - "urls": [ - "/${VERSION}/install-client-drivers.html" - ] - }, - { - "title": "Client Connection Parameters", - "urls": [ - "/${VERSION}/connection-parameters.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 TABLE",
- "urls": [
- "/${VERSION}/alter-table.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": "COMMIT",
- "urls": [
- "/${VERSION}/commit-transaction.html"
- ]
- },
- {
- "title": "CREATE DATABASE",
- "urls": [
- "/${VERSION}/create-database.html"
- ]
- },
- {
- "title": "CREATE INDEX",
- "urls": [
- "/${VERSION}/create-index.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 TABLE",
- "urls": [
- "/${VERSION}/drop-table.html"
- ]
- },
- {
- "title": "DROP USER",
- "urls": [
- "/${VERSION}/drop-user.html"
- ]
- },
- {
- "title": "DROP VIEW",
- "urls": [
- "/${VERSION}/drop-view.html"
- ]
- },
- {
- "title": "EXPLAIN",
- "urls": [
- "/${VERSION}/explain.html"
- ]
- },
- {
- "title": "GRANT",
- "urls": [
- "/${VERSION}/grant.html"
- ]
- },
- {
- "title": "IMPORT (Beta)",
- "urls": [
- "/${VERSION}/import.html"
- ]
- },
- {
- "title": "INSERT",
- "urls": [
- "/${VERSION}/insert.html"
- ]
- },
- {
- "title": "PAUSE JOB",
- "urls": [
- "/${VERSION}/pause-job.html"
- ]
- },
- {
- "title": "RENAME COLUMN",
- "urls": [
- "/${VERSION}/rename-column.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": "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",
- "urls": [
- "/${VERSION}/revoke.html"
- ]
- },
- {
- "title": "ROLLBACK",
- "urls": [
- "/${VERSION}/rollback-transaction.html"
- ]
- },
- {
- "title": "SAVEPOINT",
- "urls": [
- "/${VERSION}/savepoint.html"
- ]
- },
- {
- "title": "SELECT",
- "urls": [
- "/${VERSION}/select.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 TABLE",
- "urls": [
- "/${VERSION}/show-create-table.html"
- ]
- },
- {
- "title": "SHOW CREATE VIEW",
- "urls": [
- "/${VERSION}/show-create-view.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 QUERIES",
- "urls": [
- "/${VERSION}/show-queries.html"
- ]
- },
- {
- "title": "SHOW SESSIONS",
- "urls": [
- "/${VERSION}/show-sessions.html"
- ]
- },
- {
- "title": "SHOW TABLES",
- "urls": [
- "/${VERSION}/show-tables.html"
- ]
- },
- {
- "title": "SHOW TRACE",
- "urls": [
- "/${VERSION}/show-trace.html"
- ]
- },
- {
- "title": "SHOW USERS",
- "urls": [
- "/${VERSION}/show-users.html"
- ]
- },
- {
- "title": "TRUNCATE",
- "urls": [
- "/${VERSION}/truncate.html"
- ]
- },
- {
- "title": "UPDATE",
- "urls": [
- "/${VERSION}/update.html"
- ]
- },
- {
- "title": "UPSERT",
- "urls": [
- "/${VERSION}/upsert.html"
- ]
- }
- ]
- },
- {
- "title": "Functions and Operators",
- "urls": [
- "/${VERSION}/functions-and-operators.html"
- ]
- },
- {
- "title": "SQL Syntax",
- "items": [
- {
- "title": "Keywords & Identifiers",
- "urls": [
- "/${VERSION}/keywords-and-identifiers.html"
- ]
- },
- {
- "title": "Constants",
- "urls": [
- "/${VERSION}/sql-constants.html"
- ]
- },
- {
- "title": "Selection Clauses",
- "urls": [
- "/${VERSION}/selection-clauses.html"
- ]
- },
- {
- "title": "Value Expressions",
- "urls": [
- "/${VERSION}/sql-expressions.html"
- ]
- },
- {
- "title": "Table Expressions",
- "urls": [
- "/${VERSION}/table-expressions.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": "Full SQL Grammar",
- "urls": [
- "/${VERSION}/sql-grammar.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": "Data Types",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/data-types.html"
- ]
- },
- {
- "title": "INT",
- "urls": [
- "/${VERSION}/int.html"
- ]
- },
- {
- "title": "UUID",
- "urls": [
- "/${VERSION}/uuid.html"
- ]
- },
- {
- "title": "SERIAL",
- "urls": [
- "/${VERSION}/serial.html"
- ]
- },
- {
- "title": "DECIMAL",
- "urls": [
- "/${VERSION}/decimal.html"
- ]
- },
- {
- "title": "FLOAT",
- "urls": [
- "/${VERSION}/float.html"
- ]
- },
- {
- "title": "BOOL",
- "urls": [
- "/${VERSION}/bool.html"
- ]
- },
- {
- "title": "DATE",
- "urls": [
- "/${VERSION}/date.html"
- ]
- },
- {
- "title": "TIMESTAMP",
- "urls": [
- "/${VERSION}/timestamp.html"
- ]
- },
- {
- "title": "INTERVAL",
- "urls": [
- "/${VERSION}/interval.html"
- ]
- },
- {
- "title": "STRING",
- "urls": [
- "/${VERSION}/string.html"
- ]
- },
- {
- "title": "COLLATE",
- "urls": [
- "/${VERSION}/collate.html"
- ]
- },
- {
- "title": "BYTES",
- "urls": [
- "/${VERSION}/bytes.html"
- ]
- },
- {
- "title": "ARRAY",
- "urls": [
- "/${VERSION}/array.html"
- ]
- }
- ]
- },
- {
- "title": "Privileges",
- "urls": [
- "/${VERSION}/privileges.html"
- ]
- },
- {
- "title": "Transactions",
- "urls": [
- "/${VERSION}/transactions.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": "Column Families",
- "urls": [
- "/${VERSION}/column-families.html"
- ]
- },
- {
- "title": "Interleaved Tables",
- "urls": [
- "/${VERSION}/interleave-in-parent.html"
- ]
- },
- {
- "title": "Parallel Statement Execution",
- "urls": [
- "/${VERSION}/parallel-statement-execution.html"
- ]
- }
- ]
- },
- {
- "title": "Information Schema",
- "urls": [
- "/${VERSION}/information-schema.html"
- ]
- },
- {
- "title": "Porting Applications",
- "items": [
- {
- "title": "From PostgreSQL",
- "urls": [
- "/${VERSION}/porting-postgres.html"
- ]
- }
- ]
- }
- ]
- },
- {
- "title": "Deploy",
- "items": [
- {
- "title": "Production Checklist",
- "urls": [
- "/${VERSION}/recommended-production-settings.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 Deployment",
- "urls": [
- "/${VERSION}/orchestrate-cockroachdb-with-kubernetes.html",
- "/${VERSION}/orchestrate-cockroachdb-with-kubernetes-insecure.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": "Monitoring and Alerting",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/monitoring-and-alerting.html"
- ]
- },
- {
- "title": "Use Prometheus and Alertmanager",
- "urls": [
- "/${VERSION}/monitor-cockroachdb-with-prometheus.html"
- ]
- }
- ]
- },
- {
- "title": "Use the Admin UI",
- "items": [
- {
- "title": "Overview",
- "urls": [
- "/${VERSION}/admin-ui-overview.html"
- ]
- },
- {
- "title": "Access and Navigate the Admin UI",
- "urls": [
- "/${VERSION}/admin-ui-access-and-navigate.html"
- ]
- },
- {
- "title": "Overview Dashboard",
- "urls": [
- "/${VERSION}/admin-ui-overview-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": "Databases Page",
- "urls": [
- "/${VERSION}/admin-ui-databases-page.html"
- ]
- },
- {
- "title": "Jobs Page",
- "urls": [
- "/${VERSION}/admin-ui-jobs-page.html"
- ]
- }
- ]
- },
- {
- "title": "Enterprise Licensing",
- "urls": [
- "/${VERSION}/enterprise-licensing.html"
- ]
- },
- {
- "title": "Start a Node",
- "urls": [
- "/${VERSION}/start-a-node.html"
- ]
- },
- {
- "title": "Initialize a Cluster",
- "urls": [
- "/${VERSION}/initialize-a-cluster.html"
- ]
- },
- {
- "title": "Create Security Certificates",
- "urls": [
- "/${VERSION}/create-security-certificates.html",
- "/${VERSION}/create-security-certificates-openssl.html"
- ]
- },
- {
- "title": "Create & Manage Users",
- "urls": [
- "/${VERSION}/create-and-manage-users.html"
- ]
- },
- {
- "title": "Configure Replication Zones",
- "urls": [
- "/${VERSION}/configure-replication-zones.html"
- ]
- },
- {
- "title": "Cluster Settings",
- "urls": [
- "/${VERSION}/cluster-settings.html"
- ]
- },
- {
- "title": "Cockroach Commands",
- "urls": [
- "/${VERSION}/cockroach-commands.html"
- ]
- }
- ]
- },
- {
- "title": "Maintain",
- "items": [
- {
- "title": "Upgrade to CockroachDB v1.1",
- "urls": [
- "/${VERSION}/upgrade-cockroach-version.html"
- ]
- },
- {
- "title": "Manage Long-Running Queries",
- "urls": [
- "/${VERSION}/manage-long-running-queries.html"
- ]
- },
- {
- "title": "Stop a Node",
- "urls": [
- "/${VERSION}/stop-a-node.html"
- ]
- },
- {
- "title": "Decommission Nodes",
- "urls": [
- "/${VERSION}/remove-nodes.html"
- ]
- },
- {
- "title": "Import Data",
- "urls": [
- "/${VERSION}/import-data.html"
- ]
- },
- {
- "title": "Back up Data",
- "urls": [
- "/${VERSION}/back-up-data.html"
- ]
- },
- {
- "title": "Restore Data",
- "urls": [
- "/${VERSION}/restore-data.html"
- ]
- },
- {
- "title": "Dump/Export Schema or Data",
- "urls": [
- "/${VERSION}/sql-dump.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": "Generate CockroachDB Resources",
- "urls": [
- "/${VERSION}/generate-cockroachdb-resources.html"
- ]
- },
- {
- "title": "View Node Details",
- "urls": [
- "/${VERSION}/view-node-details.html"
- ]
- },
- {
- "title": "View Version Details",
- "urls": [
- "/${VERSION}/view-version-details.html"
- ]
- },
- {
- "title": "Diagnostics Reporting",
- "urls": [
- "/${VERSION}/diagnostics-reporting.html"
- ]
- }
- ]
- },
- {
- "title": "Troubleshoot",
- "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": "Collect Cluster Debug Info",
- "urls": [
- "/${VERSION}/debug-zip.html"
- ]
- },
- {
- "title": "Support Resources",
- "urls": [
- "/${VERSION}/support-resources.html"
- ]
- },
- {
- "title": "File an Issue",
- "urls": [
- "/${VERSION}/file-an-issue.html"
- ]
- }
- ]
- },
- {
- "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": "Contribute",
- "items": [
- {
- "title": "Improve the Docs",
- "urls": [
- "/${VERSION}/improve-the-docs.html"
- ]
- }
- ]
- },
- {% include sidebar-releases.json %},
- {
- "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": "CockroachDB in Comparison",
- "urls": [
- "/${VERSION}/cockroachdb-in-comparison.html"
- ]
- },
- {
- "title": "CockroachDB Features",
- "items": [
- {
- "title": "Multi-Active Availability",
- "urls": [
- "/${VERSION}/multi-active-availability.html"
- ]
- },
- {
- "title": "Simplified Deployment",
- "urls": [
- "/${VERSION}/simplified-deployment.html"
- ]
- },
- {
- "title": "Strong Consistency",
- "urls": [
- "/${VERSION}/strong-consistency.html"
- ]
- },
- {
- "title": "SQL",
- "urls": [
- "/${VERSION}/sql.html"
- ]
- },
- {
- "title": "Distributed Transactions",
- "urls": [
- "/${VERSION}/distributed-transactions.html"
- ]
- },
- {
- "title": "Automated Scaling & Repair",
- "urls": [
- "/${VERSION}/automated-scaling-and-repair.html"
- ]
- },
- {
- "title": "High Availability",
- "urls": [
- "/${VERSION}/high-availability.html"
- ]
- },
- {
- "title": "Open Source",
- "urls": [
- "/${VERSION}/open-source.html"
- ]
- },
- {
- "title": "Go Implementation",
- "urls": [
- "/${VERSION}/go-implementation.html"
- ]
- }
- ]
- }
- ]
- }
- ]
- }
-]
diff --git a/src/current/_includes/v1.1/app/BasicSample.java b/src/current/_includes/v1.1/app/BasicSample.java
deleted file mode 100644
index c6466fb02f8..00000000000
--- a/src/current/_includes/v1.1/app/BasicSample.java
+++ /dev/null
@@ -1,34 +0,0 @@
-import java.sql.*;
-
-/*
-You can compile and run this example with a command like:
- javac BasicSample.java && java -cp .:~/path/to/postgresql-9.4.1208.jar BasicSample
-You can download the postgres JDBC driver jar from https://jdbc.postgresql.org.
-*/
-public class BasicSample {
- public static void main(String[] args) throws ClassNotFoundException, SQLException {
- // Load the postgres JDBC driver.
- Class.forName("org.postgresql.Driver");
-
- // Connect to the "bank" database.
- Connection db = DriverManager.getConnection("jdbc:postgresql://127.0.0.1:26257/bank?sslmode=disable", "maxroach", "");
-
- try {
- // Create the "accounts" table.
- db.createStatement().execute("CREATE TABLE IF NOT EXISTS accounts (id INT PRIMARY KEY, balance INT)");
-
- // Insert two rows into the "accounts" table.
- db.createStatement().execute("INSERT INTO accounts (id, balance) VALUES (1, 1000), (2, 250)");
-
- // Print out the balances.
- System.out.println("Initial balances:");
- ResultSet res = db.createStatement().executeQuery("SELECT id, balance FROM accounts");
- while (res.next()) {
- System.out.printf("\taccount %s: %s\n", res.getInt("id"), res.getInt("balance"));
- }
- } finally {
- // Close the database connection.
- db.close();
- }
- }
-}
diff --git a/src/current/_includes/v1.1/app/TxnSample.java b/src/current/_includes/v1.1/app/TxnSample.java
deleted file mode 100644
index 4f965d6e1a3..00000000000
--- a/src/current/_includes/v1.1/app/TxnSample.java
+++ /dev/null
@@ -1,113 +0,0 @@
-import java.sql.*;
-
-/*
- You can compile and run this example with a command like:
- javac TxnSample.java && java -cp .:~/path/to/postgresql-9.4.1208.jar TxnSample
- You can download the postgres JDBC driver jar from https://jdbc.postgresql.org.
-*/
-
-// Ambiguous whether the transaction committed or not.
-class AmbiguousCommitException extends SQLException{
- public AmbiguousCommitException(Throwable cause) {
- super(cause);
- }
-}
-class InsufficientBalanceException extends Exception {}
-class AccountNotFoundException extends Exception {
- public int account;
- public AccountNotFoundException(int account) {
- this.account = account;
- }
-}
-
-// A simple interface that provides a retryable lambda expression.
-interface RetryableTransaction {
- public void run(Connection conn)
- throws SQLException, InsufficientBalanceException, AccountNotFoundException, AmbiguousCommitException;
-}
-
-public class TxnSample {
- public static RetryableTransaction transferFunds(int from, int to, int amount) {
- return new RetryableTransaction() {
- public void run(Connection conn)
- throws SQLException, InsufficientBalanceException, AccountNotFoundException, AmbiguousCommitException {
- // Check the current balance.
- ResultSet res = conn.createStatement().executeQuery("SELECT balance FROM accounts WHERE id = " + from);
- if(!res.next()) {
- throw new AccountNotFoundException(from);
- }
- int balance = res.getInt("balance");
- if(balance < from) {
- throw new InsufficientBalanceException();
- }
- // Perform the transfer.
- conn.createStatement().executeUpdate("UPDATE accounts SET balance = balance - " + amount + " where id = " + from);
- conn.createStatement().executeUpdate("UPDATE accounts SET balance = balance + " + amount + " where id = " + to);
- }
- };
- }
-
- public static void retryTransaction(Connection conn, RetryableTransaction tx)
- throws SQLException, InsufficientBalanceException, AccountNotFoundException, AmbiguousCommitException {
- Savepoint sp = conn.setSavepoint("cockroach_restart");
- while(true) {
- boolean releaseAttempted = false;
- try {
- tx.run(conn);
- releaseAttempted = true;
- conn.releaseSavepoint(sp);
- }
- catch(SQLException e) {
- String sqlState = e.getSQLState();
- // Check if the error code indicates a SERIALIZATION_FAILURE.
- if(sqlState.equals("40001")) {
- // Signal the database that we will attempt a retry.
- conn.rollback(sp);
- continue;
- } else if(releaseAttempted) {
- throw new AmbiguousCommitException(e);
- } else {
- throw e;
- }
- }
- break;
- }
- conn.commit();
- }
-
- public static void main(String[] args) throws ClassNotFoundException, SQLException {
- // Load the postgres JDBC driver.
- Class.forName("org.postgresql.Driver");
-
- // Connect to the "bank" database.
- Connection db = DriverManager.getConnection("jdbc:postgresql://127.0.0.1:26257/bank?sslmode=disable", "maxroach", "");
- try {
- // We need to turn off autocommit mode to allow for
- // multi-statement transactions.
- db.setAutoCommit(false);
- // Perform the transfer. This assumes the table has
- // already been set up as in the "Build a Test App"
- // tutorial.
- RetryableTransaction transfer = transferFunds(1, 2, 100);
- retryTransaction(db, transfer);
-
- // Check balances after transfer.
- db.setAutoCommit(true);
- ResultSet res = db.createStatement().executeQuery("SELECT id, balance FROM accounts");
- while (res.next()) {
- System.out.printf("\taccount %s: %s\n", res.getInt("id"), res.getInt("balance"));
- }
- } catch(InsufficientBalanceException e) {
- System.out.println("Insufficient balance");
- } catch(AccountNotFoundException e) {
- System.out.println("No users in the table with id " + e.account);
- } catch(AmbiguousCommitException e) {
- System.out.println("Ambiguous result encountered: " + e);
- } catch(SQLException e) {
- System.out.println("SQLException encountered:" + e);
- } finally {
- // Close the database connection.
- db.close();
- }
- }
-}
diff --git a/src/current/_includes/v1.1/app/activerecord-basic-sample.rb b/src/current/_includes/v1.1/app/activerecord-basic-sample.rb
deleted file mode 100644
index 35bccdcb7e8..00000000000
--- a/src/current/_includes/v1.1/app/activerecord-basic-sample.rb
+++ /dev/null
@@ -1,45 +0,0 @@
-require 'active_record'
-require 'pg'
-require 'activerecord-cockroachdb-adapter'
-
-# Connect to CockroachDB through ActiveRecord.
-# In Rails, this configuration would go in config/database.yml as usual.
-ActiveRecord::Base.establish_connection(
- adapter: 'cockroachdb',
- username: 'maxroach',
- password: '',
- database: 'bank',
- host: 'localhost',
- port: 26257,
-)
-
-
-# Define the Account model.
-# In Rails, this would go in app/models/ as usual.
-class Account < ActiveRecord::Base
- validates :id, presence: true
- validates :balance, presence: true
-end
-
-# Define a migration for the accounts table.
-# In Rails, this would go in db/migrate/ as usual.
-class Schema < ActiveRecord::Migration
- def change
- create_table :accounts, force: true do |t|
- t.integer :balance
- end
- end
-end
-
-# Run the schema migration by hand.
-# In Rails, this would be done via rake db:migrate as usual.
-Schema.new.change()
-
-# Create two accounts, inserting two rows into the accounts table.
-Account.create(id: 1, balance: 1000)
-Account.create(id: 2, balance: 250)
-
-# Retrieve accounts and print out the balances
-Account.all.each do |acct|
- puts "#{acct.id} #{acct.balance}"
-end
diff --git a/src/current/_includes/v1.1/app/basic-sample.c b/src/current/_includes/v1.1/app/basic-sample.c
deleted file mode 100644
index e69de29bb2d..00000000000
diff --git a/src/current/_includes/v1.1/app/basic-sample.clj b/src/current/_includes/v1.1/app/basic-sample.clj
deleted file mode 100644
index b139d27b8e1..00000000000
--- a/src/current/_includes/v1.1/app/basic-sample.clj
+++ /dev/null
@@ -1,31 +0,0 @@
-(ns test.test
- (:require [clojure.java.jdbc :as j]
- [test.util :as util]))
-
-;; Define the connection parameters to the cluster.
-(def db-spec {:subprotocol "postgresql"
- :subname "//localhost:26257/bank"
- :user "maxroach"
- :password ""})
-
-(defn test-basic []
- ;; Connect to the cluster and run the code below with
- ;; the connection object bound to 'conn'.
- (j/with-db-connection [conn db-spec]
-
- ;; Insert two rows into the "accounts" table.
- (j/insert! conn :accounts {:id 1 :balance 1000})
- (j/insert! conn :accounts {:id 2 :balance 250})
-
- ;; Print out the balances.
- (println "Initial balances:")
- (->> (j/query conn ["SELECT id, balance FROM accounts"])
- (map println)
- doall)
-
- ;; The database connection is automatically closed by with-db-connection.
- ))
-
-
-(defn -main [& args]
- (test-basic))
diff --git a/src/current/_includes/v1.1/app/basic-sample.cpp b/src/current/_includes/v1.1/app/basic-sample.cpp
deleted file mode 100644
index 0cdb6f65bfd..00000000000
--- a/src/current/_includes/v1.1/app/basic-sample.cpp
+++ /dev/null
@@ -1,41 +0,0 @@
-// Build with g++ -std=c++11 basic-sample.cpp -lpq -lpqxx
-
-#include 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` diff --git a/src/current/_includes/v1.1/misc/remove-user-callout.html b/src/current/_includes/v1.1/misc/remove-user-callout.html deleted file mode 100644 index 086d27509fc..00000000000 --- a/src/current/_includes/v1.1/misc/remove-user-callout.html +++ /dev/null @@ -1 +0,0 @@ -Removing a user does not remove that user's privileges. Therefore, to prevent a future user with an identical username from inheriting an old user's privileges, it's important to revoke a user's privileges before or after removing the user. diff --git a/src/current/_includes/v1.1/misc/schema-change-view-job.md b/src/current/_includes/v1.1/misc/schema-change-view-job.md deleted file mode 100644 index 1e9b4a7444e..00000000000 --- a/src/current/_includes/v1.1/misc/schema-change-view-job.md +++ /dev/null @@ -1 +0,0 @@ -Whenever you initiate a schema change, CockroachDB registers it as a job, which you can view with [`SHOW JOBS`](show-jobs.html). diff --git a/src/current/_includes/v1.1/orchestration/initialize-cluster-insecure.md b/src/current/_includes/v1.1/orchestration/initialize-cluster-insecure.md deleted file mode 100644 index 1b374e6dbf9..00000000000 --- a/src/current/_includes/v1.1/orchestration/initialize-cluster-insecure.md +++ /dev/null @@ -1,40 +0,0 @@ -1. Use our [`cluster-init.yaml`](https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/cluster-init.yaml) file to perform a one-time initialization that joins the nodes into a single cluster: - - {% include copy-clipboard.html %} - ~~~ shell - $ kubectl create -f https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/cluster-init.yaml - ~~~ - - ~~~ - job "cluster-init" created - ~~~ - -2. Confirm that cluster initialization has completed successfully. The job - should be considered successful and the CockroachDB pods should soon be - considered `Ready`: - - {% include copy-clipboard.html %} - ~~~ shell - $ kubectl get job cluster-init - ~~~ - - ~~~ - NAME DESIRED SUCCESSFUL AGE - cluster-init 1 1 2m - ~~~ - - {% include copy-clipboard.html %} - ~~~ shell - $ kubectl get pods - ~~~ - - ~~~ - NAME READY STATUS RESTARTS AGE - cockroachdb-0 1/1 Running 0 3m - cockroachdb-1 1/1 Running 0 3m - cockroachdb-2 1/1 Running 0 3m - ~~~ - -{{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
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 %}
-
-2. Go to https://localhost:8080.
-
-{% else %}
-
-2. Go to http://localhost:8080.
-
-{% endif %}
-
-3. 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/v1.1/orchestration/start-cluster.md b/src/current/_includes/v1.1/orchestration/start-cluster.md
deleted file mode 100644
index 18504455761..00000000000
--- a/src/current/_includes/v1.1/orchestration/start-cluster.md
+++ /dev/null
@@ -1,67 +0,0 @@
-{% if page.secure == true %}
-
-From your local workstation, use our [`cockroachdb-statefulset-secure.yaml`](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml) file to create the StatefulSet that automatically creates 3 pods, each with a CockroachDB node running inside it:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ kubectl create -f https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/cockroachdb-statefulset-secure.yaml
-~~~
-
-~~~
-serviceaccount "cockroachdb" created
-role "cockroachdb" created
-clusterrole "cockroachdb" created
-rolebinding "cockroachdb" created
-clusterrolebinding "cockroachdb" created
-service "cockroachdb-public" created
-service "cockroachdb" created
-poddisruptionbudget "cockroachdb-budget" created
-statefulset "cockroachdb" created
-~~~
-
-{% else %}
-
-1. From your local workstation, use our [`cockroachdb-statefulset.yaml`](https://github.com/cockroachdb/cockroach/blob/master/cloud/kubernetes/cockroachdb-statefulset.yaml) file to create the StatefulSet that automatically creates 3 pods, each with a CockroachDB node running inside it:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl create -f https://raw.githubusercontent.com/cockroachdb/cockroach/master/cloud/kubernetes/cockroachdb-statefulset.yaml
- ~~~
-
- ~~~
- service "cockroachdb-public" created
- service "cockroachdb" created
- poddisruptionbudget "cockroachdb-budget" created
- statefulset "cockroachdb" created
- ~~~
-
-2. Confirm that three pods are `Running` successfully. Note that they will not
- be considered `Ready` until after the cluster has been initialized:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl get pods
- ~~~
-
- ~~~
- NAME READY STATUS RESTARTS AGE
- cockroachdb-0 0/1 Running 0 2m
- cockroachdb-1 0/1 Running 0 2m
- cockroachdb-2 0/1 Running 0 2m
- ~~~
-
-3. Confirm that the persistent volumes and corresponding claims were created successfully for all three pods:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl get persistentvolumes
- ~~~
-
- ~~~
- NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM REASON AGE
- pvc-52f51ecf-8bd5-11e6-a4f4-42010a800002 1Gi RWO Delete Bound default/datadir-cockroachdb-0 26s
- pvc-52fd3a39-8bd5-11e6-a4f4-42010a800002 1Gi RWO Delete Bound default/datadir-cockroachdb-1 27s
- pvc-5315efda-8bd5-11e6-a4f4-42010a800002 1Gi RWO Delete Bound default/datadir-cockroachdb-2 27s
- ~~~
-
-{% endif %}
diff --git a/src/current/_includes/v1.1/orchestration/start-kubernetes.md b/src/current/_includes/v1.1/orchestration/start-kubernetes.md
deleted file mode 100644
index a71013ca981..00000000000
--- a/src/current/_includes/v1.1/orchestration/start-kubernetes.md
+++ /dev/null
@@ -1,82 +0,0 @@
-## Step 1. Choose your deployment environment
-
-Choose whether you want to orchestrate CockroachDB with Kubernetes using the hosted Google Kubernetes Engine (GKE) service or manually on Google Compute Engine (GCE) or AWS. The instructions below will change slightly depending on your choice.
-
-
-
-
-
-
-
-## Step 2. Start Kubernetes
-
-
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ gcloud container clusters delete cockroachdb
- ~~~
-
-
-
-
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ cluster/kube-down.sh
- ~~~
-
-
-
-
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ cluster/kube-down.sh
- ~~~
-
-
-
- {{site.data.alerts.callout_danger}}If you stop Kubernetes without first deleting the persistent volumes, they will still exist in your cloud project.{{site.data.alerts.end}}
diff --git a/src/current/_includes/v1.1/orchestration/test-cluster-insecure.md b/src/current/_includes/v1.1/orchestration/test-cluster-insecure.md
deleted file mode 100644
index 52396b848ad..00000000000
--- a/src/current/_includes/v1.1/orchestration/test-cluster-insecure.md
+++ /dev/null
@@ -1,45 +0,0 @@
-1. Launch a temporary interactive pod and start the [built-in SQL client](use-the-built-in-sql-client.html) inside it:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kubectl run cockroachdb -it --image=cockroachdb/cockroach --rm --restart=Never \
- -- sql --insecure --host=cockroachdb-public
- ~~~
-
-2. Run some basic [CockroachDB SQL statements](learn-cockroachdb-sql.html):
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > CREATE DATABASE bank;
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > CREATE TABLE bank.accounts (id INT PRIMARY KEY, balance DECIMAL);
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > INSERT INTO bank.accounts VALUES (1, 1000.50);
- ~~~
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > SELECT * FROM bank.accounts;
- ~~~
-
- ~~~
- +----+---------+
- | id | balance |
- +----+---------+
- | 1 | 1000.5 |
- +----+---------+
- (1 row)
- ~~~
-
-3. Exit the SQL shell and delete the temporary pod:
-
- {% include copy-clipboard.html %}
- ~~~ sql
- > \q
- ~~~
diff --git a/src/current/_includes/v1.1/prod-deployment/insecure-initialize-cluster.md b/src/current/_includes/v1.1/prod-deployment/insecure-initialize-cluster.md
deleted file mode 100644
index 5d1384c8467..00000000000
--- a/src/current/_includes/v1.1/prod-deployment/insecure-initialize-cluster.md
+++ /dev/null
@@ -1,12 +0,0 @@
-On your local machine, complete the node startup process and have them join together as a cluster:
-
-1. [Install CockroachDB](install-cockroachdb.html) on your local machine, if you haven't already.
-
-2. Run the [`cockroach init`](initialize-a-cluster.html) command, with the `--host` flag set to the address of any node:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ cockroach init --insecure --host=
- ~~~
-
- Each node then prints helpful details to the [standard output](start-a-node.html#standard-output), such as the CockroachDB version, the URL for the admin UI, and the SQL URL for clients.
diff --git a/src/current/_includes/v1.1/prod-deployment/insecure-recommendations.md b/src/current/_includes/v1.1/prod-deployment/insecure-recommendations.md
deleted file mode 100644
index e6f7fc0b9fe..00000000000
--- a/src/current/_includes/v1.1/prod-deployment/insecure-recommendations.md
+++ /dev/null
@@ -1,15 +0,0 @@
-- If you plan to use CockroachDB in production, carefully review the [Production Checklist](recommended-production-settings.html).
-
-- Consider using a [secure cluster](manual-deployment.html) instead. Using an insecure cluster comes with risks:
- - Your cluster is open to any client that can access any node's IP addresses.
- - Any user, even `root`, can log in without providing a password.
- - Any user, connecting as `root`, can read or write any data in your cluster.
- - There is no network encryption or authentication, and thus no confidentiality.
-
-- Decide how you want to access your Admin UI:
-
- Access Level | Description
- -------------|------------
- Partially open | Set a firewall rule to allow only specific IP addresses to communicate on port `8080`.
- Completely open | Set a firewall rule to allow all IP addresses to communicate on port `8080`.
- Completely closed | Set a firewall rule to disallow all communication on port `8080`. In this case, a machine with SSH access to a node could use an SSH tunnel to access the Admin UI.
diff --git a/src/current/_includes/v1.1/prod-deployment/insecure-requirements.md b/src/current/_includes/v1.1/prod-deployment/insecure-requirements.md
deleted file mode 100644
index 52640254763..00000000000
--- a/src/current/_includes/v1.1/prod-deployment/insecure-requirements.md
+++ /dev/null
@@ -1,5 +0,0 @@
-- You must have [SSH access]({{page.ssh-link}}) to each machine. This is necessary for distributing and starting CockroachDB binaries.
-
-- Your network configuration must allow TCP communication on the following ports:
- - `26257` for intra-cluster and client-cluster communication
- - `8080` to expose your Admin UI
diff --git a/src/current/_includes/v1.1/prod-deployment/insecure-scale-cluster.md b/src/current/_includes/v1.1/prod-deployment/insecure-scale-cluster.md
deleted file mode 100644
index 66df603eb03..00000000000
--- a/src/current/_includes/v1.1/prod-deployment/insecure-scale-cluster.md
+++ /dev/null
@@ -1,120 +0,0 @@
-You can start the nodes manually or automate the process using [systemd](https://www.freedesktop.org/wiki/Software/systemd/).
-
-
-
-
-
-
-
-If you want the node to listen on multiple interfaces, leave `--host` empty.
If you want the node to communicate with other nodes on an internal address (e.g., within a private network) while listening on all interfaces, leave `--host` empty and set the `--advertise-host` flag to the internal address. - `--join` | Identifies the address and port of 3-5 of the initial nodes of the cluster. - -9. Repeat these steps for each additional node that you want in your cluster. - -
-
-
-
-
-
-If you want the node to listen on multiple interfaces, leave `--host` out.
If you want the node to communicate with other nodes on an internal address (e.g., within a private network) while listening on all interfaces, leave `--host` out and set the `--advertise-host` flag to the internal address. - `--locality` | Key-value pairs that describe the location of the node, e.g., country, region, datacenter, rack, etc. It is recommended to set `--locality` when deploying across multiple datacenters or when there is otherwise high latency between nodes. It is also required to use certain enterprise features. For more details, see [Locality](start-a-node.html#locality). - `--cache`
`--max-sql-memory` | Increases the node's cache and temporary SQL memory size to 25% of available system memory to improve read performance and increase capacity for in-memory SQL processing (see [Recommended Production Settings](recommended-production-settings.html) for more details). - `--join` | Identifies the address and port of 3-5 of the initial nodes of the cluster. - `--background` | Starts the node in the background so you gain control of the terminal to issue more commands. - - For other flags not explicitly set, the command uses default values. For example, the node stores data in `--store=cockroach-data`, binds internal and client communication to `--port=26257`, and binds Admin UI HTTP requests to `--http-port=8080`. To set these options manually, see [Start a Node](start-a-node.html). - -5. Repeat these steps for each additional node that you want in your cluster. - -
If you want the node to listen on multiple interfaces, leave `--host` empty.
If you want the node to communicate with other nodes on an internal address (e.g., within a private network) while listening on all interfaces, leave `--host` empty and set the `--advertise-host` flag to the internal address. - -9. Start the CockroachDB cluster: - - {% include copy-clipboard.html %} - ~~~ shell - $ systemctl start insecurecockroachdb - ~~~ - -10. Repeat these steps for each additional node that you want in your cluster. - -{{site.data.alerts.callout_info}} -`systemd` handles node restarts in case of node failure. To stop a node without `systemd` restarting it, run
systemctl stop insecurecockroachdb
-{{site.data.alerts.end}}
-
-node.crt and node.key As an alternative to deleting these files, you can run the next cockroach cert create-node commands with the --overwrite flag.{{site.data.alerts.end}}
-
-7. Create the certificate and key for the second node, issued to all common names you might use to refer to the node as well as to the load balancer instances:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ cockroach cert create-node \
-
-
-
-
-
-
-If you want the node to listen on multiple interfaces, leave `--host` empty.
If you want the node to communicate with other nodes on an internal address (e.g., within a private network) while listening on all interfaces, leave `--host` empty and set the `--advertise-host` flag to the internal address. - `--join` | Identifies the address and port of 3-5 of the initial nodes of the cluster. - -10. Repeat these steps for each additional node that you want in your cluster. - -
-
-
-
-
-
-If you want the node to listen on multiple interfaces, leave `--host` out.
If you want the node to communicate with other nodes on an internal address (e.g., within a private network) while listening on all interfaces, leave `--host` out and set the `--advertise-host` flag to the internal address. - `--locality` | Key-value pairs that describe the location of the node, e.g., country, region, datacenter, rack, etc. It is recommended to set `--locality` when deploying across multiple datacenters or when there is otherwise high latency between nodes. It is also required to use certain enterprise features. For more details, see [Locality](start-a-node.html#locality). - `--cache`
`--max-sql-memory` | Increases the node's cache and temporary SQL memory size to 25% of available system memory to improve read performance and increase capacity for in-memory SQL processing (see [Recommended Production Settings](recommended-production-settings.html) for more details). - `--join` | Identifies the address and port of 3-5 of the initial nodes of the cluster. - `--background` | Starts the node in the background so you gain control of the terminal to issue more commands. - - For other flags not explicitly set, the command uses default values. For example, the node stores data in `--store=cockroach-data`, binds internal and client communication to `--port=26257`, and binds Admin UI HTTP requests to `--http-port=8080`. To set these options manually, see [Start a Node](start-a-node.html). - -5. Repeat these steps for each additional node that you want in your cluster. - -
If you want the node to listen on multiple interfaces, leave `--host` empty.
If you want the node to communicate with other nodes on an internal address (e.g., within a private network) while listening on all interfaces, leave `--host` empty and set the `--advertise-host` flag to the internal address. - -10. Start the CockroachDB cluster: - - {% include copy-clipboard.html %} - ~~~ shell - $ systemctl start securecockroachdb - ~~~ - -11. Repeat these steps for each additional node that you want in your cluster. - -{{site.data.alerts.callout_info}} -`systemd` handles node restarts in case of node failure. To stop a node without `systemd` restarting it, run
systemctl stop securecockroachdb
-{{site.data.alerts.end}}
-
-**Env Variable:** `COCKROACH_URL`
**Default:** no URL diff --git a/src/current/_includes/v1.1/sql/connection-parameters.md b/src/current/_includes/v1.1/sql/connection-parameters.md deleted file mode 100644 index 2e74255dcc4..00000000000 --- a/src/current/_includes/v1.1/sql/connection-parameters.md +++ /dev/null @@ -1,7 +0,0 @@ -Flag | Description ------|------------ -`--host` | The server host to connect to. This can be the address of any node in the cluster.
**Env Variable:** `COCKROACH_HOST`
**Default:**`localhost` -`--port`
`-p` | The server port to connect to.
**Env Variable:** `COCKROACH_PORT`
**Default:** `26257` -`--user`
`-u` | The [SQL user](create-and-manage-users.html) that will own the client session.
**Env Variable:** `COCKROACH_USER`
**Default:** `root` -`--insecure` | Use an insecure connection.
**Env Variable:** `COCKROACH_INSECURE`
**Default:** `false` -`--certs-dir` | The path to the [certificate directory](create-security-certificates.html) containing the CA and client certificates and client key.
**Env Variable:** `COCKROACH_CERTS_DIR`
**Default:** `${HOME}/.cockroach-certs/` \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/add_column.html b/src/current/_includes/v1.1/sql/diagrams/add_column.html deleted file mode 100644 index af8294780aa..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/add_column.html +++ /dev/null @@ -1,58 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/add_constraint.html b/src/current/_includes/v1.1/sql/diagrams/add_constraint.html deleted file mode 100644 index e4d6d884a90..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/add_constraint.html +++ /dev/null @@ -1,41 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/alter_column.html b/src/current/_includes/v1.1/sql/diagrams/alter_column.html deleted file mode 100644 index 9f59c11c25f..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/alter_column.html +++ /dev/null @@ -1,59 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/alter_view.html b/src/current/_includes/v1.1/sql/diagrams/alter_view.html deleted file mode 100644 index 2e481fa60aa..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/alter_view.html +++ /dev/null @@ -1,36 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/backup.html b/src/current/_includes/v1.1/sql/diagrams/backup.html deleted file mode 100644 index 1974cb5bcb0..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/backup.html +++ /dev/null @@ -1,73 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/begin_transaction.html b/src/current/_includes/v1.1/sql/diagrams/begin_transaction.html deleted file mode 100644 index ee2372d9861..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/begin_transaction.html +++ /dev/null @@ -1,47 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/cancel_job.html b/src/current/_includes/v1.1/sql/diagrams/cancel_job.html deleted file mode 100644 index aca612ec209..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/cancel_job.html +++ /dev/null @@ -1,19 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/cancel_query.html b/src/current/_includes/v1.1/sql/diagrams/cancel_query.html deleted file mode 100644 index 6cc33a38466..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/cancel_query.html +++ /dev/null @@ -1,19 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/check_column_level.html b/src/current/_includes/v1.1/sql/diagrams/check_column_level.html deleted file mode 100644 index 59eec3e3c15..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/check_column_level.html +++ /dev/null @@ -1,70 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/check_table_level.html b/src/current/_includes/v1.1/sql/diagrams/check_table_level.html deleted file mode 100644 index 6066d637220..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/check_table_level.html +++ /dev/null @@ -1,60 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/col_qualification.html b/src/current/_includes/v1.1/sql/diagrams/col_qualification.html deleted file mode 100644 index c0783fe6806..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/col_qualification.html +++ /dev/null @@ -1,115 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/column_def.html b/src/current/_includes/v1.1/sql/diagrams/column_def.html deleted file mode 100644 index ee1245cce55..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/column_def.html +++ /dev/null @@ -1,23 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/commit_transaction.html b/src/current/_includes/v1.1/sql/diagrams/commit_transaction.html deleted file mode 100644 index 12914f3e1cb..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/commit_transaction.html +++ /dev/null @@ -1,17 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/create_database.html b/src/current/_includes/v1.1/sql/diagrams/create_database.html deleted file mode 100644 index c621b08e138..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/create_database.html +++ /dev/null @@ -1,42 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/create_index.html b/src/current/_includes/v1.1/sql/diagrams/create_index.html deleted file mode 100644 index e18dc99378e..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/create_index.html +++ /dev/null @@ -1,84 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/create_table.html b/src/current/_includes/v1.1/sql/diagrams/create_table.html deleted file mode 100644 index a082a9580ad..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/create_table.html +++ /dev/null @@ -1,62 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/create_table_as.html b/src/current/_includes/v1.1/sql/diagrams/create_table_as.html deleted file mode 100644 index f3a1df94cfb..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/create_table_as.html +++ /dev/null @@ -1,50 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/create_user.html b/src/current/_includes/v1.1/sql/diagrams/create_user.html deleted file mode 100644 index 45aaffe4d37..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/create_user.html +++ /dev/null @@ -1,30 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/create_view.html b/src/current/_includes/v1.1/sql/diagrams/create_view.html deleted file mode 100644 index 11ae19e1c83..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/create_view.html +++ /dev/null @@ -1,38 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/default_value_column_level.html b/src/current/_includes/v1.1/sql/diagrams/default_value_column_level.html deleted file mode 100644 index 0ba9afca9c4..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/default_value_column_level.html +++ /dev/null @@ -1,64 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/delete.html b/src/current/_includes/v1.1/sql/diagrams/delete.html deleted file mode 100644 index 23fe8ece582..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/delete.html +++ /dev/null @@ -1,68 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/drop_column.html b/src/current/_includes/v1.1/sql/diagrams/drop_column.html deleted file mode 100644 index abdbbff2353..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/drop_column.html +++ /dev/null @@ -1,48 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/drop_constraint.html b/src/current/_includes/v1.1/sql/diagrams/drop_constraint.html deleted file mode 100644 index 767437f8d16..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/drop_constraint.html +++ /dev/null @@ -1,42 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/drop_database.html b/src/current/_includes/v1.1/sql/diagrams/drop_database.html deleted file mode 100644 index 038eb0befc1..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/drop_database.html +++ /dev/null @@ -1,31 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/drop_index.html b/src/current/_includes/v1.1/sql/diagrams/drop_index.html deleted file mode 100644 index 1f997ca6fd8..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/drop_index.html +++ /dev/null @@ -1,42 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/drop_table.html b/src/current/_includes/v1.1/sql/diagrams/drop_table.html deleted file mode 100644 index 833929d41da..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/drop_table.html +++ /dev/null @@ -1,34 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/drop_user.html b/src/current/_includes/v1.1/sql/diagrams/drop_user.html deleted file mode 100644 index 57c3db991b9..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/drop_user.html +++ /dev/null @@ -1,28 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/drop_view.html b/src/current/_includes/v1.1/sql/diagrams/drop_view.html deleted file mode 100644 index ff559cb165d..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/drop_view.html +++ /dev/null @@ -1,34 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/explain.html b/src/current/_includes/v1.1/sql/diagrams/explain.html deleted file mode 100644 index 89ca35dd0fa..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/explain.html +++ /dev/null @@ -1,40 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/family_def.html b/src/current/_includes/v1.1/sql/diagrams/family_def.html deleted file mode 100644 index c0034d4f13e..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/family_def.html +++ /dev/null @@ -1,30 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/foreign_key_column_level.html b/src/current/_includes/v1.1/sql/diagrams/foreign_key_column_level.html deleted file mode 100644 index a963e586425..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/foreign_key_column_level.html +++ /dev/null @@ -1,75 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/foreign_key_table_level.html b/src/current/_includes/v1.1/sql/diagrams/foreign_key_table_level.html deleted file mode 100644 index 2eb3498af46..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/foreign_key_table_level.html +++ /dev/null @@ -1,85 +0,0 @@ - \ No newline at end of file diff --git a/src/current/_includes/v1.1/sql/diagrams/grammar.html b/src/current/_includes/v1.1/sql/diagrams/grammar.html deleted file mode 100644 index 71d8cf930a9..00000000000 --- a/src/current/_includes/v1.1/sql/diagrams/grammar.html +++ /dev/null @@ -1,10848 +0,0 @@ -
-
-
-
-
-
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
- -
diff --git a/src/current/_includes/v1.1/sql/diagrams/grant.html b/src/current/_includes/v1.1/sql/diagrams/grant.html
deleted file mode 100644
index 4271082a93c..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/grant.html
+++ /dev/null
@@ -1,74 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/import.html b/src/current/_includes/v1.1/sql/diagrams/import.html
deleted file mode 100644
index 337df23de82..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/import.html
+++ /dev/null
@@ -1,72 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/index_def.html b/src/current/_includes/v1.1/sql/diagrams/index_def.html
deleted file mode 100644
index 5e44af24228..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/index_def.html
+++ /dev/null
@@ -1,55 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/insert.html b/src/current/_includes/v1.1/sql/diagrams/insert.html
deleted file mode 100644
index a9285df7b1d..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/insert.html
+++ /dev/null
@@ -1,65 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/interleave.html b/src/current/_includes/v1.1/sql/diagrams/interleave.html
deleted file mode 100644
index 2053298411e..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/interleave.html
+++ /dev/null
@@ -1,64 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/not_null_column_level.html b/src/current/_includes/v1.1/sql/diagrams/not_null_column_level.html
deleted file mode 100644
index 52e17e9d57d..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/not_null_column_level.html
+++ /dev/null
@@ -1,59 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/opt_interleave.html b/src/current/_includes/v1.1/sql/diagrams/opt_interleave.html
deleted file mode 100644
index cb1593971c6..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/opt_interleave.html
+++ /dev/null
@@ -1,33 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/pause_job.html b/src/current/_includes/v1.1/sql/diagrams/pause_job.html
deleted file mode 100644
index 86ecbbd14e0..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/pause_job.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/primary_key_column_level.html b/src/current/_includes/v1.1/sql/diagrams/primary_key_column_level.html
deleted file mode 100644
index f938b641654..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/primary_key_column_level.html
+++ /dev/null
@@ -1,59 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/primary_key_table_level.html b/src/current/_includes/v1.1/sql/diagrams/primary_key_table_level.html
deleted file mode 100644
index db8ece49c39..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/primary_key_table_level.html
+++ /dev/null
@@ -1,63 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/release_savepoint.html b/src/current/_includes/v1.1/sql/diagrams/release_savepoint.html
deleted file mode 100644
index 194ce6573ca..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/release_savepoint.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/rename_column.html b/src/current/_includes/v1.1/sql/diagrams/rename_column.html
deleted file mode 100644
index 2d275bc9de7..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/rename_column.html
+++ /dev/null
@@ -1,44 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/rename_database.html b/src/current/_includes/v1.1/sql/diagrams/rename_database.html
deleted file mode 100644
index ce9ddd3ddba..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/rename_database.html
+++ /dev/null
@@ -1,30 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/rename_index.html b/src/current/_includes/v1.1/sql/diagrams/rename_index.html
deleted file mode 100644
index e9b242c1afe..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/rename_index.html
+++ /dev/null
@@ -1,44 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/rename_table.html b/src/current/_includes/v1.1/sql/diagrams/rename_table.html
deleted file mode 100644
index 316c56482eb..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/rename_table.html
+++ /dev/null
@@ -1,36 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/reset_csetting.html b/src/current/_includes/v1.1/sql/diagrams/reset_csetting.html
deleted file mode 100644
index 49e120ffc69..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/reset_csetting.html
+++ /dev/null
@@ -1,22 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/reset_session.html b/src/current/_includes/v1.1/sql/diagrams/reset_session.html
deleted file mode 100644
index 0a47ec52d49..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/reset_session.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/restore.html b/src/current/_includes/v1.1/sql/diagrams/restore.html
deleted file mode 100644
index 7dbfbc34d1a..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/restore.html
+++ /dev/null
@@ -1,60 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/resume_job.html b/src/current/_includes/v1.1/sql/diagrams/resume_job.html
deleted file mode 100644
index fe577ebd40d..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/resume_job.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/revoke.html b/src/current/_includes/v1.1/sql/diagrams/revoke.html
deleted file mode 100644
index f321d3a87a8..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/revoke.html
+++ /dev/null
@@ -1,74 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/rollback_transaction.html b/src/current/_includes/v1.1/sql/diagrams/rollback_transaction.html
deleted file mode 100644
index c34d5d12047..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/rollback_transaction.html
+++ /dev/null
@@ -1,22 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/savepoint.html b/src/current/_includes/v1.1/sql/diagrams/savepoint.html
deleted file mode 100644
index 9b7dc70608b..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/savepoint.html
+++ /dev/null
@@ -1,16 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/select.html b/src/current/_includes/v1.1/sql/diagrams/select.html
deleted file mode 100644
index 86251fe92f9..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/select.html
+++ /dev/null
@@ -1,120 +0,0 @@
-
diff --git a/src/current/_includes/v1.1/sql/diagrams/set_cluster_setting.html b/src/current/_includes/v1.1/sql/diagrams/set_cluster_setting.html
deleted file mode 100644
index b6554c7be52..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/set_cluster_setting.html
+++ /dev/null
@@ -1,36 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/set_transaction.html b/src/current/_includes/v1.1/sql/diagrams/set_transaction.html
deleted file mode 100644
index 14d8b19a019..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/set_transaction.html
+++ /dev/null
@@ -1,68 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/set_var.html b/src/current/_includes/v1.1/sql/diagrams/set_var.html
deleted file mode 100644
index 360741a76db..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/set_var.html
+++ /dev/null
@@ -1,53 +0,0 @@
-
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_backup.html b/src/current/_includes/v1.1/sql/diagrams/show_backup.html
deleted file mode 100644
index 0f4f4e2c379..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_backup.html
+++ /dev/null
@@ -1,19 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_cluster_setting.html b/src/current/_includes/v1.1/sql/diagrams/show_cluster_setting.html
deleted file mode 100644
index eae5bb8b447..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_cluster_setting.html
+++ /dev/null
@@ -1,34 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_columns.html b/src/current/_includes/v1.1/sql/diagrams/show_columns.html
deleted file mode 100644
index 7b47a3b3123..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_columns.html
+++ /dev/null
@@ -1,22 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_constraints.html b/src/current/_includes/v1.1/sql/diagrams/show_constraints.html
deleted file mode 100644
index 9c520ae9bc6..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_constraints.html
+++ /dev/null
@@ -1,25 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_create_table.html b/src/current/_includes/v1.1/sql/diagrams/show_create_table.html
deleted file mode 100644
index c88be5e28fa..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_create_table.html
+++ /dev/null
@@ -1,22 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_create_view.html b/src/current/_includes/v1.1/sql/diagrams/show_create_view.html
deleted file mode 100644
index c5ef64c5708..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_create_view.html
+++ /dev/null
@@ -1,22 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_databases.html b/src/current/_includes/v1.1/sql/diagrams/show_databases.html
deleted file mode 100644
index 487bfc4e629..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_databases.html
+++ /dev/null
@@ -1,14 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_grants.html b/src/current/_includes/v1.1/sql/diagrams/show_grants.html
deleted file mode 100644
index e5d611689e3..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_grants.html
+++ /dev/null
@@ -1,50 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_index.html b/src/current/_includes/v1.1/sql/diagrams/show_index.html
deleted file mode 100644
index 3014183c521..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_index.html
+++ /dev/null
@@ -1,28 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_jobs.html b/src/current/_includes/v1.1/sql/diagrams/show_jobs.html
deleted file mode 100644
index b59d4d176d0..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_jobs.html
+++ /dev/null
@@ -1,14 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_queries.html b/src/current/_includes/v1.1/sql/diagrams/show_queries.html
deleted file mode 100644
index 26376243dac..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_queries.html
+++ /dev/null
@@ -1,20 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_sessions.html b/src/current/_includes/v1.1/sql/diagrams/show_sessions.html
deleted file mode 100644
index 3b2aa5b16ee..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_sessions.html
+++ /dev/null
@@ -1,20 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_tables.html b/src/current/_includes/v1.1/sql/diagrams/show_tables.html
deleted file mode 100644
index 570e6222172..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_tables.html
+++ /dev/null
@@ -1,22 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_trace.html b/src/current/_includes/v1.1/sql/diagrams/show_trace.html
deleted file mode 100644
index 29eb658f64c..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_trace.html
+++ /dev/null
@@ -1,28 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_users.html b/src/current/_includes/v1.1/sql/diagrams/show_users.html
deleted file mode 100644
index 7c33b7f00b4..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_users.html
+++ /dev/null
@@ -1,14 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/show_var.html b/src/current/_includes/v1.1/sql/diagrams/show_var.html
deleted file mode 100644
index fb7ec6f4ce8..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/show_var.html
+++ /dev/null
@@ -1,20 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/table.html b/src/current/_includes/v1.1/sql/diagrams/table.html
deleted file mode 100644
index e69de29bb2d..00000000000
diff --git a/src/current/_includes/v1.1/sql/diagrams/table_constraint.html b/src/current/_includes/v1.1/sql/diagrams/table_constraint.html
deleted file mode 100644
index 1390a9e4af7..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/table_constraint.html
+++ /dev/null
@@ -1,115 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/truncate.html b/src/current/_includes/v1.1/sql/diagrams/truncate.html
deleted file mode 100644
index 06cb91a310c..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/truncate.html
+++ /dev/null
@@ -1,28 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/unique_column_level.html b/src/current/_includes/v1.1/sql/diagrams/unique_column_level.html
deleted file mode 100644
index c7c178e9351..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/unique_column_level.html
+++ /dev/null
@@ -1,59 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/unique_table_level.html b/src/current/_includes/v1.1/sql/diagrams/unique_table_level.html
deleted file mode 100644
index e77a972161a..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/unique_table_level.html
+++ /dev/null
@@ -1,63 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/update.html b/src/current/_includes/v1.1/sql/diagrams/update.html
deleted file mode 100644
index 78f1ef6ee07..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/update.html
+++ /dev/null
@@ -1,101 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/upsert.html b/src/current/_includes/v1.1/sql/diagrams/upsert.html
deleted file mode 100644
index df7aa8d2a6e..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/upsert.html
+++ /dev/null
@@ -1,60 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/sql/diagrams/validate_constraint.html b/src/current/_includes/v1.1/sql/diagrams/validate_constraint.html
deleted file mode 100644
index d470d8dd98f..00000000000
--- a/src/current/_includes/v1.1/sql/diagrams/validate_constraint.html
+++ /dev/null
@@ -1,36 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/_includes/v1.1/start-in-docker/mac-linux-steps.md b/src/current/_includes/v1.1/start-in-docker/mac-linux-steps.md
deleted file mode 100644
index e8715c0dd48..00000000000
--- a/src/current/_includes/v1.1/start-in-docker/mac-linux-steps.md
+++ /dev/null
@@ -1,160 +0,0 @@
-## Before you begin
-
-If you have not already installed the official CockroachDB Docker image, go to [Install CockroachDB](install-cockroachdb.html) and follow the instructions under **Use Docker**.
-
-## Step 1. Create a bridge network
-
-Since you'll be running multiple Docker containers on a single host, with one CockroachDB node per container, you need to create what Docker refers to as a [bridge network](https://docs.docker.com/engine/userguide/networking/#/a-bridge-network). The bridge network will enable the containers to communicate as a single cluster while keeping them isolated from external networks.
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ docker network create -d bridge roachnet
-~~~
-
-We've used `roachnet` as the network name here and in subsequent steps, but feel free to give your network any name you like.
-
-## Step 2. Start the first node
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ docker run -d \
---name=roach1 \
---hostname=roach1 \
---net=roachnet \
--p 26257:26257 -p 8080:8080 \
--v "${PWD}/cockroach-data/roach1:/cockroach/cockroach-data" \
-{{page.release_info.docker_image}}:{{page.release_info.version}} start --insecure
-~~~
-
-This command creates a container and starts the first CockroachDB node inside it. Let's look at each part:
-
-- `docker run`: The Docker command to start a new container.
-- `-d`: This flag runs the container in the background so you can continue the next steps in the same shell.
-- `--name`: The name for the container. This is optional, but a custom name makes it significantly easier to reference the container in other commands, for example, when opening a Bash session in the container or stopping the container.
-- `--hostname`: The hostname for the container. You will use this to join other containers/nodes to the cluster.
-- `--net`: The bridge network for the container to join. See step 1 for more details.
-- `-p 26257:26257 -p 8080:8080`: These flags map the default port for inter-node and client-node communication (`26257`) and the default port for HTTP requests to the Admin UI (`8080`) from the container to the host. This enables inter-container communication and makes it possible to call up the Admin UI from a browser.
-- `-v "${PWD}/cockroach-data/roach1:/cockroach/cockroach-data"`: This flag mounts a host directory as a data volume. This means that data and logs for this node will be stored in `${PWD}/cockroach-data/roach1` on the host and will persist after the container is stopped or deleted. For more details, see Docker's Bind Mounts topic.
-- `{{page.release_info.docker_image}}:{{page.release_info.version}} start --insecure`: The CockroachDB command to [start a node](start-a-node.html) in the container in insecure mode.
-
-## Step 3. Add nodes to the cluster
-
-At this point, your cluster is live and operational. With just one node, you can already connect a SQL client and start building out your database. In real deployments, however, you'll always want 3 or more nodes to take advantage of CockroachDB's [automatic replication](demo-data-replication.html), [rebalancing](demo-automatic-rebalancing.html), and [fault tolerance](demo-fault-tolerance-and-recovery.html) capabilities.
-
-To simulate a real deployment, scale your cluster by adding two more nodes:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ docker run -d \
---name=roach2 \
---hostname=roach2 \
---net=roachnet \
--v "${PWD}/cockroach-data/roach2:/cockroach/cockroach-data" \
-{{page.release_info.docker_image}}:{{page.release_info.version}} start --insecure --join=roach1
-~~~
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ docker run -d \
---name=roach3 \
---hostname=roach3 \
---net=roachnet \
--v "${PWD}/cockroach-data/roach3:/cockroach/cockroach-data" \
-{{page.release_info.docker_image}}:{{page.release_info.version}} start --insecure --join=roach1
-~~~
-
-These commands add two more containers and start CockroachDB nodes inside them, joining them to the first node. There are only a few differences to note from step 2:
-
-- `-v`: This flag mounts a host directory as a data volume. Data and logs for these nodes will be stored in `${PWD}/cockroach-data/roach2` and `${PWD}/cockroach-data/roach3` on the host and will persist after the containers are stopped or deleted.
-- `--join`: This flag joins the new nodes to the cluster, using the first container's `hostname`. Otherwise, all [`cockroach start`](start-a-node.html) defaults are accepted. Note that since each node is in a unique container, using identical default ports won’t cause conflicts.
-
-## Step 4. Test the cluster
-
-Now that you've scaled to 3 nodes, you can use any node as a SQL gateway to the cluster. To demonstrate this, use the `docker exec` command to start the [built-in SQL shell](use-the-built-in-sql-client.html) in the first container:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ docker exec -it roach1 ./cockroach sql --insecure
-~~~
-
-~~~
-# Welcome to the cockroach SQL interface.
-# All statements must be terminated by a semicolon.
-# To exit: CTRL + D.
-~~~
-
-Run some basic [CockroachDB SQL statements](learn-cockroachdb-sql.html):
-
-{% include copy-clipboard.html %}
-~~~ sql
-> CREATE DATABASE bank;
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> CREATE TABLE bank.accounts (id INT PRIMARY KEY, balance DECIMAL);
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> INSERT INTO bank.accounts VALUES (1, 1000.50);
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SELECT * FROM bank.accounts;
-~~~
-
-~~~
-+----+---------+
-| id | balance |
-+----+---------+
-| 1 | 1000.5 |
-+----+---------+
-(1 row)
-~~~
-
-Exit the SQL shell on node 1:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> \q
-~~~
-
-Then start the SQL shell in the second container:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ docker exec -it roach2 ./cockroach sql --insecure
-~~~
-
-~~~
-# Welcome to the cockroach SQL interface.
-# All statements must be terminated by a semicolon.
-# To exit: CTRL + D.
-~~~
-
-Now run the same `SELECT` query:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SELECT * FROM bank.accounts;
-~~~
-
-~~~
-+----+---------+
-| id | balance |
-+----+---------+
-| 1 | 1000.5 |
-+----+---------+
-(1 row)
-~~~
-
-As you can see, node 1 and node 2 behaved identically as SQL gateways.
-
-When you're done, exit the SQL shell on node 2:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> \q
-~~~
diff --git a/src/current/images/v1.1/2automated-scaling-repair.png b/src/current/images/v1.1/2automated-scaling-repair.png
deleted file mode 100644
index 2402db24d75..00000000000
Binary files a/src/current/images/v1.1/2automated-scaling-repair.png and /dev/null differ
diff --git a/src/current/images/v1.1/2distributed-transactions.png b/src/current/images/v1.1/2distributed-transactions.png
deleted file mode 100644
index 52fc2d11943..00000000000
Binary files a/src/current/images/v1.1/2distributed-transactions.png and /dev/null differ
diff --git a/src/current/images/v1.1/2go-implementation.png b/src/current/images/v1.1/2go-implementation.png
deleted file mode 100644
index e5729f51cfb..00000000000
Binary files a/src/current/images/v1.1/2go-implementation.png and /dev/null differ
diff --git a/src/current/images/v1.1/2open-source.png b/src/current/images/v1.1/2open-source.png
deleted file mode 100644
index b2a936d8d29..00000000000
Binary files a/src/current/images/v1.1/2open-source.png and /dev/null differ
diff --git a/src/current/images/v1.1/2simplified-deployments.png b/src/current/images/v1.1/2simplified-deployments.png
deleted file mode 100644
index 15576d1ae5d..00000000000
Binary files a/src/current/images/v1.1/2simplified-deployments.png and /dev/null differ
diff --git a/src/current/images/v1.1/2strong-consistency.png b/src/current/images/v1.1/2strong-consistency.png
deleted file mode 100644
index 571dc01761d..00000000000
Binary files a/src/current/images/v1.1/2strong-consistency.png and /dev/null differ
diff --git a/src/current/images/v1.1/CockroachDB_Training_Wide.png b/src/current/images/v1.1/CockroachDB_Training_Wide.png
deleted file mode 100644
index 0844c2b50e0..00000000000
Binary files a/src/current/images/v1.1/CockroachDB_Training_Wide.png and /dev/null differ
diff --git a/src/current/images/v1.1/Parallel_Statement_Execution_Error_Mismatch.png b/src/current/images/v1.1/Parallel_Statement_Execution_Error_Mismatch.png
deleted file mode 100644
index f60360c9598..00000000000
Binary files a/src/current/images/v1.1/Parallel_Statement_Execution_Error_Mismatch.png and /dev/null differ
diff --git a/src/current/images/v1.1/Parallel_Statement_Hybrid_Execution.png b/src/current/images/v1.1/Parallel_Statement_Hybrid_Execution.png
deleted file mode 100644
index a4edf85dc02..00000000000
Binary files a/src/current/images/v1.1/Parallel_Statement_Hybrid_Execution.png and /dev/null differ
diff --git a/src/current/images/v1.1/Parallel_Statement_Normal_Execution.png b/src/current/images/v1.1/Parallel_Statement_Normal_Execution.png
deleted file mode 100644
index df63ab1da01..00000000000
Binary files a/src/current/images/v1.1/Parallel_Statement_Normal_Execution.png and /dev/null differ
diff --git a/src/current/images/v1.1/Sequential_Statement_Execution.png b/src/current/images/v1.1/Sequential_Statement_Execution.png
deleted file mode 100644
index 99c47c51664..00000000000
Binary files a/src/current/images/v1.1/Sequential_Statement_Execution.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui.png b/src/current/images/v1.1/admin_ui.png
deleted file mode 100644
index c5794d108a3..00000000000
Binary files a/src/current/images/v1.1/admin_ui.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_capacity.png b/src/current/images/v1.1/admin_ui_capacity.png
deleted file mode 100644
index 265ddfc0004..00000000000
Binary files a/src/current/images/v1.1/admin_ui_capacity.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_cpu_time.png b/src/current/images/v1.1/admin_ui_cpu_time.png
deleted file mode 100644
index 5f42bda546d..00000000000
Binary files a/src/current/images/v1.1/admin_ui_cpu_time.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_database_grants_view.png b/src/current/images/v1.1/admin_ui_database_grants_view.png
deleted file mode 100644
index 6ea6f8cefe5..00000000000
Binary files a/src/current/images/v1.1/admin_ui_database_grants_view.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_database_tables_view.png b/src/current/images/v1.1/admin_ui_database_tables_view.png
deleted file mode 100644
index 004b14566a7..00000000000
Binary files a/src/current/images/v1.1/admin_ui_database_tables_view.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_events.png b/src/current/images/v1.1/admin_ui_events.png
deleted file mode 100644
index 3d3a4738c78..00000000000
Binary files a/src/current/images/v1.1/admin_ui_events.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_file_descriptors.png b/src/current/images/v1.1/admin_ui_file_descriptors.png
deleted file mode 100644
index a6117216347..00000000000
Binary files a/src/current/images/v1.1/admin_ui_file_descriptors.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_hovering.gif b/src/current/images/v1.1/admin_ui_hovering.gif
deleted file mode 100644
index 1795471051f..00000000000
Binary files a/src/current/images/v1.1/admin_ui_hovering.gif and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_jobs_page.png b/src/current/images/v1.1/admin_ui_jobs_page.png
deleted file mode 100644
index 91f8089bf00..00000000000
Binary files a/src/current/images/v1.1/admin_ui_jobs_page.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_memory_usage.png b/src/current/images/v1.1/admin_ui_memory_usage.png
deleted file mode 100644
index fa72188ee79..00000000000
Binary files a/src/current/images/v1.1/admin_ui_memory_usage.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_node_count.png b/src/current/images/v1.1/admin_ui_node_count.png
deleted file mode 100644
index f8000cd8e25..00000000000
Binary files a/src/current/images/v1.1/admin_ui_node_count.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_nodes_page.png b/src/current/images/v1.1/admin_ui_nodes_page.png
deleted file mode 100644
index 61dae944906..00000000000
Binary files a/src/current/images/v1.1/admin_ui_nodes_page.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_overview.gif b/src/current/images/v1.1/admin_ui_overview.gif
deleted file mode 100644
index eb3a19536e8..00000000000
Binary files a/src/current/images/v1.1/admin_ui_overview.gif and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_ranges.png b/src/current/images/v1.1/admin_ui_ranges.png
deleted file mode 100644
index f82458ad8bc..00000000000
Binary files a/src/current/images/v1.1/admin_ui_ranges.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_replica_quiescence.png b/src/current/images/v1.1/admin_ui_replica_quiescence.png
deleted file mode 100644
index 2e2ccd05cae..00000000000
Binary files a/src/current/images/v1.1/admin_ui_replica_quiescence.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_replica_snapshots.png b/src/current/images/v1.1/admin_ui_replica_snapshots.png
deleted file mode 100644
index 56146c7f775..00000000000
Binary files a/src/current/images/v1.1/admin_ui_replica_snapshots.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_replicas.png b/src/current/images/v1.1/admin_ui_replicas.png
deleted file mode 100644
index 8ee31eed675..00000000000
Binary files a/src/current/images/v1.1/admin_ui_replicas.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_replicas_migration.png b/src/current/images/v1.1/admin_ui_replicas_migration.png
deleted file mode 100644
index 0814b120cc1..00000000000
Binary files a/src/current/images/v1.1/admin_ui_replicas_migration.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_replicas_migration2.png b/src/current/images/v1.1/admin_ui_replicas_migration2.png
deleted file mode 100644
index 4e415289175..00000000000
Binary files a/src/current/images/v1.1/admin_ui_replicas_migration2.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_replicas_migration3.png b/src/current/images/v1.1/admin_ui_replicas_migration3.png
deleted file mode 100644
index 75ede383fe3..00000000000
Binary files a/src/current/images/v1.1/admin_ui_replicas_migration3.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_replicas_per_node.png b/src/current/images/v1.1/admin_ui_replicas_per_node.png
deleted file mode 100644
index 216e425f183..00000000000
Binary files a/src/current/images/v1.1/admin_ui_replicas_per_node.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_replicas_per_store.png b/src/current/images/v1.1/admin_ui_replicas_per_store.png
deleted file mode 100644
index df820578d80..00000000000
Binary files a/src/current/images/v1.1/admin_ui_replicas_per_store.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_service_latency_99_percentile.png b/src/current/images/v1.1/admin_ui_service_latency_99_percentile.png
deleted file mode 100644
index a4e9710b652..00000000000
Binary files a/src/current/images/v1.1/admin_ui_service_latency_99_percentile.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_single_node.gif b/src/current/images/v1.1/admin_ui_single_node.gif
deleted file mode 100644
index 008916d85fb..00000000000
Binary files a/src/current/images/v1.1/admin_ui_single_node.gif and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_sql_byte_traffic.png b/src/current/images/v1.1/admin_ui_sql_byte_traffic.png
deleted file mode 100644
index 51bb87f7cad..00000000000
Binary files a/src/current/images/v1.1/admin_ui_sql_byte_traffic.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_sql_connections.png b/src/current/images/v1.1/admin_ui_sql_connections.png
deleted file mode 100644
index fce2fd470d5..00000000000
Binary files a/src/current/images/v1.1/admin_ui_sql_connections.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_sql_queries.png b/src/current/images/v1.1/admin_ui_sql_queries.png
deleted file mode 100644
index aee2c707e27..00000000000
Binary files a/src/current/images/v1.1/admin_ui_sql_queries.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_summary_panel.png b/src/current/images/v1.1/admin_ui_summary_panel.png
deleted file mode 100644
index 3c736430eb1..00000000000
Binary files a/src/current/images/v1.1/admin_ui_summary_panel.png and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_time_range.gif b/src/current/images/v1.1/admin_ui_time_range.gif
deleted file mode 100644
index 5379c6fe2a3..00000000000
Binary files a/src/current/images/v1.1/admin_ui_time_range.gif and /dev/null differ
diff --git a/src/current/images/v1.1/admin_ui_transactions.png b/src/current/images/v1.1/admin_ui_transactions.png
deleted file mode 100644
index 30abbaefa40..00000000000
Binary files a/src/current/images/v1.1/admin_ui_transactions.png and /dev/null differ
diff --git a/src/current/images/v1.1/after-decommission1.png b/src/current/images/v1.1/after-decommission1.png
deleted file mode 100644
index feb0ad77991..00000000000
Binary files a/src/current/images/v1.1/after-decommission1.png and /dev/null differ
diff --git a/src/current/images/v1.1/after-decommission2.png b/src/current/images/v1.1/after-decommission2.png
deleted file mode 100644
index 28612b52359..00000000000
Binary files a/src/current/images/v1.1/after-decommission2.png and /dev/null differ
diff --git a/src/current/images/v1.1/automated-operations1.png b/src/current/images/v1.1/automated-operations1.png
deleted file mode 100644
index c27832db2f4..00000000000
Binary files a/src/current/images/v1.1/automated-operations1.png and /dev/null differ
diff --git a/src/current/images/v1.1/before-decommission1.png b/src/current/images/v1.1/before-decommission1.png
deleted file mode 100644
index 0bccfb83c5e..00000000000
Binary files a/src/current/images/v1.1/before-decommission1.png and /dev/null differ
diff --git a/src/current/images/v1.1/before-decommission2.png b/src/current/images/v1.1/before-decommission2.png
deleted file mode 100644
index 4ca1c019c07..00000000000
Binary files a/src/current/images/v1.1/before-decommission2.png and /dev/null differ
diff --git a/src/current/images/v1.1/cloudformation_admin_ui_live_node_count.png b/src/current/images/v1.1/cloudformation_admin_ui_live_node_count.png
deleted file mode 100644
index 179575ef199..00000000000
Binary files a/src/current/images/v1.1/cloudformation_admin_ui_live_node_count.png and /dev/null differ
diff --git a/src/current/images/v1.1/cloudformation_admin_ui_replicas.png b/src/current/images/v1.1/cloudformation_admin_ui_replicas.png
deleted file mode 100644
index 3e491973103..00000000000
Binary files a/src/current/images/v1.1/cloudformation_admin_ui_replicas.png and /dev/null differ
diff --git a/src/current/images/v1.1/cloudformation_admin_ui_sql_queries.png b/src/current/images/v1.1/cloudformation_admin_ui_sql_queries.png
deleted file mode 100644
index 2b30c9ff4d7..00000000000
Binary files a/src/current/images/v1.1/cloudformation_admin_ui_sql_queries.png and /dev/null differ
diff --git a/src/current/images/v1.1/cluster-status-after-decommission1.png b/src/current/images/v1.1/cluster-status-after-decommission1.png
deleted file mode 100644
index 4757c6b94f3..00000000000
Binary files a/src/current/images/v1.1/cluster-status-after-decommission1.png and /dev/null differ
diff --git a/src/current/images/v1.1/cluster-status-after-decommission2.png b/src/current/images/v1.1/cluster-status-after-decommission2.png
deleted file mode 100644
index b2e0ae42891..00000000000
Binary files a/src/current/images/v1.1/cluster-status-after-decommission2.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-multiple1.png b/src/current/images/v1.1/decommission-multiple1.png
deleted file mode 100644
index b8a23868fbf..00000000000
Binary files a/src/current/images/v1.1/decommission-multiple1.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-multiple2.png b/src/current/images/v1.1/decommission-multiple2.png
deleted file mode 100644
index e2806f2931c..00000000000
Binary files a/src/current/images/v1.1/decommission-multiple2.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-multiple3.png b/src/current/images/v1.1/decommission-multiple3.png
deleted file mode 100644
index b671ec075b3..00000000000
Binary files a/src/current/images/v1.1/decommission-multiple3.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-multiple4.png b/src/current/images/v1.1/decommission-multiple4.png
deleted file mode 100644
index 892741327e3..00000000000
Binary files a/src/current/images/v1.1/decommission-multiple4.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-multiple5.png b/src/current/images/v1.1/decommission-multiple5.png
deleted file mode 100644
index cc3b787d751..00000000000
Binary files a/src/current/images/v1.1/decommission-multiple5.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-multiple6.png b/src/current/images/v1.1/decommission-multiple6.png
deleted file mode 100644
index 8e38c39a9de..00000000000
Binary files a/src/current/images/v1.1/decommission-multiple6.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-multiple7.png b/src/current/images/v1.1/decommission-multiple7.png
deleted file mode 100644
index 6c94f261593..00000000000
Binary files a/src/current/images/v1.1/decommission-multiple7.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-scenario1.1.png b/src/current/images/v1.1/decommission-scenario1.1.png
deleted file mode 100644
index a66389270de..00000000000
Binary files a/src/current/images/v1.1/decommission-scenario1.1.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-scenario1.2.png b/src/current/images/v1.1/decommission-scenario1.2.png
deleted file mode 100644
index 9b33855e101..00000000000
Binary files a/src/current/images/v1.1/decommission-scenario1.2.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-scenario1.3.png b/src/current/images/v1.1/decommission-scenario1.3.png
deleted file mode 100644
index 4c1175d956b..00000000000
Binary files a/src/current/images/v1.1/decommission-scenario1.3.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-scenario2.1.png b/src/current/images/v1.1/decommission-scenario2.1.png
deleted file mode 100644
index 2fa8790c556..00000000000
Binary files a/src/current/images/v1.1/decommission-scenario2.1.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-scenario2.2.png b/src/current/images/v1.1/decommission-scenario2.2.png
deleted file mode 100644
index 391b8e24c0f..00000000000
Binary files a/src/current/images/v1.1/decommission-scenario2.2.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-scenario3.1.png b/src/current/images/v1.1/decommission-scenario3.1.png
deleted file mode 100644
index db682df3d78..00000000000
Binary files a/src/current/images/v1.1/decommission-scenario3.1.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-scenario3.2.png b/src/current/images/v1.1/decommission-scenario3.2.png
deleted file mode 100644
index 3571bd0b83e..00000000000
Binary files a/src/current/images/v1.1/decommission-scenario3.2.png and /dev/null differ
diff --git a/src/current/images/v1.1/decommission-scenario3.3.png b/src/current/images/v1.1/decommission-scenario3.3.png
deleted file mode 100644
index 45f61d9bd18..00000000000
Binary files a/src/current/images/v1.1/decommission-scenario3.3.png and /dev/null differ
diff --git a/src/current/images/v1.1/follow-workload-1.png b/src/current/images/v1.1/follow-workload-1.png
deleted file mode 100644
index a58fcb2e5ed..00000000000
Binary files a/src/current/images/v1.1/follow-workload-1.png and /dev/null differ
diff --git a/src/current/images/v1.1/follow-workload-2.png b/src/current/images/v1.1/follow-workload-2.png
deleted file mode 100644
index 47d83c5d4d6..00000000000
Binary files a/src/current/images/v1.1/follow-workload-2.png and /dev/null differ
diff --git a/src/current/images/v1.1/icon_info.svg b/src/current/images/v1.1/icon_info.svg
deleted file mode 100644
index 57aac994733..00000000000
--- a/src/current/images/v1.1/icon_info.svg
+++ /dev/null
@@ -1,4 +0,0 @@
-
\ No newline at end of file
diff --git a/src/current/images/v1.1/raw-status-endpoints.png b/src/current/images/v1.1/raw-status-endpoints.png
deleted file mode 100644
index a893911fa87..00000000000
Binary files a/src/current/images/v1.1/raw-status-endpoints.png and /dev/null differ
diff --git a/src/current/images/v1.1/recovery1.png b/src/current/images/v1.1/recovery1.png
deleted file mode 100644
index daba155a6f8..00000000000
Binary files a/src/current/images/v1.1/recovery1.png and /dev/null differ
diff --git a/src/current/images/v1.1/recovery2.png b/src/current/images/v1.1/recovery2.png
deleted file mode 100644
index 411973319b5..00000000000
Binary files a/src/current/images/v1.1/recovery2.png and /dev/null differ
diff --git a/src/current/images/v1.1/recovery3.png b/src/current/images/v1.1/recovery3.png
deleted file mode 100644
index b82fd6bbd05..00000000000
Binary files a/src/current/images/v1.1/recovery3.png and /dev/null differ
diff --git a/src/current/images/v1.1/remove-dead-node1.png b/src/current/images/v1.1/remove-dead-node1.png
deleted file mode 100644
index ee34cce9e2a..00000000000
Binary files a/src/current/images/v1.1/remove-dead-node1.png and /dev/null differ
diff --git a/src/current/images/v1.1/replication1.png b/src/current/images/v1.1/replication1.png
deleted file mode 100644
index 33d309e0cc3..00000000000
Binary files a/src/current/images/v1.1/replication1.png and /dev/null differ
diff --git a/src/current/images/v1.1/replication2.png b/src/current/images/v1.1/replication2.png
deleted file mode 100644
index 3a966e9e776..00000000000
Binary files a/src/current/images/v1.1/replication2.png and /dev/null differ
diff --git a/src/current/images/v1.1/scalability1.png b/src/current/images/v1.1/scalability1.png
deleted file mode 100644
index ee06acea929..00000000000
Binary files a/src/current/images/v1.1/scalability1.png and /dev/null differ
diff --git a/src/current/images/v1.1/scalability2.png b/src/current/images/v1.1/scalability2.png
deleted file mode 100644
index 8eb8c63b03d..00000000000
Binary files a/src/current/images/v1.1/scalability2.png and /dev/null differ
diff --git a/src/current/images/v1.1/trace.png b/src/current/images/v1.1/trace.png
deleted file mode 100644
index 4f0fb98a753..00000000000
Binary files a/src/current/images/v1.1/trace.png and /dev/null differ
diff --git a/src/current/releases/v1.1.md b/src/current/releases/v1.1.md
index 8967c9ae6f8..f70cc497912 100644
--- a/src/current/releases/v1.1.md
+++ b/src/current/releases/v1.1.md
@@ -1,5 +1,5 @@
---
-title: What's New in v1.1
+title: What's New in v1.1
toc: true
toc_not_nested: true
summary: Additions and changes in CockroachDB version v1.1 since version v1.0
@@ -8,16 +8,30 @@ docs_area: releases
keywords: gin, gin index, gin indexes, inverted index, inverted indexes, accelerated index, accelerated indexes
---
-{% assign rel = site.data.releases | where_exp: "rel", "rel.major_version == page.major_version" | sort: "release_date" | reverse %}
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-{% assign vers = site.data.versions | where_exp: "vers", "vers.major_version == page.major_version" | first %}
+This release is no longer supported. For more information, see our [Release support policy]({% link releases/release-support-policy.md %}).
-{% assign today = "today" | date: "%Y-%m-%d" %}
-
-{% include releases/testing-release-notice.md major_version=vers %}
-
-{% include releases/whats-new-intro.md major_version=vers %}
-
-{% for r in rel %}
-{% include releases/{{ page.major_version }}/{{ r.release_name }}.md release=r.release_name release_date=r.release_date %}
-{% endfor %}
+To download the archived documentation for this release, see [Archived Documentation]({% link releases/archived-documentation.md %}).
\ No newline at end of file
diff --git a/src/current/v1.1/404.md b/src/current/v1.1/404.md
deleted file mode 100755
index 13a69ddde5c..00000000000
--- a/src/current/v1.1/404.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: Page Not Found
-description: "Page not found."
-sitemap: false
-search: exclude
-related_pages: none
-toc: false
----
-
-
-{%comment%}
-
-
-{%endcomment%}
\ No newline at end of file
diff --git a/src/current/v1.1/add-column.md b/src/current/v1.1/add-column.md
deleted file mode 100644
index c0207233c09..00000000000
--- a/src/current/v1.1/add-column.md
+++ /dev/null
@@ -1,131 +0,0 @@
----
-title: ADD COLUMN
-summary: Use the ADD COLUMN statement to add columns to tables.
-toc: true
----
-
-The `ADD COLUMN` [statement](sql-statements.html) is part of `ALTER TABLE` and adds columns to tables.
-
-
-## Synopsis
-
-{% include {{ page.version.version }}/sql/diagrams/add_column.html %}
-
-## Required Privileges
-
-The user must have the `CREATE` [privilege](privileges.html) on the table.
-
-## Parameters
-
-| Parameter | Description |
-|-----------|-------------|
-| `table_name` | The name of the table to which you want to add the column. |
-| `name` | The name of the column you want to add. The column name must follow these [identifier rules](keywords-and-identifiers.html#identifiers) and must be unique within the table but can have the same name as indexes or constraints. |
-| `typename` | The [data type](data-types.html) of the new column. |
-| `col_qualification` | A list of column definitions, which may include [column-level constraints](constraints.html), [collation](collate.html), or [column family assignments](column-families.html).no references
- -
referenced by: -
-
-
- stmt_block -
- -
referenced by: -
-
-
- stmt_list -
- -
referenced by: -
-
-
- explainable_stmt -
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- explainable_stmt -
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- explainable_stmt -
- stmt -
- -
referenced by: -
-
-
- explainable_stmt -
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- alter_split_index_stmt -
- alter_split_stmt -
- create_table_as_stmt -
- create_view_stmt -
- insert_rest -
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- stmt -
- -
referenced by: -
-
-
- alter_stmt -
- -
referenced by: -
-
-
- alter_stmt -
- -
referenced by: -
-
-
- alter_stmt -
- -
referenced by: -
-
-
- alter_stmt -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- backup_stmt -
- from_clause -
- restore_stmt -
- -
referenced by: -
-
-
- backup_stmt -
- -
referenced by: -
-
-
- backup_stmt -
- import_stmt -
- restore_stmt -
- -
referenced by: -
-
-
- cancel_stmt -
- -
referenced by: -
-
-
- cancel_stmt -
- -
referenced by: -
-
-
- alter_rename_table_stmt -
- alter_rename_view_stmt -
- alter_scatter_stmt -
- alter_split_stmt -
- col_qualification_elem -
- constraint_elem -
- copy_from_stmt -
- create_index_stmt -
- d_expr -
- insert_target -
- opt_interleave -
- qualified_name_list -
- relation_expr -
- single_set_clause -
- sortby -
- table_name_with_index -
- table_ref -
- -
referenced by: -
-- -
referenced by: -
-
-
- create_stmt -
- -
referenced by: -
-
-
- create_stmt -
- -
referenced by: -
-
-
- create_stmt -
- -
referenced by: -
-
-
- create_stmt -
- -
referenced by: -
-
-
- create_stmt -
- -
referenced by: -
-
-
- create_stmt -
- -
referenced by: -
-
-
- alias_clause -
- alter_rename_database_stmt -
- alter_rename_index_stmt -
- alter_rename_table_stmt -
- alter_table_cmd -
- any_name -
- col_qualification -
- column_def -
- create_database_stmt -
- create_index_stmt -
- create_user_stmt -
- deallocate_stmt -
- drop_database_stmt -
- execute_stmt -
- func_name -
- grantee_list -
- index_elem -
- insert_target -
- kv_option -
- name_list -
- opt_existing_window_name -
- opt_name -
- opt_name_parens -
- over_clause -
- prepare_stmt -
- qualified_name -
- relation_expr_opt_alias -
- savepoint_name -
- savepoint_stmt -
- show_tables_stmt -
- table_constraint -
- table_pattern -
- window_definition -
- -
referenced by: -
-
-
- delete_stmt -
- update_stmt -
- -
referenced by: -
-- -
referenced by: -
-
-
- delete_stmt -
- -
referenced by: -
-
-
- delete_stmt -
- insert_stmt -
- update_stmt -
- upsert_stmt -
- -
referenced by: -
-
-
- drop_stmt -
- -
referenced by: -
-
-
- drop_stmt -
- -
referenced by: -
-
-
- drop_stmt -
- -
referenced by: -
-
-
- drop_stmt -
- -
referenced by: -
-
-
- drop_stmt -
- -
referenced by: -
-
-
- execute_stmt -
- -
referenced by: -
-
-
- explain_stmt -
- show_trace_stmt -
- table_ref -
- -
referenced by: -
-
-
- explain_stmt -
- -
referenced by: -
-
-
- grant_stmt -
- revoke_stmt -
- -
referenced by: -
-
-
- for_grantee_clause -
- grant_stmt -
- revoke_stmt -
- -
referenced by: -
-
-
- insert_stmt -
- upsert_stmt -
- -
referenced by: -
-
-
- insert_stmt -
- upsert_stmt -
- -
referenced by: -
-
-
- insert_stmt -
- -
referenced by: -
-
-
- create_table_as_stmt -
- create_table_stmt -
- create_view_stmt -
- import_stmt -
- show_csettings_stmt -
- table_name_list -
- var_name -
- -
referenced by: -
-
-
- import_stmt -
- opt_incremental -
- restore_stmt -
- -
referenced by: -
-- -
referenced by: -
-
-
- a_expr -
- alter_column_default -
- array_subscript -
- cancel_job_stmt -
- cancel_query_stmt -
- case_arg -
- case_default -
- col_qualification_elem -
- constraint_elem -
- ctext_expr -
- d_expr -
- expr_list -
- extract_list -
- filter_clause -
- func_expr_common_subexpr -
- having_clause -
- implicit_row -
- join_qual -
- offset_clause -
- opt_select_fetch_first_value -
- opt_slice_bound -
- overlay_list -
- overlay_placing -
- pause_stmt -
- resume_stmt -
- select_limit_value -
- sortby -
- substr_for -
- substr_from -
- substr_list -
- target_elem -
- trim_list -
- when_clause -
- where_clause -
- -
referenced by: -
-
-
- prepare_stmt -
- -
referenced by: -
-
-
- explainable_stmt -
- prepare_stmt -
- -
referenced by: -
-- -
referenced by: -
-
-
- c_expr -
- d_expr -
- in_expr -
- multiple_set_clause -
- select_clause -
- select_stmt -
- select_with_parens -
- table_ref -
- -
referenced by: -
-
-
- opt_to_savepoint -
- release_stmt -
- -
referenced by: -
-
-
- reset_stmt -
- -
referenced by: -
-
-
- reset_stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- set_stmt -
- -
referenced by: -
-
-
- preparable_stmt -
- set_stmt -
- -
referenced by: -
-
-
- set_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- show_stmt -
- -
referenced by: -
-
-
- transaction_stmt -
- -
referenced by: -
-
-
- transaction_stmt -
- -
referenced by: -
-
-
- transaction_stmt -
- -
referenced by: -
-
-
- truncate_stmt -
- -
referenced by: -
-
-
- truncate_stmt -
- -
referenced by: -
-
-
- alter_table_cmd -
- drop_database_stmt -
- drop_index_stmt -
- drop_table_stmt -
- drop_view_stmt -
- truncate_stmt -
- -
referenced by: -
-
-
- on_conflict -
- update_stmt -
- -
referenced by: -
-
-
- alter_table_stmt -
- -
referenced by: -
-
-
- alter_table_stmt -
- -
referenced by: -
-
-
- alter_table_stmt -
- -
referenced by: -
-
-
- alter_table_stmt -
- -
referenced by: -
-
-
- alter_index_stmt -
- -
referenced by: -
-
-
- alter_index_stmt -
- -
referenced by: -
-
-
- alter_index_stmt -
- -
referenced by: -
-
-
- alter_view_stmt -
- -
referenced by: -
-- -
referenced by: -
-
-
- targets -
- -
referenced by: -
-
-
- alias_clause -
- constraint_elem -
- drop_user_stmt -
- family_def -
- join_qual -
- opt_column_list -
- opt_conf_expr -
- opt_interleave -
- opt_storing -
- targets -
- -
referenced by: -
-
-
- opt_encoding_clause -
- opt_lc_collate_clause -
- opt_lc_ctype_clause -
- opt_template_clause -
- string_or_placeholder -
- -
referenced by: -
-
-
- d_expr -
- opt_as_of_clause -
- -
referenced by: -
-
-
- opt_with_options -
- -
referenced by: -
-
-
- func_name -
- qualified_name -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- create_user_stmt -
- -
referenced by: -
-- -
referenced by: -
-
-
- name -
- non_reserved_word -
- unrestricted_name -
- -
referenced by: -
-
-
- alter_onetable_stmt -
- alter_rename_table_stmt -
- alter_rename_view_stmt -
- relation_expr_list -
- relation_expr_opt_alias -
- table_ref -
- -
referenced by: -
-
-
- opt_limit_clause -
- select_limit -
- -
referenced by: -
-- -
referenced by: -
-
-
- drop_index_stmt -
- -
referenced by: -
-- -
referenced by: -
-
-
- alter_scatter_index_stmt -
- alter_scatter_stmt -
- array_expr -
- execute_param_clause -
- explicit_row -
- extract_list -
- func_application -
- func_expr_common_subexpr -
- group_clause -
- implicit_row -
- in_expr -
- opt_partition_clause -
- overlay_list -
- substr_list -
- table_ref -
- trim_list -
- -
referenced by: -
-- -
referenced by: -
-
-
- privileges -
- -
referenced by: -
-
-
- on_conflict -
- -
referenced by: -
-
-
- any_name -
- -
referenced by: -
-
-
- table_elem_list -
- -
referenced by: -
-
-
- a_expr -
- b_expr -
- offset_clause -
- -
referenced by: -
-
-
- a_expr -
- b_expr -
- func_expr_common_subexpr -
- -
referenced by: -
-
-
- a_expr -
- b_expr -
- cast_target -
- column_def -
- func_expr_common_subexpr -
- type_list -
- -
referenced by: -
-
-
- a_expr -
- attrs -
- col_qualification -
- index_hints_param -
- name_indirection -
- opt_index_hints -
- sortby -
- table_name_with_index -
- target_elem -
- -
referenced by: -
-
-
- a_expr -
- b_expr -
- prep_type_clause -
- -
referenced by: -
-
-
- a_expr -
- -
referenced by: -
-
-
- a_expr -
- b_expr -
- col_qualification_elem -
- position_list -
- -
referenced by: -
-
-
- a_expr -
- -
referenced by: -
-
-
- a_expr -
- -
referenced by: -
-
-
- a_expr -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- select_no_parens -
- -
referenced by: -
-- -
referenced by: -
-
-
- generic_set -
- reset_csetting_stmt -
- set_csetting_stmt -
- show_columns_stmt -
- show_constraints_stmt -
- show_create_table_stmt -
- show_create_view_stmt -
- show_indexes_stmt -
- -
referenced by: -
-
-
- set_session_stmt -
- -
referenced by: -
-- -
referenced by: -
-
-
- set_csetting_stmt -
- var_list -
- -
referenced by: -
-- -
referenced by: -
-
-
- show_grants_stmt -
- -
referenced by: -
-
-
- show_grants_stmt -
- -
referenced by: -
-
-
- begin_stmt -
- commit_stmt -
- -
referenced by: -
-
-
- begin_stmt -
- -
referenced by: -
-
-
- rollback_stmt -
- -
referenced by: -
-
-
- set_clause_list -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- alter_rename_index_stmt -
- alter_scatter_index_stmt -
- alter_split_index_stmt -
- table_name_with_index_list -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- a_expr_const -
- -
referenced by: -
-
-
- a_expr_const -
- -
referenced by: -
-
-
- kv_option_list -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- index_params -
- -
referenced by: -
-
-
- opt_storing -
- -
referenced by: -
-
-
- limit_clause -
- -
referenced by: -
-
-
- limit_clause -
- -
referenced by: -
-
-
- limit_clause -
- -
referenced by: -
-
-
- limit_clause -
- offset_clause -
- -
referenced by: -
-
-
- target_list -
- -
referenced by: -
-
-
- privilege_list -
- -
referenced by: -
-
-
- alter_table_cmd -
- table_elem -
- -
referenced by: -
-
-
- table_elem -
- -
referenced by: -
-
-
- table_elem -
- -
referenced by: -
-
-
- alter_table_cmd -
- table_elem -
- -
referenced by: -
-
-
- c_expr -
- -
referenced by: -
-
-
- c_expr -
- -
referenced by: -
-
-
- cast_target -
- -
referenced by: -
-
-
- typename -
- -
referenced by: -
-
-
- typename -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- subquery_op -
- -
referenced by: -
-
-
- d_expr -
- -
referenced by: -
-
-
- array_expr_list -
- d_expr -
- -
referenced by: -
-
-
- d_expr -
- -
referenced by: -
-
-
- d_expr -
- -
referenced by: -
-
-
- simple_select -
- -
referenced by: -
-
-
- simple_select -
- -
referenced by: -
-
-
- simple_select -
- -
referenced by: -
-
-
- simple_select -
- -
referenced by: -
-
-
- sort_clause -
- -
referenced by: -
-
-
- select_limit -
- -
referenced by: -
-
-
- set_rest_more -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- set_clause -
- -
referenced by: -
-
-
- set_clause -
- -
referenced by: -
-
-
- alter_table_cmds -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- const_typename -
- -
referenced by: -
-
-
- const_typename -
- -
referenced by: -
-- -
referenced by: -
-
-
- interval -
- simple_typename -
- -
referenced by: -
-
-
- index_elem -
- sortby -
- -
referenced by: -
-- -
referenced by: -
-
-
- column_def -
- -
referenced by: -
-
-
- table_constraint -
- -
referenced by: -
-
-
- array_subscripts -
- -
referenced by: -
-
-
- case_expr -
- -
referenced by: -
-
-
- case_expr -
- -
referenced by: -
-
-
- case_expr -
- -
referenced by: -
-
-
- simple_typename -
- -
referenced by: -
-
-
- simple_typename -
- -
referenced by: -
-
-
- func_expr -
- -
referenced by: -
-
-
- func_expr -
- -
referenced by: -
-
-
- func_expr -
- -
referenced by: -
-
-
- func_expr -
- -
referenced by: -
-
-
- array_expr -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- from_list -
- joined_table -
- table_clause -
- -
referenced by: -
-
-
- set_operation -
- -
referenced by: -
-
-
- sortby_list -
- -
referenced by: -
-
-
- generic_set -
- -
referenced by: -
-
-
- transaction_mode -
- -
referenced by: -
-
-
- transaction_mode -
- -
referenced by: -
-
-
- alter_table_cmd -
- -
referenced by: -
-
-
- alter_table_cmd -
- -
referenced by: -
-
-
- numeric -
- -
referenced by: -
-
-
- numeric -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- character -
- const_character -
- -
referenced by: -
-
-
- character -
- const_character -
- -
referenced by: -
-
-
- col_qual_list -
- -
referenced by: -
-- -
referenced by: -
-
-
- array_subscript -
- -
referenced by: -
-
-
- when_clause_list -
- -
referenced by: -
-
-
- func_application -
- -
referenced by: -
-
-
- over_clause -
- window_definition -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- from_clause -
- -
referenced by: -
-
-
- window_clause -
- -
referenced by: -
-
-
- ctext_row -
- -
referenced by: -
-
-
- table_ref -
- -
referenced by: -
-
-
- table_ref -
- -
referenced by: -
-
-
- table_ref -
- -
referenced by: -
-
-
- joined_table -
- table_ref -
- -
referenced by: -
-
-
- opt_alias_clause -
- table_ref -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- key_actions -
- -
referenced by: -
-
-
- key_actions -
- -
referenced by: -
-
-
- func_name -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- extract_list -
- -
referenced by: -
-
-
- overlay_list -
- -
referenced by: -
-
-
- overlay_list -
- substr_list -
- -
referenced by: -
-
-
- overlay_list -
- substr_list -
- -
referenced by: -
-- -
referenced by: -
-
-
- opt_index_hints -
- -
referenced by: -
-
-
- joined_table -
- -
referenced by: -
-
-
- joined_table -
- -
referenced by: -
-- -
referenced by: -
-- -
referenced by: -
-
-
- join_type -
generated by Railroad Diagram Generator
Note that it is not possible to add a column with the [Foreign Key](foreign-key.html) constraint. As a workaround, you can add the column without the constraint, then use [`CREATE INDEX`](create-index.html) to index the column, and then use [`ADD CONSTRAINT`](add-constraint.html) to add the Foreign Key constraint to the column. | - -## Viewing Schema Changes New in v1.1 -{% include {{ page.version.version }}/misc/schema-change-view-job.md %} - -## Examples - -### Add a Single Column - -~~~ sql -> ALTER TABLE accounts ADD COLUMN names STRING; -~~~ - -~~~ sql -> SHOW COLUMNS FROM accounts; -~~~ - -~~~ -+-----------+-------------------+-------+---------+-----------+ -| Field | Type | Null | Default | Indices | -+-----------+-------------------+-------+---------+-----------+ -| id | INT | false | NULL | {primary} | -| balance | DECIMAL | true | NULL | {} | -| names | STRING | true | NULL | {} | -+-----------+-------------------+-------+---------+-----------+ -~~~ - -### Add Multiple Columns - -~~~ sql -> ALTER TABLE accounts ADD COLUMN location STRING, ADD COLUMN amount DECIMAL; -~~~ - -~~~ sql -> SHOW COLUMNS FROM accounts; -~~~ - -~~~ -+-----------+-------------------+-------+---------+-----------+ -| Field | Type | Null | Default | Indices | -+-----------+-------------------+-------+---------+-----------+ -| id | INT | false | NULL | {primary} | -| balance | DECIMAL | true | NULL | {} | -| names | STRING | true | NULL | {} | -| location | STRING | true | NULL | {} | -| amount | DECIMAL | true | NULL | {} | -+-----------+-------------------+-------+---------+-----------+ - -~~~ - -### Add a Non-Null Column with a Default Value - -~~~ sql -> ALTER TABLE accounts ADD COLUMN interest DECIMAL NOT NULL DEFAULT (DECIMAL '1.3'); -~~~ - -~~~ sql -> SHOW COLUMNS FROM accounts; -~~~ -~~~ -+-----------+-------------------+-------+---------------------------+-----------+ -| Field | Type | Null | Default | Indices | -+-----------+-------------------+-------+---------------------------+-----------+ -| id | INT | false | NULL | {primary} | -| balance | DECIMAL | true | NULL | {} | -| names | STRING | true | NULL | {} | -| location | STRING | true | NULL | {} | -| amount | DECIMAL | true | NULL | {} | -| interest | DECIMAL | false | ('1.3':::STRING::DECIMAL) | {} | -+-----------+-------------------+-------+---------------------------+-----------+ -~~~ - -### Add a Non-Null Column with Unique Values - -~~~ sql -> ALTER TABLE accounts ADD COLUMN cust_number DECIMAL UNIQUE NOT NULL; -~~~ - -### Add a Column with Collation - -~~~ sql -> ALTER TABLE accounts ADD COLUMN more_names STRING COLLATE en; -~~~ - -### Add a Column and Assign it to a Column Family - -#### Add a Column and Assign it to a New Column Family -~~~ sql -> ALTER TABLE accounts ADD COLUMN location1 STRING CREATE FAMILY new_family; -~~~ - -#### Add a Column and Assign it to an Existing Column Family -~~~ sql -> ALTER TABLE accounts ADD COLUMN location2 STRING FAMILY existing_family; -~~~ - -#### Add a Column and Create a New Column Family if Column Family Does Not Exist -~~~ sql -> ALTER TABLE accounts ADD COLUMN new_name STRING CREATE IF NOT EXISTS FAMILY f1; -~~~ - - -## See Also -- [`ALTER TABLE`](alter-table.html) -- [Column-level Constraints](constraints.html) -- [Collation](collate.html) -- [Column Families](column-families.html) diff --git a/src/current/v1.1/add-constraint.md b/src/current/v1.1/add-constraint.md deleted file mode 100644 index df5fe0ef63e..00000000000 --- a/src/current/v1.1/add-constraint.md +++ /dev/null @@ -1,123 +0,0 @@ ---- -title: ADD CONSTRAINT -summary: Use the ADD CONSTRAINT statement to add constraints to columns. -toc: true ---- - -The `ADD CONSTRAINT` [statement](sql-statements.html) is part of `ALTER TABLE` and can add the following [constraints](constraints.html) to columns: - -- [Check](check.html) -- [Foreign Keys](foreign-key.html) -- [Unique](unique.html) - -{{site.data.alerts.callout_info}} -The Primary Key and Not Null constraints can only be applied through
CREATE TABLE. The Default constraint is managed through ALTER COLUMN.{{site.data.alerts.end}}
-
-
-## Synopsis
-
-{% include {{ page.version.version }}/sql/diagrams/add_constraint.html %}
-
-## Required Privileges
-
-The user must have the `CREATE` [privilege](privileges.html) on the table.
-
-## Parameters
-
-| Parameter | Description |
-|-----------|-------------|
-| `table_name` | The name of the table containing the column you want to constrain. |
-| `name` | The name of the constraint, which must be unique to its table and follow these [identifier rules](keywords-and-identifiers.html#identifiers). |
-| `constraint_elem` | The [Check](check.html), [Foreign Keys](foreign-key.html), [Unique](unique.html) constraint you want to add. Adding/changing a Default constraint is done through [`ALTER COLUMN`](alter-column.html).
Adding/changing the table's Primary Key is not supported through `ALTER TABLE`; it can only be specified during [table creation](create-table.html#create-a-table-primary-key-defined). | - -## Viewing Schema Changes New in v1.1 - -{% include {{ page.version.version }}/misc/schema-change-view-job.md %} - -## Examples - -### Add the Unique Constraint - -Adding the [Unique constraint](unique.html) requires that all of a column's values be distinct from one another (except for *NULL* values). - -~~~ sql -> ALTER TABLE orders ADD CONSTRAINT id_customer_unique UNIQUE (id, customer); -~~~ - -### Add the Check Constraint - -Adding the [Check constraint](check.html) requires that all of a column's values evaluate to `TRUE` for a Boolean expression. - -~~~ sql -> ALTER TABLE orders ADD CONSTRAINT total_0_check CHECK (total > 0); -~~~ - -### Add the Foreign Key Constraint - -Before you can add the [Foreign Key](foreign-key.html) constraint to columns, the columns must already be indexed. If they are not already indexed, use [`CREATE INDEX`](create-index.html) to index them and only then use the `ADD CONSTRAINT` statement to add the Foreign Key constraint to the columns. - -For example, let's say you have two simple tables, `orders` and `customers`: - -~~~ sql -> SHOW CREATE TABLE customers; -~~~ - -~~~ -+-----------+-------------------------------------------------+ -| Table | CreateTable | -+-----------+-------------------------------------------------+ -| customers | CREATE TABLE customers ( | -| | id INT NOT NULL, | -| | "name" STRING NOT NULL, | -| | address STRING NULL, | -| | CONSTRAINT "primary" PRIMARY KEY (id ASC), | -| | FAMILY "primary" (id, "name", address) | -| | ) | -+-----------+-------------------------------------------------+ -(1 row) -~~~ - -~~~ sql -> SHOW CREATE TABLE orders; -~~~ - -~~~ -+--------+-------------------------------------------------------------------------------------------------------------+ -| Table | CreateTable | -+--------+-------------------------------------------------------------------------------------------------------------+ -| orders | CREATE TABLE orders ( | -| | id INT NOT NULL, | -| | customer_id INT NULL, | -| | status STRING NOT NULL, | -| | CONSTRAINT "primary" PRIMARY KEY (id ASC), | -| | FAMILY "primary" (id, customer_id, status), | -| | CONSTRAINT check_status CHECK (status IN ('open':::STRING, 'complete':::STRING, 'cancelled':::STRING)) | -| | ) | -+--------+-------------------------------------------------------------------------------------------------------------+ -(1 row) -~~~ - -To ensure that each value in the `orders.customer_id` column matches a unique value in the `customers.id` column, you want to add the Foreign Key constraint to `orders.customer_id`. So you first create an index on `orders.customer_id`: - -~~~ sql -> CREATE INDEX ON orders (customer_id); -~~~ - -Then you add the Foreign Key constraint: - -~~~ sql -> ALTER TABLE orders ADD CONSTRAINT customer_fk FOREIGN KEY (customer_id) REFERENCES customers (id); -~~~ - -If you had tried to add the constraint before indexing the column, you would have received an error: - -~~~ -pq: foreign key requires an existing index on columns ("customer_id") -~~~ - -## See Also - -- [Constraints](constraints.html) -- [`ALTER COLUMN`](alter-column.html) -- [`CREATE TABLE`](create-table.html) -- [`ALTER TABLE`](alter-table.html) diff --git a/src/current/v1.1/admin-ui-access-and-navigate.md b/src/current/v1.1/admin-ui-access-and-navigate.md deleted file mode 100644 index 3742e7c0960..00000000000 --- a/src/current/v1.1/admin-ui-access-and-navigate.md +++ /dev/null @@ -1,128 +0,0 @@ ---- -title: Access and Navigate the CockroachDB Admin UI -summary: Learn how to access and navigate the Admin UI. -toc: true ---- - - -## Access the Admin UI - -You can access the Admin UI from any node in the cluster. - -By default, you can access it via HTTP on port `8080` of the hostname or IP address you configured using the `--host` flag while [starting the node](start-a-node.html#general). For example, `http://
-
-### Time Series Graphs
-
-The Admin UI displays time series graphs of key metrics. Time series graphs are useful to visualize and monitor data trends. You can hover over each graph to see actual point-in-time values.
-
-
-
-#### Change time range
-
-You can change the time range by clicking on the time window.
-
-
-{{site.data.alerts.callout_info}}The Admin UI shows time in UTC, even if you set a different time zone for your cluster. {{site.data.alerts.end}}
-
-#### View metrics for a single node
-
-By default, the time series panel displays the metrics for the entire cluster. To view the metrics for an individual node, select the node from the **Graph** drop-down list.
-
-
-### Summary Panel
-
-
-The **Summary** panel provides the following metrics:
-
-Metric | Description
---------|----
-Total Nodes | The total number of nodes in the cluster. Decommissioned nodes are not included in the Total Nodes count. You can further drill down into the nodes details by clicking on [**View nodes list**](#nodes-list). -Dead Nodes | The number of [dead nodes](admin-ui-access-and-navigate.html#dead-nodes) in the cluster. -Capacity Used | The storage capacity used as a percentage of total storage capacity 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 number of SQL queries executed per second. -P50 Latency | The 50th percentile of service latency. Service latency is calculated as the time between when the cluster receives a query and finishes executing the query. This time does not include returning results to the client. -P99 Latency | The 99th percentile of service latency. - -{{site.data.alerts.callout_info}} -{% include v1.1/misc/available-capacity-metric.md %} -{{site.data.alerts.end}} - -### Nodes List - -To see basic details about the nodes in your cluster, click **View nodes list** in the **Summary** panel. -
-
-#### Live Nodes
-Live nodes are nodes that are online and responding. They are marked with a green dot. If a node is removed or dies, the dot turns yellow to indicate that it is not responding. If the node remains unresponsive for a certain amount of time (5 minutes by default), the node turns red and is moved to the [**Dead Nodes**](#dead-nodes) section, indicating that it is no longer expected to come back.
-
-The following details are shown for each live node:
-
-Column | Description
--------|------------
-ID | The ID of the node.
-Address | The address of the node. You can click on the address to view further details about the node.
-Uptime | How long the node has been running.
-Bytes | The used capacity for the node.
-Replicas | The number of replicas on the node.
-Mem Usage | The memory usage for the node.
-Version | The build tag of the CockroachDB version installed on the node.
-Logs | Click **Logs** to see the logs for the node.
-
-#### Dead Nodes
-
-Nodes are considered dead once they have not responded for a certain amount of time (5 minutes by default). At this point, the automated repair process starts, wherein CockroachDB automatically rebalances replicas from the dead node, using the unaffected replicas as sources. See [Stop a Node](stop-a-node.html#how-it-works) for more information.
-
-The following details are shown for each dead node:
-
-Column | Description
--------|------------
-ID | The ID of the node.
-Address | The address of the node. You can click on the address to view further details about the node.
-Down Since | How long the node has been down.
-
-#### Decommissioned Nodes
-
-New in v1.1: Nodes that have been decommissioned for permanent removal from the cluster are listed in the **Decommissioned Nodes** table.
-
-
-
-When you decommission a node, CockroachDB lets the node finish in-flight requests, rejects any new requests, and transfers all range replicas and range leases off the node so that it can be safely shut down. See [Remove Nodes](remove-nodes.html) for more information.
-
-### Events Panel
-
-
-
-The **Events** panel lists the 10 most recent events logged for the all nodes across the cluster. To see the list of 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
diff --git a/src/current/v1.1/admin-ui-databases-page.md b/src/current/v1.1/admin-ui-databases-page.md
deleted file mode 100644
index b3de8ba3fa8..00000000000
--- a/src/current/v1.1/admin-ui-databases-page.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Database Page
-toc: true
----
-
-The **Databases** page of the Admin UI provides details of the databases configured, the tables in each database, and the grants assigned to each user.
-
-
-## Tables View
-
-The **Tables** view shows details of the system table as well as the tables in your databases. To view these details, [access the Admin UI](admin-ui-access-and-navigate.html#access-the-admin-ui) and then select **Databases** from the left-hand navigation bar.
-
-
-
-The following details are displayed for each table:
-
-Metric | Description
---------|----
-Table Name | The name of the table.
-Size | The size of the table in bytes.
-Ranges | The number of ranges in the table.
-\# of Columns | The number of columns in the table.
-\# of Indices | The number of indices for the table.
-
-## Grants View
-
-The **Grants** view shows the [privileges](privileges.html) granted to users for each database. To view these details, [access the Admin UI](admin-ui-access-and-navigate.html#access-the-admin-ui) and then select **Databases** from the left-hand navigation bar, select **Databases** from the left-hand navigation bar, and then select **Grants** from the **View** menu.
-
-For more details about grants and privileges, see [Grants](grant.html).
-
-
diff --git a/src/current/v1.1/admin-ui-jobs-page.md b/src/current/v1.1/admin-ui-jobs-page.md
deleted file mode 100644
index 6d99be0debd..00000000000
--- a/src/current/v1.1/admin-ui-jobs-page.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: Jobs Page
-toc: true
----
-
-New in v1.1: The **Jobs** page of the Admin UI provides details about the backup/restore jobs as well as schema changes performed across all nodes in the cluster. To view these details, [access the Admin UI](admin-ui-access-and-navigate.html#access-the-admin-ui) and then click **Jobs** in the left-hand navigation bar.
-
-
-## Job Details
-
-The **Jobs** table displays the user, description, creation time, and status of each backup and restore job, as well as schema changes performed across all nodes in the cluster.
-
-
-
-## Filter Results
-
-You can filter the results based on the status of the jobs or the type of jobs (backups, restores, or schema changes). You can also choose to view either the latest 50 jobs or all the jobs across all nodes.
-
-Filter By | Description
-----------|------------
-Job Status | From the **Status** menu, select the required status filter.
-Job Type | From the **Type** menu, select **Backups**, **Restores**, **Imports**, or **Schema Changes**.
-Jobs Shown | From the **Show** menu, select **First 50** or **All**.
diff --git a/src/current/v1.1/admin-ui-overview-dashboard.md b/src/current/v1.1/admin-ui-overview-dashboard.md
deleted file mode 100644
index 484d605db96..00000000000
--- a/src/current/v1.1/admin-ui-overview-dashboard.md
+++ /dev/null
@@ -1,62 +0,0 @@
----
-title: Overview Dashboard
-summary: The Overview dashboard lets you monitor important SQL performance, replication, and storage metrics.
-toc: true
----
-
-On [accessing the CockroachDB Admin UI](admin-ui-access-and-navigate.html#access-the-admin-ui), the **Overview** is shown by default. This dashboard lets you monitor important SQL performance, replication, and storage metrics.
-
-
-The **Overview** dashboard displays the following time series graphs:
-
-## SQL Queries
-
-
-
-- In the node view, the SQL Queries graph shows the current moving average, over the last 10 seconds, of the number of `SELECT`/`INSERT`/`UPDATE`/`DELETE` queries per second issued by SQL clients on the node.
-
-- In the cluster view, the graph shows the sum of the per-node averages, that is, an aggregate estimation of the current query load over the cluster, assuming the last 10 seconds of activity per node are representative of this load.
-
-## Service Latency: SQL, 99th percentile
-
-
-
-Service latency is calculated as the time between when the cluster receives a query and finishes executing the query. This time does not include returning results to the client.
-
-- In the node view, the graph shows the 99th [percentile](https://en.wikipedia.org/wiki/Percentile#The_normal_distribution_and_percentiles) of service latency for the node.
-
-- In the cluster view, the graph shows the 99th [percentile](https://en.wikipedia.org/wiki/Percentile#The_normal_distribution_and_percentiles) of service latency across all nodes in the cluster.
-
-## Replicas per Node
-
-
-
-Ranges are subsets of your data, which are replicated to ensure survivability. Ranges are replicated to a configurable number of CockroachDB nodes.
-
-- In the node view, the graph shows the number of range replicas on the selected node.
-
-- In the cluster view, the graph shows the number of range replicas on each node in the cluster.
-
-For details about how to control the number and location of replicas, see [Configure Replication Zones](configure-replication-zones.html).
-
-## Capacity
-
-
-
-You can monitor the **Capacity** graph to determine when additional storage is needed.
-
-- In the node view, the graph shows the maximum allocated capacity, available storage capacity, and capacity used by CockroachDB for the selected node.
-
-- In the cluster view, the graph shows the maximum allocated capacity, available storage capacity, and capacity used by CockroachDB across all nodes in the cluster.
-
-On hovering over the graph, the values for the following metrics are displayed:
-
-Metric | Description
---------|----
-Capacity | The maximum storage capacity allocated to CockroachDB. You can configure the maximum allocated storage capacity for CockroachDB using the --store flag. For more information, see [Start a Node](start-a-node.html#store).
-Available | The free storage capacity available to CockroachDB.
-Used | Disk space used by the data in the CockroachDB store. Note that this value is less than (Capacity - Available) because Capacity and Available metrics consider the entire disk and all applications on the disk including CockroachDB, whereas Used metric tracks only the store's disk usage.
-
-{{site.data.alerts.callout_info}}
-{% include v1.1/misc/available-capacity-metric.md %}
-{{site.data.alerts.end}}
diff --git a/src/current/v1.1/admin-ui-overview.md b/src/current/v1.1/admin-ui-overview.md
deleted file mode 100644
index db1bd3e5224..00000000000
--- a/src/current/v1.1/admin-ui-overview.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Admin UI Overview
-summary: Use the Admin UI to monitor and optimize cluster performance.
-toc: false
-key: explore-the-admin-ui.html
----
-
-The CockroachDB Admin UI provides details about your cluster and database configuration, and helps you optimize cluster performance by monitoring the following areas:
-
-Area | Description
---------|----
-[Cluster Health](admin-ui-access-and-navigate.html#summary-panel) | View essential metrics about the cluster's health, such as the number of live, dead, and suspect nodes, the number of unavailable ranges, and the queries per second and service latency across the cluster.
-[Overview Metrics](admin-ui-overview-dashboard.html) | View important SQL performance, replication, and storage metrics.
-[Runtime Metrics](admin-ui-runtime-dashboard.html) | View metrics about node count, CPU time, and memory usage.
-[SQL Performance](admin-ui-sql-dashboard.html) | View metrics about SQL connections, byte traffic, queries, transactions, and service latency.
-[Storage Utilization](admin-ui-storage-dashboard.html) | View metrics about storage capacity and file descriptors.
-[Replication Details](admin-ui-replication-dashboard.html) | View metrics about how data is replicated across the cluster, such as range status, replicas per store, and replica quiescence.
-[Nodes Details](admin-ui-access-and-navigate.html#summary-panel) | View details of live, dead, and decommissioned nodes.
-[Events](admin-ui-access-and-navigate.html#events-panel) | View a list of recent cluster events.
-[Database Details](admin-ui-databases-page.html) | View details about the system and user databases in the cluster.
-[Jobs Details](admin-ui-jobs-page.html) | View details of the jobs running in the cluster.
-
-The Admin UI also provides details about the way data is **Distributed**, the state of specific **Queues**, and metrics for **Slow Queries**, but these details are largely internal and intended for use by CockroachDB developers.
-
-{{site.data.alerts.callout_info}}By default, the Admin UI shares anonymous usage details with Cockroach Labs. For information about the details shared and how to opt-out of reporting, see Diagnostics Reporting.{{site.data.alerts.end}}
diff --git a/src/current/v1.1/admin-ui-replication-dashboard.md b/src/current/v1.1/admin-ui-replication-dashboard.md
deleted file mode 100644
index b7510a0754c..00000000000
--- a/src/current/v1.1/admin-ui-replication-dashboard.md
+++ /dev/null
@@ -1,92 +0,0 @@
----
-title: Replication Dashboard
-summary: The Replication dashboard lets you monitor the replication metrics for your cluster.
-toc: true
----
-
-The **Replication** dashboard in the CockroachDB Admin UI enables you to monitor the replication metrics for your cluster. To view this dashboard, [access the Admin UI](admin-ui-access-and-navigate.html#access-the-admin-ui) and then select **Dashboard** > **Replication**.
-
-
-## Review of CockroachDB terminology
-
-- **Range**: CockroachDB stores all user data and almost all system data in a giant sorted map of key-value pairs. This keyspace is divided into "ranges", contiguous chunks of the keyspace, so that every key can always be found in a single range.
-- **Range Replica:** CockroachDB replicates each range (3 times by default) and stores each replica on a different node.
-- **Range Lease:** 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.
-- **Under-replicated Ranges:** When a cluster is first initialized, the few default starting ranges will only have a single replica, but as soon as other nodes are available, they will replicate to them until they've reached their desired replication factor, the default being 3. If a range does not have enough replicas, the range is said to be "under-replicated".
-- **Unavailable Ranges:** If a majority of a range's replicas are on nodes that are unavailable, then the entire range is unavailable and will be unable to process queries.
-
-For more details, see [Scalable SQL Made Easy: How CockroachDB Automates Operations](https://www.cockroachlabs.com/blog/automated-rebalance-and-repair/)
-
-## Replication Dashboard
-
-The **Replication** dashboard displays the following time series graphs:
-
-### Ranges
-
-
-
-The **Ranges** graph shows you various details about the status of ranges.
-
-- In the node view, the graph shows details about ranges on the node.
-
-- In the cluster view, the graph shows details about ranges across all nodes in the cluster.
-
-On hovering over the graph, the values for the following metrics are displayed:
-
-Metric | Description
---------|----
-Ranges | The number of ranges.
-Leaders | The number of ranges with leaders. If the number does not match the number of ranges for a long time, troubleshoot your cluster.
-Lease Holders | The number of ranges that have leases.
-Leaders w/o Leases | The number of Raft leaders without leases. If the number if non-zero for a long time, troubleshoot your cluster.
-Unavailable | The number of unavailable ranges. If the number if non-zero for a long time, troubleshoot your cluster.
-Under-replicated | The number of under-replicated ranges.
-
-### Replicas Per Store
-
-
-
-- In the node view, the graph shows the number of range replicas on the store.
-
-- In the cluster view, the graph shows the number of range replicas on each store.
-
-You can [Configure replication zones](configure-replication-zones.html) to set the number and location of replicas. You can monitor the configuration changes using the Admin UI, as described in [Fault tolerance and recovery](demo-fault-tolerance-and-recovery.html).
-
-### Replica Quiescence
-
-
-
-- In the node view, the graph shows the number of replicas on the node.
-
-- In the cluster view, the graph shows the number of replicas across all nodes.
-
-On hovering over the graph, the values for the following metrics are displayed:
-
-Metric | Description
---------|----
-Replicas | The number of replicas.
-Quiescent | The number of replicas that haven't been accessed for a while.
-
-### Snapshots
-
-
-
-Usually the nodes in a [Raft group](architecture/replication-layer.html#raft) stay synchronized by following along the log message by message. However, if a node is far enough behind the log (e.g., if it was offline or is a new node getting up to speed), rather than send all the individual messages that changed the range, the cluster can send it a snapshot of the range and it can start following along from there. Commonly this is done preemptively, when the cluster can predict that a node will need to catch up, but occasionally the Raft protocol itself will request the snapshot.
-
-Metric | Description
--------|------------
-Generated | The number of snapshots created per second.
-Applied (Raft-initiated) | The number of snapshots applied to nodes per second that were initiated within Raft.
-Applied (Preemptive) | The number of snapshots applied to nodes per second that were anticipated ahead of time (e.g., because a node was about to be added to a Raft group).
-Reserved | The number of slots reserved per second for incoming snapshots that will be sent to a node.
-
-### Other Graphs
-
-The **Replication** dashboard shows other time series graphs that are important for CockroachDB developers:
-
-- Leaseholders per Store
-- Live Bytes per Store
-- Keys Written per Second per Store
-- Range Operations
-
-For monitoring CockroachDB, it is sufficient to use the [**Ranges**](#ranges), [**Replicas per Store**](#replicas-per-store), and [**Replica Quiescence**](#replica-quiescence) graphs.
diff --git a/src/current/v1.1/admin-ui-runtime-dashboard.md b/src/current/v1.1/admin-ui-runtime-dashboard.md
deleted file mode 100644
index 699f74320f9..00000000000
--- a/src/current/v1.1/admin-ui-runtime-dashboard.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Runtime Dashboard
-toc: true
----
-
-The **Runtime** dashboard in the CockroachDB Admin UI lets you monitor runtime metrics for you cluster, such as node count, CPU time, and memory usage. To view this dashboard, [access the Admin UI](admin-ui-access-and-navigate.html#access-the-admin-ui) and then select **Dashboard** > **Runtime**.
-
-
-The **Runtime** dashboard displays the following time series graphs:
-
-## Node Count
-
-
-
-In the node view as well as the cluster view, the graph shows the number of live nodes in the cluster.
-
-A dip in the graph indicates decommissioned nodes, dead nodes, or nodes that are not responding. To troubleshoot the dip in the graph, refer to the [Summary panel](admin-ui-access-and-navigate.html#summary-panel).
-
-## Memory Usage
-
-
-
-- In the node view, the graph shows the memory in use for the selected node.
-
-- In the cluster view, the graph shows the memory in use across all nodes in the cluster.
-
-On hovering over the graph, the values for the following metrics are displayed:
-
-Metric | Description
---------|----
-RSS | Total memory in use by CockroachDB.
-Go Allocated | Memory allocated by the Go layer.
-Go Total | Total memory managed by the Go layer.
-CGo Allocated | Memory allocated by the C layer.
-CGo Total | Total memory managed by the C layer.
-
-{{site.data.alerts.callout_info}}If Go Total or CGO Total fluctuates or grows steadily over time, contact us.{{site.data.alerts.end}}
-
-## CPU Time
-
-
-
-- In the node view, the graph shows the [CPU time](https://en.wikipedia.org/wiki/CPU_time) used by CockroachDB user and system-level operations for the selected node.
-
-In the cluster view, the graph shows the [CPU time](https://en.wikipedia.org/wiki/CPU_time) used by CockroachDB user and system-level operations across all nodes in the cluster.
-
-On hovering over the CPU Time graph, the values for the following metrics are displayed:
-
-Metric | Description
---------|----
-User CPU Time | Total CPU seconds per second used by the CockroachDB process across all nodes.
-Sys CPU Time | Total CPU seconds per second used by the system calls made by CockroachDB across all nodes.
-GC Pause Time | Time required by the Garbage Collection process of Go.
-
-{{site.data.alerts.callout_info}}The GC Pause Time metric is important for CockroachDB developers. For monitoring CockroachDB, it is sufficient to monitor the User CPU Time and Sys CPU Time.{{site.data.alerts.end}}
-
-## Other Graphs
-
-The **Runtime** dashboard shows other time series graphs that are important for CockroachDB developers:
-
-- Goroutine Count
-- GC Runs
-- GC Pause Time
-
-For monitoring CockroachDB, it is sufficient to use the [**Node Count**](#node-count), [**Memory Usage**](#memory-usage), and [**CPU Time**](#cpu-time) graphs.
diff --git a/src/current/v1.1/admin-ui-sql-dashboard.md b/src/current/v1.1/admin-ui-sql-dashboard.md
deleted file mode 100644
index 4d594681572..00000000000
--- a/src/current/v1.1/admin-ui-sql-dashboard.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: SQL Dashboard
-summary: The SQL dashboard lets you monitor the performance of your SQL queries.
-toc: true
----
-
-The **SQL** dashboard in the CockroachDB Admin UI lets you monitor the performance of your SQL queries. To view this dashboard, [access the Admin UI](admin-ui-access-and-navigate.html#access-the-admin-ui) and then select **Dashboard** > **SQL**.
-
-
-The **SQL** dashboard displays the following time series graphs:
-
-## SQL Connections
-
-
-
-- In the node view, the graph shows the number of connections currently open between the client and the selected node.
-
-- In the cluster view, the graph shows the total number of SQL client connections to all nodes combined.
-
-## SQL Byte Traffic
-
-
-
-The **SQL Byte Traffic** graph helps you correlate SQL query count to byte traffic, especially in bulk data inserts or analytic queries that return data in bulk.
-
-- In the node view, the graph shows the current byte throughput (bytes/second) between all the currently connected SQL clients and the node.
-
-- In the cluster view, the graph shows the aggregate client throughput across all nodes.
-
-## SQL Queries
-
-
-
-- In the node view, the graph shows the current moving average, over the last 10 seconds, of the number of `SELECT`/`INSERT`/`UPDATE`/`DELETE` queries per second issued by SQL clients on the node.
-
-- In the cluster view, the graph shows the sum of the per-node averages, that is, an aggregate estimation of the current query load over the cluster, assuming the last 10 seconds of activity per node are representative of this load.
-
-## Transactions
-
-
-
-- In the node view, the graph shows separately the current moving average, over the last 10 seconds, of the number of opened, committed, aborted and rolled back transactions per second issued by SQL clients on the node.
-
-- In the cluster view, the graph shows the sum of the per-node averages, that is, an aggregate estimation of the current transactions load over the cluster, assuming the last 10 seconds of activity per node are representative of this load.
-
-If the graph shows excessive aborts or rollbacks, it might indicate issues with the SQL queries. In that case, re-examine queries to lower contention.
-
-## Service Latency
-
-
-
-Service latency is calculated as the time between when the cluster receives a query and finishes executing the query. This time does not include returning results to the client.
-
-- In the node view, the graph displays the 99th [percentile](https://en.wikipedia.org/wiki/Percentile#The_normal_distribution_and_percentiles) of service latency for the selected node.
-
-- In the cluster view, the graph displays the 99th [percentile](https://en.wikipedia.org/wiki/Percentile#The_normal_distribution_and_percentiles) of service latency for each node in the cluster.
-
-## Other Graphs
-
-The **SQL** dashboard shows other time series graphs that are important for CockroachDB developers:
-
-- Execution Latency
-- Active Distributed SQL Queries
-- Active Flows for Distributed SQL Queries
-- Service Latency: DistSQL
-- Schema Changes
-
-For monitoring CockroachDB, it is sufficient to use the [**SQL Connections**](#sql-connections), [**SQL Byte Traffic**](#sql-byte-traffic), [**SQL Queries**](#sql-queries), [**Service Latency**](#service-latency), and [**Transactions**](#transactions) graphs.
diff --git a/src/current/v1.1/admin-ui-storage-dashboard.md b/src/current/v1.1/admin-ui-storage-dashboard.md
deleted file mode 100644
index c306be474ac..00000000000
--- a/src/current/v1.1/admin-ui-storage-dashboard.md
+++ /dev/null
@@ -1,58 +0,0 @@
----
-title: Storage Dashboard
-summary: The Storage dashboard lets you monitor the storage utilization for your cluster.
-toc: true
----
-
-The **Storage** dashboard in the CockroachDB Admin UI lets you monitor the storage utilization for your cluster. To view this dashboard, [access the Admin UI](admin-ui-access-and-navigate.html#access-the-admin-ui) and then selecte **Dashboard** > **Storage**.
-
-
-The **Storage** dashboard displays the following time series graphs:
-
-## Capacity
-
-
-
-You can monitor the **Capacity** graph to determine when additional storage is needed.
-
-- In the node view, the graph shows the maximum allocated capacity, available storage capacity, and capacity used by CockroachDB for the selected node.
-
-- In the cluster view, the graph shows the maximum allocated capacity, available storage capacity, and capacity used by CockroachDB across all nodes in the cluster.
-
-On hovering over the graph, the values for the following metrics are displayed:
-
-Metric | Description
---------|----
-Capacity | The maximum storage capacity allocated to CockroachDB. You can configure the maximum allocated storage capacity for CockroachDB using the `--store` flag. For more information, see [Start a Node](start-a-node.html#store).
-Available | The free storage capacity available to CockroachDB.
-Used | Disk space used by the data in the CockroachDB store. Note that this value is less than (Capacity - Available) because Capacity and Available metrics consider the entire disk and all applications on the disk including CockroachDB, whereas Used metric tracks only the store's disk usage.
-
-{{site.data.alerts.callout_info}}
-{% include v1.1/misc/available-capacity-metric.md %}
-{{site.data.alerts.end}}
-
-## File Descriptors
-
-
-
-- In the node view, the graph shows the number of open file descriptors for that node, compared with the file descriptor limit.
-
-- In the cluster view, the graph shows the number of open file descriptors across all nodes, compared with the file descriptor limit.
-
-If the Open count is almost equal to the Limit count, increase [File Descriptors](recommended-production-settings.html#file-descriptors-limit).
-
-{{site.data.alerts.callout_info}}If you are running multiple nodes on a single machine (not recommended), the actual number of open file descriptors are considered open on each node. Thus the limit count value displayed on the Admin UI is the actual value of open file descriptors multiplied by the number of nodes, compared with the file descriptor limit. {{site.data.alerts.end}}
-
-For Windows systems, you can ignore the File Descriptors graph because the concept of file descriptors is not applicable to Windows.
-
-## Other Graphs
-
-The **Storage** dashboard shows other time series graphs that are important for CockroachDB developers:
-
-- Live Bytes
-- Log Commit Latency
-- Command Commit Latency
-- RocksDB Read Amplification
-- RocksDB SSTables
-
-For monitoring CockroachDB, it is sufficient to use the [**Capacity**](#capacity) and [**File Descriptors**](#file-descriptors) graphs.
diff --git a/src/current/v1.1/alter-column.md b/src/current/v1.1/alter-column.md
deleted file mode 100644
index 4d06c8fc9b6..00000000000
--- a/src/current/v1.1/alter-column.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: ALTER COLUMN
-summary: Use the ALTER COLUMN statement to set, change, or drop a column's Default constraint or to drop the Not Null constraint.
-toc: true
----
-
-The `ALTER COLUMN` [statement](sql-statements.html) is part of `ALTER TABLE` and sets, changes, or drops a column's [Default constraint](default-value.html) or drops the [Not Null constraint](not-null.html).
-
-{{site.data.alerts.callout_info}}To manage other constraints, see ADD CONSTRAINT and DROP CONSTRAINT{{site.data.alerts.end}}
-
-
-## Synopsis
-
-{% include {{ page.version.version }}/sql/diagrams/alter_column.html %}
-
-## Required Privileges
-
-The user must have the `CREATE` [privilege](privileges.html) on the table.
-
-## Parameters
-
-| Parameter | Description |
-|-----------|-------------|
-| `table_name` | The name of the table with the column you want to modify. |
-| `name` | The name of the column you want to modify. |
-| `a_expr` | The new Default Value you want to use. |
-
-## Viewing Schema Changes New in v1.1
-{% include {{ page.version.version }}/misc/schema-change-view-job.md %}
-
-## Examples
-
-### Set or Change a Default Value
-
-Setting the [Default Value constraint](default-value.html) inserts the value when data's written to the table without explicitly defining the value for the column. If the column already has a Default Value set, you can use this statement to change it.
-
-The below example inserts the Boolean value `true` whenever you inserted data to the `subscriptions` table without defining a value for the `newsletter` column.
-
-~~~ sql
-> ALTER TABLE subscriptions ALTER COLUMN newsletter SET DEFAULT true;
-~~~
-
-### Remove Default Constraint
-
-If the column has a defined [Default Value](default-value.html), you can remove the constraint, which means the column will no longer insert a value by default if one is not explicitly defined for the column.
-
-~~~ sql
-> ALTER TABLE subscriptions ALTER COLUMN newsletter DROP DEFAULT;
-~~~
-
-### Remove Not Null Constraint
-
-If the column has the [Not Null constraint](not-null.html) applied to it, you can remove the constraint, which means the column becomes optional and can have *NULL* values written into it.
-
-~~~ sql
-> ALTER TABLE subscriptions ALTER COLUMN newsletter DROP NOT NULL;
-~~~
-
-## See Also
-
-- [Constraints](constraints.html)
-- [`ADD CONSTRAINT`](add-constraint.html)
-- [`DROP CONSTRAINT`](drop-constraint.html)
-- [`ALTER TABLE`](alter-table.html)
diff --git a/src/current/v1.1/alter-database.md b/src/current/v1.1/alter-database.md
deleted file mode 100644
index 31972f31829..00000000000
--- a/src/current/v1.1/alter-database.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: ALTER DATABASE
-summary: Use the ALTER DATABASE statement to change an existing database.
-toc: false
----
-
-The `ALTER DATABASE` [statement](sql-statements.html) applies a schema change to a database.
-
-{{site.data.alerts.callout_info}}To understand how CockroachDB changes schema elements without requiring table locking or other user-visible downtime, see Online Schema Changes in CockroachDB.{{site.data.alerts.end}}
-
-For information on using `ALTER DATABASE`, see the documents for its relevant subcommands.
-
-Subcommand | Description
------------|------------
-[`RENAME`](rename-database.html) | Change the name of a database.
diff --git a/src/current/v1.1/alter-index.md b/src/current/v1.1/alter-index.md
deleted file mode 100644
index d70fc7f26f1..00000000000
--- a/src/current/v1.1/alter-index.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: ALTER INDEX
-summary: Use the ALTER INDEX statement to change an existing index.
-toc: false
----
-
-The `ALTER INDEX` [statement](sql-statements.html) applies a schema change to an index.
-
-{{site.data.alerts.callout_info}}To understand how CockroachDB changes schema elements without requiring table locking or other user-visible downtime, see Online Schema Changes in CockroachDB.{{site.data.alerts.end}}
-
-For information on using `ALTER INDEX`, see the documents for its relevant subcommands.
-
-Subcommand | Description
------------|------------
-[`RENAME`](rename-index.html) | Change the name of an index.
-`SPLIT AT` | *(Documentation pending)* Potentially improve performance by identifying ideal locations to split data in the key-value layer.
diff --git a/src/current/v1.1/alter-table.md b/src/current/v1.1/alter-table.md
deleted file mode 100644
index 5be5ec157f3..00000000000
--- a/src/current/v1.1/alter-table.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: ALTER TABLE
-summary: Use the ALTER TABLE statement to change the schema of a table.
-toc: true
----
-
-The `ALTER TABLE` [statement](sql-statements.html) applies a schema change to a table.
-
-{{site.data.alerts.callout_info}}To understand how CockroachDB changes schema elements without requiring table locking or other user-visible downtime, see Online Schema Changes in CockroachDB.{{site.data.alerts.end}}
-
-
-## Subcommands
-
-For information on using `ALTER TABLE`, see the documents for its relevant subcommands.
-
-Subcommand | Description
------------|------------
-[`ADD COLUMN`](add-column.html) | Add columns to tables.
-[`ADD CONSTRAINT`](add-constraint.html) | Add constraints to columns.
-[`ALTER COLUMN`](alter-column.html) | Change or drop a column's [Default constraint](default-value.html) or drop the [Not Null constraint](not-null.html).
-[`DROP COLUMN`](drop-column.html) | Remove columns from tables.
-[`DROP CONSTRAINT`](drop-constraint.html) | Remove constraints from columns.
-[`RENAME COLUMN`](rename-column.html) | Change the names of columns.
-[`RENAME TABLE`](rename-table.html) | Change the names of tables.
-`SPLIT AT` | *(Documentation pending)* Potentially improve performance by identifying ideal locations to split data in the key-value layer.
-
-## Viewing Schema Changes New in v1.1
-
-{% include {{ page.version.version }}/misc/schema-change-view-job.md %}
diff --git a/src/current/v1.1/alter-view.md b/src/current/v1.1/alter-view.md
deleted file mode 100644
index f920fc805e5..00000000000
--- a/src/current/v1.1/alter-view.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: ALTER VIEW
-summary: The ALTER VIEW statement changes the name of a view.
-toc: true
----
-
-The `ALTER VIEW` [statement](sql-statements.html) changes the name of a [view](views.html).
-
-{{site.data.alerts.callout_info}}It is not currently possible to change the SELECT statement executed by a view. Instead, you must drop the existing view and create a new view. Also, it is not currently possible to rename a view that other views depend on, but this ability may be added in the future (see this issue).{{site.data.alerts.end}}
-
-
-## Required Privileges
-
-The user must have the `DROP` [privilege](privileges.html) on the view and the `CREATE` privilege on the parent database.
-
-## Synopsis
-
-{% include {{ page.version.version }}/sql/diagrams/alter_view.html %}
-
-## Parameters
-
-Parameter | Description
-----------|------------
-`IF EXISTS` | Rename the view only if a view of `view_name` exists; if one does not exist, do not return an error.
-`view_name` | The name of the view to rename. To find view names, use:`SELECT * FROM information_schema.tables WHERE table_type = 'VIEW';` -`name` | The new [`name`](sql-grammar.html#name) for the view, which must be unique to its database and follow these [identifier rules](keywords-and-identifiers.html#identifiers). - -## Example - -~~~ sql -> SELECT * FROM information_schema.tables WHERE table_type = 'VIEW'; -~~~ - -~~~ -+---------------+-------------------+--------------------+------------+---------+ -| TABLE_CATALOG | TABLE_SCHEMA | TABLE_NAME | TABLE_TYPE | VERSION | -+---------------+-------------------+--------------------+------------+---------+ -| def | bank | user_accounts | VIEW | 2 | -| def | bank | user_emails | VIEW | 1 | -+---------------+-------------------+--------------------+------------+---------+ -(2 rows) -~~~ - -~~~ sql -> ALTER VIEW bank.user_emails RENAME TO bank.user_email_addresses; -~~~ - -~~~ -RENAME VIEW -~~~ - -~~~ sql -> SELECT * FROM information_schema.tables WHERE table_type = 'VIEW'; -~~~ - -~~~ -+---------------+-------------------+----------------------+------------+---------+ -| TABLE_CATALOG | TABLE_SCHEMA | TABLE_NAME | TABLE_TYPE | VERSION | -+---------------+-------------------+----------------------+------------+---------+ -| def | bank | user_accounts | VIEW | 2 | -| def | bank | user_email_addresses | VIEW | 3 | -+---------------+-------------------+----------------------+------------+---------+ -(2 rows) -~~~ - -## See Also - -- [Views](views.html) -- [`CREATE VIEW`](create-view.html) -- [`SHOW CREATE VIEW`](show-create-view.html) -- [`DROP VIEW`](drop-view.html) diff --git a/src/current/v1.1/architecture/distribution-layer.md b/src/current/v1.1/architecture/distribution-layer.md deleted file mode 100644 index 69865e1ed64..00000000000 --- a/src/current/v1.1/architecture/distribution-layer.md +++ /dev/null @@ -1,183 +0,0 @@ ---- -title: Distribution Layer -summary: -toc: true ---- - -The Distribution Layer of CockroachDB's architecture provides a unified view of your cluster's data. - -{{site.data.alerts.callout_info}}If you haven't already, we recommend reading the Architecture Overview.{{site.data.alerts.end}} - - -## Overview - -To make all data in your cluster accessible from any node, CockroachDB stores data in a monolithic sorted map of key-value pairs. This keyspace describes all of the data in your cluster, as well as its location, and is divided into what we call "ranges", contiguous chunks of the keyspace, so that every key can always be found in a single range. - -CockroachDB implements a sorted map to enable: - - - **Simple lookups**: Because we identify which nodes are responsible for certain portions of the data, queries are able to quickly locate where to find the data they want. - - **Efficient scans**: By defining the order of data, it's easy to find data within a particular range during a scan. - -### Monolithic Sorted Map Structure - -The monolithic sorted map is comprised of two fundamental elements: - -- System data, which include **meta ranges** that describe the locations of data in your cluster (among many other cluster-wide and local data elements) -- User data, which store your cluster's **table data** - -#### Meta Ranges - -The locations of all ranges in your cluster are stored in a two-level index at the beginning of your key-space, known as meta ranges, where the first level (`meta1`) addresses the second, and the second (`meta2`) addresses data in the cluster. Importantly, every node has information on where to locate the `meta1` range (known as its Range Descriptor, detailed below), and the range is never split. - -This meta range structure lets us address up to 4EiB of user data by default: we can address 2^(18 + 18) = 2^36 ranges; each range addresses 2^26 B, and altogether we address 2^(36+26) B = 2^62 B = 4EiB. However, with larger range sizes, it's possible to expand this capacity even further. - -Meta ranges are treated mostly like normal ranges and are accessed and replicated just like other elements of your cluster's KV data. - -Each node caches values of the `meta2` range it has accessed before, which optimizes access of that data in the future. Whenever a node discovers that its `meta2` cache is invalid for a specific key, the cache is updated by performing a regular read on the `meta2` range. - -#### Table Data - -After the node's meta ranges is the KV data your cluster stores. - -This data is broken up into 64MiB sections of contiguous key-space known as ranges. This size represents a sweet spot for us between a size that's small enough to move quickly between nodes, but large enough to store a meaningfully contiguous set of data whose keys are more likely to be accessed together. These ranges are then shuffled around your cluster to ensure survivability. - -These ranges are replicated (in the aptly named Replication Layer), and have the addresses of each replica stored in the `meta2` range. - -### Using the Monolithic Sorted Map - -When a node receives a request, it looks at the Meta Ranges to find out which node it needs to route the request to by comparing the keys in the request to the keys in its `meta2` range. - -These meta ranges are heavily cached, so this is normally handled without having to send an RPC to the node actually containing the `meta2` ranges. - -The node then sends those KV operations to the Leaseholder identified in the `meta2` range. However, it's possible that the data moved, in which case the node that no longer has the information replies to the requesting node where it's now located. In this case we go back to the `meta2` range to get more up-to-date information and try again. - -### Interactions with Other Layers - -In relationship to other layers in CockroachDB, the Distribution Layer: - -- Receives requests from the Transaction Layer on the same node. -- Identifies which nodes should receive the request, and then sends the request to the proper node's Replication Layer. - -## Technical Details & Components - -### gRPC - -gRPC is the software nodes use to communicate with one another. Because the Distribution Layer is the first layer to communicate with other nodes, CockroachDB implements gRPC here. - -gRPC requires inputs and outputs to be formatted as protocol buffers (protobufs). To leverage gRPC, CockroachDB implements a protocol-buffer-based API defined in `api.proto`. - -For more information about gRPC, see the [official gRPC documentation](http://www.grpc.io/docs/guides/). - -### BatchRequest - -All KV operation requests are bundled into a [protobuf](https://en.wikipedia.org/wiki/Protocol_Buffers), known as a `BatchRequest`. The destination of this batch is identified in the `BatchRequest` header, as well as a pointer to the request's transaction record. (On the other side, when a node is replying to a `BatchRequest`, it uses a protobuf––`BatchResponse`.) - -This `BatchRequest` is also what's used to send requests between nodes using gRPC, which accepts and sends protocol buffers. - -### DistSender - -The gateway/coordinating node's `DistSender` receives `BatchRequest`s from its own `TxnCoordSender`. `DistSender` is then responsible for breaking up `BatchRequests` and routing a new set of `BatchRequests` to the nodes it identifies contain the data using its `meta2` ranges. It will use the cache to send the request to the Leaseholder, but it's also prepared to try the other replicas, in order of "proximity". The replica that the cache says is the Leaseholder is simply moved to the front of the list of replicas to be tried and then an RPC is sent to all of them, in order. - -Requests received by a non-Leaseholder fail with an error pointing at the replica's last known Leaseholder. These requests are retried transparently with the updated lease by the gateway node and never reach the client. - -As nodes begin replying to these commands, `DistSender` also aggregates the results in preparation for returning them to the client. - -### Meta Range KV Structure - -Like all other data in your cluster, meta ranges are structured as KV pairs. Both meta ranges have a similar structure: - -~~~ -metaX/successorKey -> LeaseholderAddress, [list of other nodes containing data] -~~~ - -Element | Description ---------|------------------------ -`metaX` | The level of meta range. Here we use a simplified `meta1` or `meta2`, but these are actually represented in `cockroach` as `\x02` and `\x03` respectively. -`successorKey` | The first key *greater* than the key you're scanning for. This makes CockroachDB's scans efficient; it simply scans the keys until it finds a value greater than the key it's looking for, and that is where it finds the relevant data.
The `successorKey` for the end of a keyspace is identified as `maxKey`. -`LeaseholderAddress` | The replica primarily responsible for reads and writes, known as the Leaseholder. The Replication Layer contains more information about [Leases](replication-layer.html#leases). - -Here's an example: - -~~~ -meta2/M -> node1:26257, node2:26257, node3:26257 -~~~ - -In this case, the replica on `node1` is the Leaseholder, and nodes 2 and 3 also contain replicas. - -#### Example - -Let's imagine we have an alphabetically sorted column, which we use for lookups. Here are what the meta ranges would approximately look like: - -1. `meta1` contains the address for the nodes containing the `meta2` replicas. - - ~~~ - # Points to meta2 range for keys [A-M) - meta1/M -> node1:26257, node2:26257, node3:26257 - - # Points to meta2 range for keys [M-Z] - meta1/maxKey -> node4:26257, node5:26257, node6:26257 - ~~~ - -2. `meta2` contains addresses for the nodes containing the replicas of each range in the cluster, the first of which is the [Leaseholder](replication-layer.html#leases). - - ~~~ - # Contains [A-G) - meta2/G -> node1:26257, node2:26257, node3:26257 - - # Contains [G-M) - meta2/M -> node1:26257, node2:26257, node3:26257 - - #Contains [M-Z) - meta2/Z -> node4:26257, node5:26257, node6:26257 - - #Contains [Z-maxKey) - meta2/maxKey-> node4:26257, node5:26257, node6:26257 - ~~~ - -### Table Data KV Structure - -Key-Value data, which represents the data in your tables using the following structure: - -~~~ -/
diff --git a/src/current/v1.1/back-up-data.md b/src/current/v1.1/back-up-data.md
deleted file mode 100644
index e9a02f47c9f..00000000000
--- a/src/current/v1.1/back-up-data.md
+++ /dev/null
@@ -1,26 +0,0 @@
----
-title: Back Up Data
-summary: Learn how to back up and restore a CockroachDB cluster.
-toc: false
----
-
-CockroachDB offers the following methods to back up your cluster's data:
-
-- [`cockroach dump`](sql-dump.html), which is a CLI command to dump/export your database's schema and table data.
-- [`BACKUP`](backup.html) (*[enterprise license](https://www.cockroachlabs.com/pricing/) only*), which is a SQL statement that backs up your cluster to cloud or network file storage.
-
-### Details
-
-We recommend creating daily backups of your data as an operational best practice.
-
-However, because CockroachDB is designed with high fault tolerance, backups are primarily needed for disaster recovery (i.e., if your cluster loses a majority of its nodes). Isolated issues (such as small-scale node outages) do not require any intervention.
-
-## Restore
-
-For information about restoring your backed up data, see [Restoring Data](restore-data.html).
-
-## See Also
-
-- [Restore Data](restore-data.html)
-- [Use the Built-in SQL Client](use-the-built-in-sql-client.html)
-- [Other Cockroach Commands](cockroach-commands.html)
diff --git a/src/current/v1.1/backup.md b/src/current/v1.1/backup.md
deleted file mode 100644
index d56bf42b226..00000000000
--- a/src/current/v1.1/backup.md
+++ /dev/null
@@ -1,150 +0,0 @@
----
-title: BACKUP
-summary: Back up your CockroachDB cluster to a cloud storage services such as AWS S3, Google Cloud Storage, or other NFS.
-toc: true
----
-
-{{site.data.alerts.callout_danger}}The | - | - - | -- - | -CockroachDB | -
|---|---|---|---|
- Automated Scaling
-
- 
-
- |
- - No - Yes - | -- No - Yes - | -Yes | -
|
- Automated Failover
-
-
-
- |
- - Optional - Yes - | -- Optional - Yes - | -Yes | -
|
- Automated Repair
-
-
-
- |
- - No - Yes - | -- No - Yes - | -Yes | -
|
- Strongly Consistent Replication
-
-
-
- |
- - No - Optional - Yes - | -- No - Optional - Yes - | -Yes | -
|
- Consensus-Based Replication
-
-
-
- |
- - No - Optional - Yes - | -- No - Optional - Yes - | -Yes | -
|
- Distributed Transactions
-
-
-
- |
- - No - Yes - No* - | -- No - Yes - No* - | -Yes | -
|
- ACID Semantics
-
-
-
- |
- - Yes - No - Row-only - Row-only* - Document-only - | -- Yes - No - Row-only - Row-only* - Document-only - | -Yes | -
|
- Eventually Consistent Reads
-
-
-
- |
- - Yes - | -- Yes - | -No | -
|
- SQL
-
-
-
- |
- - Yes - No - Read-only - | -- Yes - No - Read-only - | -Yes | -
|
- Open Source
-
-
-
- |
- - Yes - No - | -- Yes - No - | -Yes | -
|
- Commercial Version
-
-
-
- |
- - Optional - No - Yes - | -- Optional - No - Yes - | -Optional | -
|
- Support
-
-
-
- |
- - Full - | -- Full - | -Full | -
STRING.{{site.data.alerts.end}}
-
-- **Value syntax**: `CREATE TABLE statement.{{site.data.alerts.end}}
-
-### Assign Column Families When Adding Columns
-
-When using the [`ALTER TABLE .. ADD COLUMN`](add-column.html) statement to add a column to a table, you can assign the column to a new or existing column family.
-
-- Use the `CREATE FAMILY` keyword to assign a new column to a **new family**. For example, the following would add a `data2 BYTES` column to the `test` table above and assign it to a new column family:
-
- ~~~ sql
- > ALTER TABLE test ADD COLUMN data2 BYTES CREATE FAMILY f3;
- ~~~
-
-- Use the `FAMILY` keyword to assign a new column to an **existing family**. For example, the following would add a `name STRING` column to the `test` table above and assign it to family `f1`:
-
- ~~~ sql
- > ALTER TABLE test ADD COLUMN name STRING FAMILY f1;
- ~~~
-
-- Use the `CREATE IF NOT EXISTS FAMILY` keyword to assign a new column to an **existing family or, if the family doesn't exist, to a new family**. For example, the following would assign the new column to the existing `f1` family; if that family didn't exist, it would create a new family and assign the column to it:
-
- ~~~ sql
- > ALTER TABLE test ADD COLUMN name STRING CREATE IF NOT EXISTS FAMILY f1;
- ~~~
-
-## Compatibility with Past Releases
-
-Using the [`beta-20160714`](../releases/v1.0.html#beta-20160714) release makes your data incompatible with versions earlier than the [`beta-20160629`](../releases/v1.0.html#beta-20160629) release.
-
-## See Also
-
-- [`CREATE TABLE`](create-table.html)
-- [`ADD COLUMN`](add-column.html)
-- [Other SQL Statements](sql-statements.html)
diff --git a/src/current/v1.1/commit-transaction.md b/src/current/v1.1/commit-transaction.md
deleted file mode 100644
index 24a267258c5..00000000000
--- a/src/current/v1.1/commit-transaction.md
+++ /dev/null
@@ -1,66 +0,0 @@
----
-title: COMMIT
-summary: Commit a transaction with the COMMIT statement in CockroachDB.
-toc: true
----
-
-The `COMMIT` [statement](sql-statements.html) commits the current [transaction](transactions.html) or, when using [client-side transaction retries](transactions.html#client-side-transaction-retries), clears the connection to allow new transactions to begin.
-
-When using [client-side transaction retries](transactions.html#client-side-transaction-retries), statements issued after [`SAVEPOINT cockroach_restart`](savepoint.html) are committed when [`RELEASE SAVEPOINT cockroach_restart`](release-savepoint.html) is issued instead of `COMMIT`. However, you must still issue a `COMMIT` statement to clear the connection for the next transaction.
-
-For non-retryable transactions, if statements in the transaction [generated any errors](transactions.html#error-handling), `COMMIT` is equivalent to `ROLLBACK`, which aborts the transaction and discards *all* updates made by its statements.
-
-
-## Synopsis
-
-{% include {{ page.version.version }}/sql/diagrams/commit_transaction.html %}
-
-## Required Privileges
-
-No [privileges](privileges.html) are required to commit a transaction. However, privileges are required for each statement within a transaction.
-
-## Aliases
-
-In CockroachDB, `END` is an alias for the `COMMIT` statement.
-
-## Example
-
-### Commit a Transaction
-
-How you commit transactions depends on how your application handles [transaction retries](transactions.html#transaction-retries).
-
-#### Client-Side Retryable Transactions
-
-When using [client-side transaction retries](transactions.html#client-side-transaction-retries), statements are committed by [`RELEASE SAVEPOINT cockroach_restart`](release-savepoint.html). `COMMIT` itself only clears the connection for the next transaction.
-
-~~~ sql
-> BEGIN;
-
-> SAVEPOINT cockroach_restart;
-
-> UPDATE products SET inventory = 0 WHERE sku = '8675309';
-
-> INSERT INTO orders (customer, sku, status) VALUES (1001, '8675309', 'new');
-
-> RELEASE SAVEPOINT cockroach_restart;
-
-> COMMIT;
-~~~
-
-{{site.data.alerts.callout_danger}}This example assumes you're using client-side intervention to handle transaction retries.{{site.data.alerts.end}}
-
-#### Automatically Retried Transactions
-
-If you are using transactions that CockroachDB will [automatically retry](transactions.html#automatic-retries) (i.e., all statements sent in a single batch), commit the transaction with `COMMIT`.
-
-~~~ sql
-> BEGIN; UPDATE products SET inventory = 100 WHERE = '8675309'; UPDATE products SET inventory = 100 WHERE = '8675310'; COMMIT;
-~~~
-
-## See Also
-
-- [Transactions](transactions.html)
-- [`BEGIN`](begin-transaction.html)
-- [`RELEASE SAVEPOINT`](release-savepoint.html)
-- [`ROLLBACK`](rollback-transaction.html)
-- [`SAVEPOINT`](savepoint.html)
diff --git a/src/current/v1.1/common-errors.md b/src/current/v1.1/common-errors.md
deleted file mode 100644
index 98f3dfb7f5c..00000000000
--- a/src/current/v1.1/common-errors.md
+++ /dev/null
@@ -1,162 +0,0 @@
----
-title: Common Errors
-summary: Understand and resolve common error messages written to stderr or logs.
-toc: false
----
-
-This page helps you understand and resolve error messages written to `stderr` or your [logs](debug-and-error-logs.html).
-
-Topic | Message
-------|--------
-Client connection | [`connection refused`](#connection-refused)
-Client connection | [`node is running secure mode, SSL connection required`](#node-is-running-secure-mode-ssl-connection-required)
-Transactions | [`retry transaction`](#retry-transaction)
-Node startup | [`node belongs to cluster root user can configure replication zones.{{site.data.alerts.end}}
-
-
-## Overview
-
-### Replication Zone Levels
-
-There are three replication zone levels:
-
-- **Cluster:** CockroachDB comes with a single, default replication zone for the entire cluster. See [View the Default Replication Zone](#view-the-default-replication-zone) and [Edit the Default Replication Zone](#edit-the-default-replication-zone) for more details.
-- **Database:** You can add replication zones for specific databases. See [Create a Replication Zone for a Database](#create-a-replication-zone-for-a-database) for more details.
-- **Table:** You can add replication zones for specific tables. See [Create a Replication Zone for a Table](#create-a-replication-zone-for-a-table) for more details.
-
-When replicating a piece of data, CockroachDB uses the most granular zone available: If there's a replication zone for the table containing the data, CockroachDB uses it; otherwise, it uses the replication zone for the database containing the data. If there's no applicable table or database replication zone, CockroachDB uses the cluster-wide replication zone.
-
-In addition to the databases and tables that are visible via SQL, CockroachDB stores additional internal data in what are called system ranges. You can configure replication zones for parts of these internal data ranges if you'd like to override the cluster-wide settings. See [Create a Replication Zone for System Ranges](#create-a-replication-zone-for-system-ranges) for more details.
-
-### Replication Zone Format
-
-A replication zone is specified in [YAML](https://en.wikipedia.org/wiki/YAML) format and looks like this:
-
-~~~ yaml
-range_min_bytes: **Default:** `67108864` (64MiB) -`ttlseconds` | The number of seconds overwritten values will be retained before garbage collection. Smaller values can save disk space if values are frequently overwritten; larger values increase the range allowed for `AS OF SYSTEM TIME` queries, also know as [Time Travel Queries](select.html#select-historical-data-time-travel).
It is not recommended to set this below `600` (10 minutes); doing so will cause problems for long-running queries. Also, since all versions of a row are stored in a single range that never splits, it is not recommended to set this so high that all the changes to a row in that time period could add up to more than 64MiB; such oversized ranges could contribute to the server running out of memory or other problems.
**Default:** `90000` (25 hours) -`num_replicas` | The number of replicas in the zone.
**Default:** `3` -`constraints` | A comma-separated list of required and/or prohibited constraints influencing the location of replicas. See [Constraints in Replication Zones](#constraints-in-replication-zones) for more details.
**Default:** No constraints, with CockroachDB locating each replica on a unique node and attempting to spread replicas evenly across localities. - -### Replication Constraints - -The location of replicas, both when they are first added and when they are rebalanced to maintain cluster equilibrium, is based on the interplay between descriptive attributes assigned to nodes and constraints set in zone configurations. - -{{site.data.alerts.callout_success}}For demonstrations of how to set node attributes and replication constraints in different scenarios, see Scenario-based Examples below.{{site.data.alerts.end}} - -#### Descriptive Attributes Assigned to Nodes - -When starting a node with the [`cockroach start`](start-a-node.html) command, you can assign the following types of descriptive attributes: - -Attribute Type | Description ----------------|------------ -**Node Locality** | Using the `--locality` flag, you can assign arbitrary key-value pairs that describe the locality of the node. Locality might include country, region, datacenter, rack, etc. The key-value pairs should be ordered from most inclusive to least inclusive (e.g., country before datacenter before rack), and the keys and the order of key-value pairs must be the same on all nodes. It's typically better to include more pairs than fewer. For example:
`--locality=region=east,datacenter=us-east-1`
`--locality=region=east,datacenter=us-east-2`
`--locality=region=west,datacenter=us-west-1`
CockroachDB attempts to spread replicas evenly across the cluster based on locality, with the order determining the priority. However, locality can be used to influence the location of data replicas in various ways using replication zones.
When there is high latency between nodes, CockroachDB also uses locality to move range leases closer to the current workload, reducing network round trips and improving read performance. See [Follow-the-workload](demo-follow-the-workload.html) for more details. -**Node Capability** | Using the `--attrs` flag, you can specify node capability, which might include specialized hardware or number of cores, for example:
`--attrs=ram:64gb` -**Store Type/Capability** | Using the `attrs` field of the `--store` flag, you can specify disk type or capability, for example:
`--store=path=/mnt/ssd01,attrs=ssd`
`--store=path=/mnt/hda1,attrs=hdd:7200rpm` - -#### Constraints in Replication Zones - -The node-level and store-level descriptive attributes mentioned above can be used as the following types of constraints in replication zones to influence the location of replicas. However, note the following general guidance: - -- When locality is the only consideration for replication, it's recommended to set locality on nodes without specifying any constraints in zone configurations. In the absence of constraints, CockroachDB attempts to spread replicas evenly across the cluster based on locality. -- Required and prohibited constraints are useful in special situations where, for example, data must or must not be stored in a specific country or on a specific type of machine. - -Constraint Type | Description | Syntax -----------------|-------------|------- -**Required** | When placing replicas, the cluster will consider only nodes/stores with matching attributes. When there are no matching nodes/stores with capacity, new replicas will not be added. | `[+ssd]` -**Prohibited** | When placing replicas, the cluster will ignore nodes/stores with matching attributes. When there are no alternate nodes/stores with capacity, new replicas will not be added. | `[-ssd]` - -### Node/Replica Recommendations - -See [Cluster Topography](recommended-production-settings.html#cluster-topology) recommendations for production deployments. - -## Subcommands - -Subcommand | Usage ------------|------ -`ls` | List all replication zones. -`get` | View the YAML contents of a replication zone. -`set` | Create or edit a replication zone. -`rm` | Remove a replication zone. - -## Synopsis - -~~~ shell -# List all replication zones: -$ cockroach zone ls
`-f` | The path to the [YAML file](#replication-zone-format) defining the zone configuration. To pass the zone configuration via the standard input, set this flag to `-`.
This flag is relevant only for the `set` subcommand. - -### Client Connection - -{% include {{ page.version.version }}/sql/connection-parameters-with-url.md %} - -See [Client Connection Parameters](connection-parameters.html) for more details. - -Currently, only the `root` user can configure replication zones and the `--database` flag is not effective. - -### Logging - -By default, the `zone` command logs errors to `stderr`. - -If you need to troubleshoot this command's behavior, you can change its [logging behavior](debug-and-error-logs.html). - -## Basic Examples - -These examples focus on the basic approach and syntax for working with zone configuration. For examples demonstrating how to use constraints, see [Scenario-based Examples](#scenario-based-examples). - -### View the Default Replication Zone - -The cluster-wide replication zone (`.default`) is initially set to replicate data to any three nodes in your cluster, with ranges in each replica splitting once they get larger than 67108864 bytes. - -To view the default replication zone, use the `cockroach zone get .default` command with appropriate flags: - -{% include copy-clipboard.html %} -~~~ shell -$ cockroach zone get .default --insecure -~~~ - -~~~ -.default -range_min_bytes: 1048576 -range_max_bytes: 67108864 -gc: - ttlseconds: 86400 -num_replicas: 3 -constraints: [] -~~~ - -### Edit the Default Replication Zone - -To edit the default replication zone, create a YAML file defining only the values you want to change (other values will not be affected), and use the `cockroach zone set .default -f
[Find more detail about how CockroachDB handles passwords](create-and-manage-users.html#user-authentication). | ✗ -`
cockroach commands that accept a URL with the
-command-line flag --url. If --url is not
-specified but the environment variable COCKROACH_URL is
-defined, the environment variable is used. Otherwise, the
-cockroach command will use discrete connection parameters
-as described below.{{site.data.alerts.end}}
-
-{{site.data.alerts.callout_info}}The <database>
-part should not be specified for any cockroach command
-other than cockroach
-sql.{{site.data.alerts.end}}
-
-### Additional Connection Parameters
-
-The following additional parameters can be passed after the `?` character in the URL:
-
-Parameter | Description | Default value
-----------|-------------|---------------
-`application_name` | An initial value for the [`application_name` session variable](set-vars.html). | Empty string.
-`sslmode` | Which type of secure connection to use: `disable`, `allow`, `prefer`, `require`, `verify-ca` or `verify-full`. See [Secure Connections With URLs](#secure-connections-with-urls) for details. | `disable`
-`sslrootcert` | Path to the [CA certificate](create-security-certificates.html), when `sslmode` is not `disable`. | Empty string.
-`sslcert` | Path to the [client certificate](create-security-certificates.html), when `sslmode` is not `disable`. | Empty string.
-`sslkey` | Path to the [client private key](create-security-certificates.html), when `sslmode` is not `disable`. | Empty string.
-
-### Secure Connections With URLs
-
-The following values are supported for `sslmode`, although only the first and the last are recommended for use.
-
-Parameter | Description | Recommended for use
-----------|-------------|--------------------
-`sslmode=disable` | Do not use an encrypted, secure connection at all. | Use during development.
-`sslmode=allow` | Enable a secure connection only if the server requires it.**Not supported in all clients.** | -`sslmode=prefer` | Try to establish a secure connection, but accept an insecure connection if the server does not support secure connections.
**Not supported in all clients.** | -`sslmode=require` | Force a secure connection. An error occurs if the secure connection cannot be established. | -`sslmode=verify-ca` | Force a secure connection and verify that the server certificate is signed by a known CA. | -`sslmode=verify-full` | Force a secure connection, verify that the server certificate is signed by a known CA, and verify that the server address matches that specified in the certificate. | Use for [secure deployments](secure-a-cluster.html). - -{{site.data.alerts.callout_danger}}Some client drivers and the -
cockroach commands do not support
-sslmode=allow and sslmode=prefer. Check the
-documentation of your SQL driver to determine whether these options
-are supported.{{site.data.alerts.end}}
-
-### Example URL for an Insecure Connection
-
-The following URL is suitable to connect to a CockroachDB node using an insecure connection:
-
-{% include_cached copy-clipboard.html %}
-~~~
-postgres://root@servername:26257/mydb?sslmode=disable
-~~~
-
-This specifies a connection for the `root` user to server `servername`
-on port 26257 (the default CockroachDB SQL port), with `mydb` set as
-current database. `sslmode=disable` makes the connection insecure.
-
-### Example URL for a Secure Connection
-
-The following URL is suitable to connect to a CockroachDB node using a secure connection:
-
-{% include_cached copy-clipboard.html %}
-~~~
-postgres://root@servername:26257/mydb?sslmode=verify-full&sslrootcert=path/to/ca.crt&sslcert=path/to/client.crt&sslkey=path/to/client.key
-~~~
-
-This uses the following components:
-
-- User `root`
-- Host name `servername`, port number 26257 (the default CockroachDB SQL port)
-- Current database `mydb`
-- SSL/TLS mode `verify-full`:
- - Root CA certificate `path/to/ca.crt`
- - Client certificate `path/to/client.crt`
- - Client key `path/to/client.key`
-
-For details about how to create and manage SSL/TLS certificates, see
-[Create Security Certificates](create-security-certificates.html) and
-[Rotate Certificates](rotate-certificates.html).
-
-## Connect Using Discrete Parameters
-
-Most [`cockroach` commands](cockroach-commands.html) accept connection
-parameters as separate, discrete command-line flags, in addition (or
-in replacement) to `--url` which [specifies all parameters as a
-URL](#connect-using-a-url).
-
-For each command-line flag that directs a connection parameter,
-CockroachDB also recognizes an environment variable. The environment
-variable is used when the command-line flag is not specified.
-
-{% include {{ page.version.version }}/sql/connection-parameters-with-url.md %}
-
-{{site.data.alerts.callout_info}}The command-line flag
---url is only supported for cockroach
-commands that use a SQL connection. See Supported Connection
-Parameters for details.{{site.data.alerts.end}}
-
-### Example Command-Line Flags for an Insecure Connection
-
-The following command-line flags establish an insecure connection:
-
-{% include_cached copy-clipboard.html %}
-~~~
---user root \
- --host servername \
- --port 26257 \
- --database mydb \
- --insecure
-~~~
-
-This specifies a connection for the `root` user to server `servername`
-on port 26257 (the default CockroachDB SQL port), with `mydb` set as
-current database. `--insecure` makes the connection insecure.
-
-### Example Command-Line Flags for a Secure Connection
-
-The following command-line flags establish a secure connection:
-
-{% include_cached copy-clipboard.html %}
-~~~
---user root \
- --host servername \
- --port 26257 \
- --database mydb \
- --certs-dir path/to/certs
-~~~
-
-This uses the following components:
-
-- User `root`
-- Host name `servername`, port number 26257 (the default CockroachDB SQL port)
-- Current database `mydb`
-- SSL/TLS enabled, with settings:
- - Root CA certificate `path/to/certs/ca.crt`
- - Client certificate `path/to/client.--certs-dir,
-and cannot be customized. To use customized file names, use a connection URL
-instead.{{site.data.alerts.end}}
-
-## See Also
-
-- [`cockroach` commands](cockroach-commands.html)
-- [Create Security Certificates](create-security-certificates.html)
-- [Secure a Cluster](secure-a-cluster.html)
-- [Create and Manage Users](create-and-manage-users.html)
diff --git a/src/current/v1.1/constraints.md b/src/current/v1.1/constraints.md
deleted file mode 100644
index 9a6392d832d..00000000000
--- a/src/current/v1.1/constraints.md
+++ /dev/null
@@ -1,115 +0,0 @@
----
-title: Constraints
-summary: Constraints offer additional data integrity by enforcing conditions on the data within a column.
-toc: true
----
-
-Constraints offer additional data integrity by enforcing conditions on the data within a column. Whenever values are manipulated (inserted, deleted, or updated), constraints are checked and modifications that violate constraints are rejected.
-
-For example, the Unique constraint requires that all values in a column be unique from one another (except *NULL* values). If you attempt to write a duplicate value, the constraint rejects the entire statement.
-
-
-## Supported Constraints
-
-| Constraint | Description |
-|------------|-------------|
-| [Check](check.html) | Values must return `TRUE` or `NULL` for a Boolean expression. |
-| [Default Value](default-value.html) | If a value is not defined for the constrained column in an `INSERT` statement, the Default Value is written to the column. |
-| [Foreign Keys](foreign-key.html) | Values must exactly match existing values from the column it references. |
-| [Not Null](not-null.html) | Values may not be *NULL*. |
-| [Primary Key](primary-key.html) | Values must uniquely identify each row *(one per table)*. This behaves as if the Not Null and Unique constraints are applied, as well as automatically creates an [index](indexes.html) for the table using the constrained columns. |
-| [Unique](unique.html) | Each non-*NULL* value must be unique. This also automatically creates an [index](indexes.html) for the table using the constrained columns. |
-
-## Using Constraints
-
-### Add Constraints
-
-How you add constraints depends on the number of columns you want to constrain, as well as whether or not the table is new.
-
-- **One column of a new table** has its constraints defined after the column's data type. For example, this statement applies the Primary Key constraint to `foo.a`:
-
- ``` sql
- > CREATE TABLE foo (a INT PRIMARY KEY);
- ```
-- **Multiple columns of a new table** have their constraints defined after the table's columns. For example, this statement applies the Primary Key constraint to `foo`'s columns `a` and `b`:
-
- ``` sql
- > CREATE TABLE bar (a INT, b INT, PRIMARY KEY (a,b));
- ```
-
- {{site.data.alerts.callout_info}}The Default Value and Not Null constraints cannot be applied to multiple columns.{{site.data.alerts.end}}
-
-- **Existing tables** can have the following constraints added:
- - **Check**, **Foreign Key**, and **Unique** constraints can be added through [`ALTER TABLE...ADD CONSTRAINT`](add-constraint.html). For example, this statement adds the Unique constraint to `baz.id`:
-
- ~~~ sql
- > ALTER TABLE baz ADD CONSTRAINT id_unique UNIQUE (id);
- ~~~
-
- - **Default Values** can be added through [`ALTER TABLE...ALTER COLUMN`](alter-column.html#set-or-change-a-default-value). For example, this statement adds the Default Value constraint to `baz.bool`:
-
- ~~~ sql
- > ALTER TABLE baz ALTER COLUMN bool SET DEFAULT true;
- ~~~
-
- - **Primary Key** and **Not Null** constraints cannot be added or changed. However, you can go through [this process](#table-migrations-to-add-or-change-immutable-constraints) to migrate data from your current table to a new table with the constraints you want to apply.
-
-#### Order of Constraints
-
-The order in which you list constraints is not important because constraints are applied to every modification of their respective tables or columns.
-
-#### Name Constraints on New Tables
-
-You can name constraints applied to new tables using the `CONSTRAINT` clause before defining the constraint:
-
-``` sql
-> CREATE TABLE foo (a INT CONSTRAINT another_name PRIMARY KEY);
-
-> CREATE TABLE bar (a INT, b INT, CONSTRAINT yet_another_name PRIMARY KEY (a,b));
-```
-
-### View Constraints
-
-To view a table's constraints, use [`SHOW CONSTRAINTS`](show-constraints.html) or [`SHOW CREATE TABLE`](show-create-table.html).
-
-### Remove Constraints
-
-The procedure for removing a constraint depends on its type:
-
-| Constraint Type | Procedure |
-|-----------------|-----------|
-| [Check](check.html) | Use [`DROP CONSTRAINT`](drop-constraint.html) |
-| [Default Value](default-value.html) | Use [`ALTER COLUMN`](alter-column.html#remove-default-constraint) |
-| [Foreign Keys](foreign-key.html) | Use [`DROP CONSTRAINT`](drop-constraint.html) |
-| [Not Null](not-null.html) | Use [`ALTER COLUMN`](alter-column.html#remove-not-null-constraint) |
-| [Primary Key](primary-key.html) | Primary Keys cannot be removed. However, you can move the table's data to a new table with [this process](#table-migrations-to-add-or-change-immutable-constraints). |
-| [Unique](unique.html) | The Unique constraint cannot be dropped directly. However, you can use [`DROP INDEX`](drop-index.html) to remove the index automatically created by the Unique constraint (whose name ends in `_key`) to remove the constraint. |
-
-### Change Constraints
-
-The procedure for changing a constraint depends on its type:
-
-| Constraint Type | Procedure |
-|-----------------|-----------|
-| [Check](check.html) | [Issue a transaction](transactions.html#syntax) that adds a new Check constraint ([`ADD CONSTRAINT`](add-constraint.html)), and then remove the existing one ([`DROP CONSTRAINT`](drop-constraint.html)). |
-| [Default Value](default-value.html) | The Default Value can be changed through [`ALTER COLUMN`](alter-column.html). |
-| [Foreign Keys](foreign-key.html) | [Issue a transaction](transactions.html#syntax) that adds a new Foreign Key constraint ([`ADD CONSTRAINT`](add-constraint.html)), and then remove the existing one ([`DROP CONSTRAINT`](drop-constraint.html)). |
-| [Not Null](not-null.html) | The Not Null constraint cannot be changed, only removed. However, you can move the table's data to a new table with [this process](#table-migrations-to-add-or-change-immutable-constraints). |
-| [Primary Key](primary-key.html) | Primary Keys cannot be modified. However, you can move the table's data to a new table with [this process](#table-migrations-to-add-or-change-immutable-constraints). |
-| [Unique](unique.html) | [Issue a transaction](transactions.html#syntax) that adds a new Unique constraint ([`ADD CONSTRAINT`](add-constraint.html)), and then remove the existing one ([`DROP CONSTRAINT`](drop-constraint.html)). |
-
-#### Table Migrations to Add or Change Immutable Constraints
-
-If you want to make a change to an immutable constraint, you can use the following process:
-
-1. [Create a new table](create-table.html) with the constraints you want to apply.
-2. Move the data from the old table to the new one using [`INSERT` from a `SELECT` statement](insert.html#insert-from-a-select-statement).
-3. [Drop the old table](drop-table.html), and then [rename the new table to the old name](rename-table.html). This cannot be done transactionally.
-
-## See Also
-
-- [`CREATE TABLE`](create-table.html)
-- [`ADD CONSTRAINT`](add-constraint.html)
-- [`DROP CONSTRAINT`](drop-constraint.html)
-- [`SHOW CONSTRAINTS`](show-constraints.html)
-- [`SHOW CREATE TABLE`](show-create-table.html)
diff --git a/src/current/v1.1/create-a-file-server.md b/src/current/v1.1/create-a-file-server.md
deleted file mode 100644
index ee1f0486b3b..00000000000
--- a/src/current/v1.1/create-a-file-server.md
+++ /dev/null
@@ -1,77 +0,0 @@
----
-title: Create a File Server for Imports and Backups
-summary: Learn how to create a simple file server for use with CockroachDB IMPORT and BACKUP
-toc: true
----
-
-If you need a location to store files for the [`IMPORT`](import.html) process or [CockroachDB enterprise backups](backup.html), but do not have access to (or simply cannot use) cloud storage providers, you can easily create your own file server. You can then use this file server by leveraging support for our HTTP Export Storage API.
-
-This is especially useful for:
-
-- Implementing a compatibility layer in front of custom or proprietary storage providers for which CockroachDB does not yet have built-in support
-- Using on-premises storage
-
-
-## HTTP Export Storage API
-
-CockroachDB tasks that require reading or writing external files (such as [`IMPORT`](import.html) and [`BACKUP`](backup.html)) can use the HTTP Export Storage API by prefacing the address with `http`, e.g., `http://fileserver/mnt/cockroach-exports`.
-
-This API uses the `GET`, `PUT` and `DELETE` methods. This behaves like you would expect typical HTTP requests to work. After a `PUT` request to some path, a subsequent `GET` request should return the content sent in the `PUT` request body, at least until a `DELETE` request is received for that path.
-
-## Examples
-
-You can use any file server software that supports `GET`, `PUT` and `DELETE` methods, but we've included code samples for common ones:
-
-- [Caddy](#using-caddy-as-a-file-server)
-- [nginx](#using-nginx-as-a-file-server)
-
-{{site.data.alerts.callout_info}}We do not recommend using any machines running cockroach as file servers. Using machines that are running cockroach as file servers could negatively impact performance if I/O operations exceed capacity.{{site.data.alerts.end}}
-
-### Using Caddy as a File Server
-
-1. [Download a `caddy` binary](https://caddyserver.com/download) that includes the `http.upload` plugin.
-
-2. Run `caddy` with an [`upload` directive](https://caddyserver.com/docs/http.upload), either in the command line or via [`Caddyfile`](https://caddyserver.com/docs/caddyfile).
- - Command line example (with no TLS):
-
- ~~~ shell
- caddy -root /mnt/cockroach-exports "upload / {" 'to "/mnt/cockroach-exports"' 'yes_without_tls' "}"
- ~~~
- - `Caddyfile` example (using a key and cert):
-
- ~~~ shell
- tls key cert
- root "/mnt/cockroach-exports"
- upload / {
- to "/mnt/cockroach-exports"
- }
- ~~~
-
-### Using nginx as a File Server
-
-1. Install `nginx` with the `webdav` module (often included in `-full` or similarly named packages in various distributions).
-
-2. In the `nginx.conf` file, add a `dav_methods PUT DELETE` directive. For example:
-
- ~~~ nginx
- events {
- worker_connections 1024;
- }
- http {
- server {
- listen 20150;
- location / {
- dav_methods PUT DELETE;
- root /mnt/cockroach-exports;
- sendfile on;
- sendfile_max_chunk 1m;
- }
- }
- }
- ~~~
-
-## See Also
-
-- [`IMPORT`](import.html)
-- [`BACKUP`](backup.html) (*Enterprise only*)
-- [`RESTORE`](restore.html) (*Enterprise only*)
diff --git a/src/current/v1.1/create-and-manage-users.md b/src/current/v1.1/create-and-manage-users.md
deleted file mode 100644
index 9765f062484..00000000000
--- a/src/current/v1.1/create-and-manage-users.md
+++ /dev/null
@@ -1,208 +0,0 @@
----
-title: Create & Manage Users
-summary: To create and manage your cluster's users (which lets you control SQL-level privileges), use the cockroach user command with appropriate flags.
-toc: true
----
-
-To create, manage, and remove your cluster's users (which lets you control SQL-level [privileges](privileges.html)), use the `cockroach user` [command](cockroach-commands.html) with appropriate flags.
-
-{{site.data.alerts.callout_success}}You can also use the CREATE USER and DROP USER statements to create and remove users.{{site.data.alerts.end}}
-
-
-## Considerations
-
-- Usernames are case-insensitive; must start with either a letter or underscore; must contain only letters, numbers, or underscores; and must be between 1 and 63 characters.
-- After creating users, you must [grant them privileges to databases and tables](grant.html).
-- On secure clusters, you must [create client certificates for users](create-security-certificates.html#create-the-certificate-and-key-pair-for-a-client) and users must [authenticate their access to the cluster](#user-authentication).
-- {% include {{ page.version.version }}/misc/remove-user-callout.html %}
-
-## Subcommands
-
-Subcommand | Usage
------------|------
-`get` | Retrieve a table containing a user and their hashed password.
-`ls` | List all users.
-`rm` | Remove a user.
-`set` | Create or update a user.
-
-## Synopsis
-
-~~~ shell
-# Create a user:
-$ cockroach user set When disabled with `--pretty=false`, or when the standard output is not a terminal, table rows are printed as tab-separated values, and special characters are escaped. This makes the output easy to parse by other programs.
**Default:** `true` when output is a terminal, `false` otherwise - -### Client Connection - -{% include {{ page.version.version }}/sql/connection-parameters-with-url.md %} - -See [Client Connection Parameters](connection-parameters.html) for more details. - -Currently, only the `root` user can create users. - -### Logging - -By default, the `user` command logs errors to `stderr`. - -If you need to troubleshoot this command's behavior, you can change its [logging behavior](debug-and-error-logs.html). - -## User Authentication - -Secure clusters require users to authenticate their access to databases and tables. CockroachDB offers two methods for this: - -- [Client certificate and key authentication](#secure-clusters-with-client-certificates), which is available to all users. To ensure the highest level of security, we recommend only using client certificate and key authentication. - -- [Password authentication](#secure-clusters-with-passwords), which is available to non-`root` users who you've created passwords for. To set a password for a non-`root` user, include the `--password` flag in the `cockroach user set` command. - - Users can use passwords to authenticate without supplying client certificates and keys; however, we recommend using certificate-based authentication whenever possible. - -{{site.data.alerts.callout_info}}Insecure clusters do not support user authentication, but you can still create passwords for users (besides
root) through the --password flag.{{site.data.alerts.end}}
-
-## Examples
-
-### Create a User
-
-#### Insecure Cluster
-
-~~~ shell
-$ cockroach user set jpointsman --insecure
-~~~
-
-Usernames are case-insensitive; must start with either a letter or underscore; must contain only letters, numbers, or underscores; and must be between 1 and 63 characters.
-
-After creating users, you must [grant them privileges to databases](grant.html).
-
-#### Secure Cluster
-
-~~~ shell
-$ cockroach user set jpointsman --certs-dir=certs
-~~~
-
-{{site.data.alerts.callout_success}}If you want to allow password authentication for the user, include the --password flag and then enter and confirm the password at the command prompt.{{site.data.alerts.end}}
-
-Usernames are case-insensitive; must start with either a letter or underscore; must contain only letters, numbers, or underscores; and must be between 1 and 63 characters.
-
-After creating users, you must:
-
-- [Create their client certificates](create-security-certificates.html#create-the-certificate-and-key-pair-for-a-client).
-- [Grant them privileges to databases](grant.html).
-
-### Authenticate as a Specific User
-
-#### Insecure Clusters
-
-~~~ shell
-$ cockroach sql --insecure --user=jpointsman
-~~~
-
-#### Secure Clusters with Client Certificates
-
-All users can authenticate their access to a secure cluster using [a client certificate](create-security-certificates.html#create-the-certificate-and-key-pair-for-a-client) issued to their username.
-
-~~~ shell
-$ cockroach sql --certs-dir=certs --user=jpointsman
-~~~
-
-#### Secure Clusters with Passwords
-
-[Users with passwords](create-and-manage-users.html#secure-cluster) can authenticate their access by entering their password at the command prompt instead of using their client certificate and key.
-
-If we cannot find client certificate and key files matching the user, we fall back on password authentication.
-
-~~~ shell
-$ cockroach sql --certs-dir=certs --user=jpointsman
-~~~
-
-### Update a User's Password
-
-~~~ shell
-$ cockroach user set jpointsman --certs-dir=certs --password
-~~~
-
-After issuing this command, enter and confirm the user's new password at the command prompt.
-
-{{site.data.alerts.callout_danger}}You cannot add password authentication to the root user.{{site.data.alerts.end}}
-
-### List All Users
-
-~~~ shell
-$ cockroach user ls --insecure
-~~~
-~~~
-+------------+
-| username |
-+------------+
-| jpointsman |
-+------------+
-~~~
-
-### Find a Specific User
-
-~~~ shell
-$ cockroach user get jpointsman --insecure
-~~~
-~~~
-+------------+--------------------------------------------------------------+
-| username | hashedPassword |
-+------------+--------------------------------------------------------------+
-| jpointsman | $2a$108tm5lYjES9RSXSKtQFLhNO.e/ysTXCBIRe7XeTgBrR6ubXfp6dDczS |
-+------------+--------------------------------------------------------------+
-~~~
-
-### Remove a User
-
-{{site.data.alerts.callout_danger}}{% include {{ page.version.version }}/misc/remove-user-callout.html %}{{site.data.alerts.end}}
-
-~~~ shell
-$ cockroach user rm jpointsman --insecure
-~~~
-
-{{site.data.alerts.callout_success}}You can also use the DROP USER SQL statement to remove users.{{site.data.alerts.end}}
-
-### Reveal the SQL statements sent implicitly by the command-line utility
-
-In this example, we use the `--echo-sql` flag to reveal the SQL statement sent implicitly by the command-line utility:
-
-~~~ shell
-$ cockroach user rm jpointsman --insecure --echo-sql
-~~~
-
-~~~
-> DELETE FROM system.users WHERE username=$1
-DELETE 1
-~~~
-
-## See Also
-
-- [`CREATE USER`](create-user.html)
-- [`DROP USER`](drop-user.html)
-- [`SHOW USERS`](show-users.html)
-- [`GRANT`](grant.html)
-- [`SHOW GRANTS`](show-grants.html)
-- [Create Security Certificates](create-security-certificates.html)
-- [Other Cockroach Commands](cockroach-commands.html)
diff --git a/src/current/v1.1/create-database.md b/src/current/v1.1/create-database.md
deleted file mode 100644
index e066a0e5baf..00000000000
--- a/src/current/v1.1/create-database.md
+++ /dev/null
@@ -1,105 +0,0 @@
----
-title: CREATE DATABASE
-summary: The CREATE DATABASE statement creates a new CockroachDB database.
-toc: true
----
-
-The `CREATE DATABASE` [statement](sql-statements.html) creates a new CockroachDB database.
-
-
-## Required Privileges
-
-Only the `root` user can create databases.
-
-## Synopsis
-
-{% include {{ page.version.version }}/sql/diagrams/create_database.html %}
-
-## Parameters
-
-Parameter | Description
-----------|------------
-`IF NOT EXISTS` | Create a new database only if a database of the same name does not already exist; if one does exist, do not return an error.
-`name` | The name of the database to create, which [must be unique](#create-fails-name-already-in-use) and follow these [identifier rules](keywords-and-identifiers.html#identifiers).
-`encoding` | The `CREATE DATABASE` statement accepts an optional `ENCODING` clause for compatibility with PostgreSQL, but `UTF-8` is the only supported encoding. The aliases `UTF8` and `UNICODE` are also accepted. Values should be enclosed in single quotes and are case-insensitive.Example: `CREATE DATABASE bank ENCODING = 'UTF-8'`. - -## Example - -### Create a Database - -~~~ sql -> CREATE DATABASE bank; -~~~ - -~~~ -> SHOW DATABASES; -~~~ - -~~~ -+----------+ -| Database | -+----------+ -| bank | -| system | -+----------+ -~~~ - -### Create Fails (Name Already In Use) - -~~~ sql -> SHOW DATABASES; -~~~ - -~~~ -+----------+ -| Database | -+----------+ -| bank | -| system | -+----------+ -~~~ - -~~~ sql -> CREATE DATABASE bank; -~~~ - -~~~ -pq: database "bank" already exists -~~~ - -~~~ sql -> SHOW DATABASES; -+----------+ -| Database | -+----------+ -| bank | -| system | -+----------+ -~~~ - -~~~ sql -> CREATE DATABASE IF NOT EXISTS bank; -~~~ - -SQL does not generate an error, but instead responds `CREATE DATABASE` even though a new database wasn't created. - -~~~ sql -> SHOW DATABASES; -~~~ - -~~~ -+----------+ -| Database | -+----------+ -| bank | -| system | -+----------+ -~~~ - -## See Also - -- [`SHOW DATABASES`](show-databases.html) -- [`RENAME DATABASE`](rename-database.html) -- [`SET DATABASE`](set-vars.html) -- [`DROP DATABASE`](drop-database.html) -- [Other SQL Statements](sql-statements.html) diff --git a/src/current/v1.1/create-index.md b/src/current/v1.1/create-index.md deleted file mode 100644 index 5693a772928..00000000000 --- a/src/current/v1.1/create-index.md +++ /dev/null @@ -1,129 +0,0 @@ ---- -title: CREATE INDEX -summary: The CREATE INDEX statement creates an index for a table. Indexes improve your database's performance by helping SQL quickly locate data. -toc: true ---- - -The `CREATE INDEX` [statement](sql-statements.html) creates an index for a table. [Indexes](indexes.html) improve your database's performance by helping SQL locate data without having to look through every row of a table. - -{{site.data.alerts.callout_info}}Indexes are automatically created for a table's
PRIMARY KEY and UNIQUE columns.When querying a table, CockroachDB uses the fastest index. For more information about that process, see Index Selection in CockroachDB.{{site.data.alerts.end}} - - -## Required Privileges - -The user must have the `CREATE` [privilege](privileges.html) on the table. - -## Synopsis - -{% include {{ page.version.version }}/sql/diagrams/create_index.html %} - -## Parameters - - - -| Parameter | Description | -|-----------|-------------| -|`UNIQUE` | Apply the [Unique constraint](unique.html) to the indexed columns.
This causes the system to check for existing duplicate values on index creation. It also applies the Unique constraint at the table level, so the system checks for duplicate values when inserting or updating data.| -|`IF NOT EXISTS` | Create a new index only if an index of the same name does not already exist; if one does exist, do not return an error.| -|`index_name` | The [`name`](sql-grammar.html#name) of the index to create, which must be unique to its table and follow these [identifier rules](keywords-and-identifiers.html#identifiers).
If you do not specify a name, CockroachDB uses the format `
-
-## Step 7. Add 3 nodes on "cloud 2"
-
-At this point, you're running three nodes on cloud 1. But what if you'd like to start experimenting with resources provided by another cloud vendor? Let's try that by adding three more nodes to a new cloud platform. Again, the flag to note is [`--locality`](configure-replication-zones.html#descriptive-attributes-assigned-to-nodes), which you're using to specify that these next 3 nodes are running on cloud 2.
-
-In a new terminal, start node 4 on cloud 2:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach start \
---insecure \
---locality=cloud=2 \
---store=cloud2node4 \
---host=localhost \
---port=26260 \
---http-port=8083 \
---cache=100MB \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-In a new terminal, start node 5 on cloud 2:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach start \
---insecure \
---locality=cloud=2 \
---store=cloud2node5 \
---host=localhost \
---port=25261 \
---http-port=8084 \
---cache=100MB \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-In a new terminal, start node 6 on cloud 2:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach start \
---insecure \
---locality=cloud=2 \
---store=cloud2node6 \
---host=localhost \
---port=25262 \
---http-port=8085 \
---cache=100MB \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-## Step 8. Watch data balance across all 6 nodes
-
-Back in the Admin UI, hover over the **Replicas per Node** graph again. Because you used [`--locality`](configure-replication-zones.html#descriptive-attributes-assigned-to-nodes) to specify that nodes are running on 2 clouds, you'll see an approximately even number of replicas on each node, indicating that CockroachDB has automatically rebalanced replicas across both simulated clouds:
-
-
-
-Note that it takes a few minutes for the Admin UI to show accurate per-node replica counts on hover. This is why the new nodes in the screenshot above show 0 replicas. However, the graph lines are accurate, and you can click **View node list** in the **Summary** area for accurate per-node replica counts as well.
-
-## Step 9. Migrate all data to "cloud 2"
-
-So your cluster is replicating across two simulated clouds. But let's say that after experimentation, you're happy with cloud vendor 2, and you decide that you'd like to move everything there. Can you do that without interruption to your live client traffic? Yes, and it's as simple as running a single command to add a [hard constraint](configure-replication-zones.html#replication-constraints) that all replicas must be on nodes with `--locality=cloud=2`.
-
-In a new terminal, edit the default replication zone:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ echo 'constraints: [+cloud=2]' | cockroach zone set .default --insecure --host=localhost -f -
-~~~
-
-## Step 10. Verify the data migration
-
-Back in the Admin UI, hover over the **Replicas per Node** graph again. Very soon, you'll see the replica count double on nodes 4, 5, and 6 and drop to 0 on nodes 1, 2, and 3:
-
-
-
-This indicates that all data has been migrated from cloud 1 to cloud 2. In a real cloud migration scenario, at this point you would update the load balancer to point to the nodes on cloud 2 and then stop the nodes on cloud 1. But for the purpose of this local simulation, there's no need to do that.
-
-## Step 11. Stop the cluster
-
-Once you're done with your cluster, stop YCSB by switching into its terminal and pressing **CTRL-C**. Then do the same for HAProxy and each CockroachDB node.
-
-{{site.data.alerts.callout_success}}For the last node, the shutdown process will take longer (about a minute) and will eventually force stop the node. This is because, with only 1 node still online, a majority of replicas are no longer available (2 of 3), and so the cluster is not operational. To speed up the process, press CTRL-C a second time.{{site.data.alerts.end}}
-
-If you do not plan to restart the cluster, you may want to remove the nodes' data stores and the HAProxy config file:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ rm -rf cloud1node1 cloud1node2 cloud1node3 cloud2node4 cloud2node5 cloud2node6 haproxy.cfg
-~~~
-
-## What's Next?
-
-Use a local cluster to explore these other core CockroachDB benefits:
-
-- [Data Replication](demo-data-replication.html)
-- [Fault Tolerance & Recovery](demo-fault-tolerance-and-recovery.html)
-- [Automatic Rebalancing](demo-automatic-rebalancing.html)
-- [Follow-the-Workload](demo-follow-the-workload.html)
-- [Orchestration](orchestrate-a-local-cluster-with-kubernetes-insecure.html)
-
-You may also want to learn other ways to control the location and number of replicas in a cluster:
-
-- [Even Replication Across Datacenters](configure-replication-zones.html#even-replication-across-datacenters)
-- [Multiple Applications Writing to Different Databases](configure-replication-zones.html#multiple-applications-writing-to-different-databases)
-- [Stricter Replication for a Specific Table](configure-replication-zones.html#stricter-replication-for-a-specific-table)
-- [Tweaking the Replication of System Ranges](configure-replication-zones.html#tweaking-the-replication-of-system-ranges)
diff --git a/src/current/v1.1/demo-automatic-rebalancing.md b/src/current/v1.1/demo-automatic-rebalancing.md
deleted file mode 100644
index 24967dbf0e2..00000000000
--- a/src/current/v1.1/demo-automatic-rebalancing.md
+++ /dev/null
@@ -1,211 +0,0 @@
----
-title: Automatic Rebalancing
-summary: Use a local cluster to explore how CockroachDB automatically rebalances data as you scale.
-toc: true
----
-
-This page walks you through a simple demonstration of how CockroachDB automatically rebalances data as you scale. Starting with a 3-node local cluster, you'll lower the maximum size for a single range, the unit of data that is replicated in CockroachDB. You'll then download and run the `block_writer` example program, which continuously inserts data into your cluster, and watch the replica count quickly increase as ranges split. You'll then add 2 more nodes and watch how CockroachDB automatically rebalances replicas to efficiently use all available capacity.
-
-
-## Before You Begin
-
-In this tutorial, you'll use an example Go program to quickly insert data into a CockroachDB cluster. To run the example program, you must have a [Go environment](http://golang.org/doc/code.html) with a 64-bit version of Go 1.7.1.
-
-- You can download the [Go binary](http://golang.org/doc/code.html) directly from the official site.
-- Be sure to set the `$GOPATH` and `$PATH` environment variables as described [here](https://golang.org/doc/code.html#GOPATH).
-
-## Step 1. Start a 3-node cluster
-
-Use the [`cockroach start`](start-a-node.html) command to start 3 nodes:
-
-{% include copy-clipboard.html %}
-~~~ shell
-# In a new terminal, start node 1:
-$ cockroach start --insecure \
---store=scale-node1 \
---host=localhost \
---port=26257 \
---http-port=8080 \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-{% include copy-clipboard.html %}
-~~~ shell
-# In a new terminal, start node 2:
-$ cockroach start --insecure \
---store=scale-node2 \
---host=localhost \
---port=26258 \
---http-port=8081 \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-{% include copy-clipboard.html %}
-~~~ shell
-# In a new terminal, start node 3:
-$ cockroach start --insecure \
---store=scale-node3 \
---host=localhost \
---port=26259 \
---http-port=8082 \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-## Step 2. Initial the cluster
-
-In a new terminal, use the [`cockroach init`](initialize-a-cluster.html) command to perform a one-time initialization of the cluster:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach init \
---insecure \
---host=localhost \
---port=26257
-~~~
-
-## Step 3. Verify that the cluster is live
-
-In a new terminal, connect the [built-in SQL shell](use-the-built-in-sql-client.html) to any node to verify that the cluster is live:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach sql --insecure --port=26257
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SHOW DATABASES;
-~~~
-
-~~~
-+--------------------+
-| Database |
-+--------------------+
-| crdb_internal |
-| information_schema |
-| pg_catalog |
-| system |
-+--------------------+
-(4 rows)
-~~~
-
-Exit the SQL shell:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> \q
-~~~
-
-## Step 4. Lower the max range size
-
-In CockroachDB, you use [replication zones](configure-replication-zones.html) to control the number and location of replicas. Initially, there is a single default replication zone for the entire cluster that is set to copy each range of data 3 times. This default replication factor is fine for this demo.
-
-However, the default replication zone also defines the size at which a single range of data spits into two ranges. Since you want to create many ranges quickly and then see how CockroachDB automatically rebalances them, reduce the max range size from the default 67108864 bytes (64MB) to cause ranges to split more quickly:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ echo -e "range_min_bytes: 1\nrange_max_bytes: 262144" | cockroach zone set .default --insecure -f -
-~~~
-
-~~~
-range_min_bytes: 1
-range_max_bytes: 262144
-gc:
- ttlseconds: 86400
-num_replicas: 3
-constraints: []
-~~~
-
-## Step 5. Download and run the `block_writer` program
-
-CockroachDB provides a number of [example programs in Go](https://github.com/cockroachdb/examples-go) for simulating client workloads. The program you'll use for this demonstration is called [`block_writer`](https://github.com/cockroachdb/examples-go/tree/master/block_writer). It will simulate multiple clients inserting data into the cluster.
-
-Download and install the program:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ go get github.com/cockroachdb/examples-go/block_writer
-~~~
-
-Then run the program for 1 minute, long enough to generate plenty of ranges:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ block_writer -duration 1m
-~~~
-
-Once it's running, `block_writer` will output the number of rows written per second:
-
-~~~
- 1s: 776.7/sec 776.7/sec
- 2s: 696.3/sec 736.7/sec
- 3s: 659.9/sec 711.1/sec
- 4s: 557.4/sec 672.6/sec
- 5s: 485.0/sec 635.1/sec
- 6s: 563.5/sec 623.2/sec
- 7s: 725.2/sec 637.7/sec
- 8s: 779.2/sec 655.4/sec
- 9s: 859.0/sec 678.0/sec
-10s: 960.4/sec 706.1/sec
-~~~
-
-## Step 6. Watch the replica count increase
-
-Open the Admin UI at `http://localhost:8080`, click **View nodes list** on the right, and you’ll see the bytes, replica count, and other metrics increase as the `block_writer` program inserts data.
-
-
-
-## Step 7. Add 2 more nodes
-
-Adding capacity is as simple as starting more nodes and joining them to the running cluster:
-
-{% include copy-clipboard.html %}
-~~~ shell
-# In a new terminal, start node 4:
-$ cockroach start --insecure \
---store=scale-node4 \
---host=localhost \
---port=26260 \
---http-port=8083 \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-{% include copy-clipboard.html %}
-~~~ shell
-# In a new terminal, start node 5:
-$ cockroach start --insecure \
---store=scale-node5 \
---host=localhost \
---port=26261 \
---http-port=8084 \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-## Step 8. Watch data rebalance across all 5 nodes
-
-Back in the Admin UI, you'll now see 5 nodes listed. At first, the bytes and replica count will be lower for nodes 4 and 5. Very soon, however, you'll see those metrics even out across all nodes, indicating that data has been automatically rebalanced to utilize the additional capacity of the new nodes.
-
-
-
-## Step 9. Stop the cluster
-
-Once you're done with your test cluster, stop each node by switching to its terminal and pressing **CTRL-C**.
-
-{{site.data.alerts.callout_success}}For the last node, the shutdown process will take longer (about a minute) and will eventually force stop the node. This is because, with only 1 node still online, a majority of replicas are no longer available (2 of 3), and so the cluster is not operational. To speed up the process, press CTRL-C a second time.{{site.data.alerts.end}}
-
-If you do not plan to restart the cluster, you may want to remove the nodes' data stores:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ rm -rf scale-node1 scale-node2 scale-node3 scale-node4 scale-node5
-~~~
-
-## What's Next?
-
-Use a local cluster to explore these other core CockroachDB benefits:
-
-- [Data Replication](demo-data-replication.html)
-- [Fault Tolerance & Recovery](demo-fault-tolerance-and-recovery.html)
-- [Cross-Cloud Migration](demo-automatic-cloud-migration.html)
-- [Follow-the-Workload](demo-follow-the-workload.html)
-- [Orchestration](orchestrate-a-local-cluster-with-kubernetes-insecure.html)
diff --git a/src/current/v1.1/demo-data-replication.md b/src/current/v1.1/demo-data-replication.md
deleted file mode 100644
index d0b340643d4..00000000000
--- a/src/current/v1.1/demo-data-replication.md
+++ /dev/null
@@ -1,236 +0,0 @@
----
-title: Data Replication
-summary: Use a local cluster to explore how CockroachDB replicates and distributes data.
-toc: true
----
-
-This page walks you through a simple demonstration of how CockroachDB replicates and distributes data. Starting with a 1-node local cluster, you'll write some data, add 2 nodes, and watch how the data is replicated automatically. You'll then update the cluster to replicate 5 ways, add 2 more nodes, and again watch how all existing replicas are re-replicated to the new nodes.
-
-
-## Before You Begin
-
-Make sure you have already [installed CockroachDB](install-cockroachdb.html).
-
-## Step 1. Start a 1-node cluster
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach start \
---insecure \
---store=repdemo-node1 \
---host=localhost
-~~~
-
-## Step 2. Write data
-
-In a new terminal, use the [`cockroach gen`](generate-cockroachdb-resources.html) command to generate an example `intro` database:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach gen example-data intro | cockroach sql --insecure
-~~~
-
-~~~
-CREATE DATABASE
-SET
-DROP TABLE
-CREATE TABLE
-INSERT 1
-INSERT 1
-INSERT 1
-INSERT 1
-...
-~~~
-
-In the same terminal, open the [built-in SQL shell](use-the-built-in-sql-client.html) and verify that the new `intro` database was added with one table, `mytable`:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach sql --insecure
-~~~
-
-~~~
-# Welcome to the cockroach SQL interface.
-# All statements must be terminated by a semicolon.
-# To exit: CTRL + D.
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SHOW DATABASES;
-~~~
-
-~~~
-+--------------------+
-| Database |
-+--------------------+
-| information_schema |
-| pg_catalog |
-| intro |
-| system |
-+--------------------+
-(4 rows)
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SHOW TABLES FROM intro;
-~~~
-
-~~~
-+---------+
-| Table |
-+---------+
-| mytable |
-+---------+
-(1 row)
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SELECT * FROM intro.mytable WHERE (l % 2) = 0;
-~~~
-
-~~~
-+----+-----------------------------------------------------+
-| l | v |
-+----+-----------------------------------------------------+
-| 0 | !__aaawwmqmqmwwwaas,,_ .__aaawwwmqmqmwwaaa,, |
-| 2 | !"VT?!"""^~~^"""??T$Wmqaa,_auqmWBT?!"""^~~^^""??YV^ |
-| 4 | ! "?##mW##?"- |
-| 6 | ! C O N G R A T S _am#Z??A#ma, Y |
-| 8 | ! _ummY" "9#ma, A |
-| 10 | ! vm#Z( )Xmms Y |
-| 12 | ! .j####mmm#####mm#m##6. |
-| 14 | ! W O W ! jmm###mm######m#mmm##6 |
-| 16 | ! ]#me*Xm#m#mm##m#m##SX##c |
-| 18 | ! dm#||+*$##m#mm#m#Svvn##m |
-| 20 | ! :mmE=|+||S##m##m#1nvnnX##; A |
-| 22 | ! :m#h+|+++=Xmm#m#1nvnnvdmm; M |
-| 24 | ! Y $#m>+|+|||##m#1nvnnnnmm# A |
-| 26 | ! O ]##z+|+|+|3#mEnnnnvnd##f Z |
-| 28 | ! U D 4##c|+|+|]m#kvnvnno##P E |
-| 30 | ! I 4#ma+|++]mmhvnnvq##P` ! |
-| 32 | ! D I ?$#q%+|dmmmvnnm##! |
-| 34 | ! T -4##wu#mm#pw##7' |
-| 36 | ! -?$##m####Y' |
-| 38 | ! !! "Y##Y"- |
-| 40 | ! |
-+----+-----------------------------------------------------+
-(21 rows)
-~~~
-
-Exit the SQL shell:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> \q
-~~~
-
-## Step 3. Add two nodes
-
-In a new terminal, add node 2:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach start \
---insecure \
---store=repdemo-node2 \
---host=localhost \
---port=26258 \
---http-port=8081 \
---join=localhost:26257
-~~~
-
-In a new terminal, add node 3:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach start \
---insecure \
---store=repdemo-node3 \
---host=localhost \
---port=26259 \
---http-port=8082 \
---join=localhost:26257
-~~~
-
-## Step 4. Watch data replicate to the new nodes
-
-Open the Admin UI at `http://localhost:8080` and click **View nodes list** on the right. You'll see that all three nodes are listed. At first, the replica count will be lower for nodes 2 and 3. Very soon, the replica count will be identical across all three nodes, indicating that all data in the cluster has been replicated 3 times; there's a copy of every piece of data on each node.
-
-
-
-## Step 5. Increase the replication factor
-
-As you just saw, CockroachDB replicates data 3 times by default. Now, in the terminal you used for the built-in SQL shell or in a new terminal, edit the default [replication zone](configure-replication-zones.html) to replicate data 5 times:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ echo 'num_replicas: 5' | cockroach zone set .default --insecure -f -
-~~~
-
-~~~
-range_min_bytes: 1048576
-range_max_bytes: 67108864
-gc:
- ttlseconds: 86400
-num_replicas: 5
-constraints: []
-~~~
-
-## Step 6. Add two more nodes
-
-In a new terminal, add node 4:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach start --insecure \
---host=localhost \
---store=repdemo-node4 \
---port=26260 \
---http-port=8083 \
---join=localhost:26257
-~~~
-
-In a new terminal, add node 5:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach start \
---insecure \
---host=localhost \
---store=repdemo-node5 \
---port=26261 \
---http-port=8084 \
---join=localhost:26257
-~~~
-
-## Step 7. Watch data replicate to the new nodes
-
-Back in the Admin UI, you'll see that there are now 5 nodes listed. Again, at first, the replica count will be lower for nodes 4 and 5. But because you changed the default replication factor to 5, very soon, the replica count will be identical across all 5 nodes, indicating that all data in the cluster has been replicated 5 times.
-
-
-
-## Step 8. Stop the cluster
-
-Once you're done with your test cluster, stop each node by switching to its terminal and pressing **CTRL-C**.
-
-{{site.data.alerts.callout_success}}For the last 2 nodes, the shutdown process will take longer (about a minute) and will eventually force stop the nodes. This is because, with only 2 nodes still online, a majority of replicas are no longer available (3 of 5), and so the cluster is not operational. To speed up the process, press CTRL-C a second time in the nodes' terminals.{{site.data.alerts.end}}
-
-If you do not plan to restart the cluster, you may want to remove the nodes' data stores:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ rm -rf repdemo-node1 repdemo-node2 repdemo-node3 repdemo-node4 repdemo-node5
-~~~
-
-## What's Next?
-
-Use a local cluster to explore these other core CockroachDB benefits:
-
-- [Fault Tolerance & Recovery](demo-fault-tolerance-and-recovery.html)
-- [Automatic Rebalancing](demo-automatic-rebalancing.html)
-- [Cross-Cloud Migration](demo-automatic-cloud-migration.html)
-- [Follow-the-Workload](demo-follow-the-workload.html)
-- [Orchestration](orchestrate-a-local-cluster-with-kubernetes-insecure.html)
diff --git a/src/current/v1.1/demo-fault-tolerance-and-recovery.md b/src/current/v1.1/demo-fault-tolerance-and-recovery.md
deleted file mode 100644
index f8b29177beb..00000000000
--- a/src/current/v1.1/demo-fault-tolerance-and-recovery.md
+++ /dev/null
@@ -1,381 +0,0 @@
----
-title: Fault Tolerance & Recovery
-summary: Use a local cluster to explore how CockroachDB remains available during, and recovers after, failure.
-toc: true
----
-
-This page walks you through a simple demonstration of how CockroachDB remains available during, and recovers after, failure. Starting with a 3-node local cluster, you'll remove a node and see how the cluster continues uninterrupted. You'll then write some data while the node is offline, rejoin the node, and see how it catches up with the rest of the cluster. Finally, you'll add a fourth node, remove a node again, and see how missing replicas eventually re-replicate to the new node.
-
-
-## Before You Begin
-
-Make sure you have already [installed CockroachDB](install-cockroachdb.html).
-
-## Step 1. Start a 3-node cluster
-
-Use the [`cockroach start`](start-a-node.html) command to start 3 nodes:
-
-{% include copy-clipboard.html %}
-~~~ shell
-# In a new terminal, start node 1:
-$ cockroach start \
---insecure \
---store=fault-node1 \
---host=localhost \
---port=26257 \
---http-port=8080 \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-{% include copy-clipboard.html %}
-~~~ shell
-# In a new terminal, start node 2:
-$ cockroach start \
---insecure \
---store=fault-node2 \
---host=localhost \
---port=26258 \
---http-port=8081 \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-{% include copy-clipboard.html %}
-~~~ shell
-# In a new terminal, start node 3:
-$ cockroach start \
---insecure \
---store=fault-node3 \
---host=localhost \
---port=26259 \
---http-port=8082 \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-## Step 2. Initialize the cluster
-
-In a new terminal, use the [`cockroach init`](initialize-a-cluster.html) command to perform a one-time initialization of the cluster:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach init \
---insecure \
---host=localhost \
---port=26257
-~~~
-
-## Step 3. Verify that the cluster is live
-
-In a new terminal, use the [`cockroach sql`](use-the-built-in-sql-client.html) command to connect the built-in SQL shell to any node:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach sql --insecure --port=26257
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SHOW DATABASES;
-~~~
-
-~~~
-+--------------------+
-| Database |
-+--------------------+
-| crdb_internal |
-| information_schema |
-| pg_catalog |
-| system |
-+--------------------+
-(4 rows)
-~~~
-
-Exit the SQL shell:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> \q
-~~~
-
-## Step 4. Remove a node temporarily
-
-In the terminal running node 2, press **CTRL-C** to stop the node.
-
-Alternatively, you can open a new terminal and run the [`cockroach quit`](stop-a-node.html) command against port `26258`:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach quit --insecure --port=26258
-~~~
-
-~~~
-initiating graceful shutdown of server
-ok
-~~~
-
-## Step 5. Verify that the cluster remains available
-
-Switch to the terminal for the built-in SQL shell and reconnect the shell to node 1 (port `26257`) or node 3 (port `26259`):
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach sql --insecure --port=26259
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SHOW DATABASES;
-~~~
-
-~~~
-+--------------------+
-| Database |
-+--------------------+
-| information_schema |
-| pg_catalog |
-| bank |
-| system |
-+--------------------+
-(4 rows)
-~~~
-
-As you see, despite one node being offline, the cluster continues uninterrupted because a majority of replicas (2/3) remains available. If you were to remove another node, however, leaving only one node live, the cluster would be unresponsive until another node was brought back online.
-
-Exit the SQL shell:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> \q
-~~~
-
-## Step 6. Write data while the node is offline
-
-In the same terminal, use the [`cockroach gen`](generate-cockroachdb-resources.html) command to generate an example `startrek` database:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach gen example-data startrek | cockroach sql --insecure
-~~~
-
-~~~
-CREATE DATABASE
-SET
-DROP TABLE
-DROP TABLE
-CREATE TABLE
-INSERT 79
-CREATE TABLE
-INSERT 200
-~~~
-
-Then reconnect the SQL shell to node 1 (port `26257`) or node 3 (port `26259`) and verify that the new `startrek` database was added with two tables, `episodes` and `quotes`:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach sql --insecure --port=26259
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SHOW DATABASES;
-~~~
-
-~~~
-+--------------------+
-| Database |
-+--------------------+
-| crdb_internal |
-| information_schema |
-| pg_catalog |
-| startrek |
-| system |
-+--------------------+
-(5 rows)
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SHOW TABLES FROM startrek;
-~~~
-
-~~~
-+----------+
-| Table |
-+----------+
-| episodes |
-| quotes |
-+----------+
-(2 rows)
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SELECT * FROM startrek.episodes LIMIT 10;
-~~~
-
-~~~
-+----+--------+-----+--------------------------------+----------+
-| id | season | num | title | stardate |
-+----+--------+-----+--------------------------------+----------+
-| 1 | 1 | 1 | The Man Trap | 1531.1 |
-| 2 | 1 | 2 | Charlie X | 1533.6 |
-| 3 | 1 | 3 | Where No Man Has Gone Before | 1312.4 |
-| 4 | 1 | 4 | The Naked Time | 1704.2 |
-| 5 | 1 | 5 | The Enemy Within | 1672.1 |
-| 6 | 1 | 6 | Mudd's Women | 1329.8 |
-| 7 | 1 | 7 | What Are Little Girls Made Of? | 2712.4 |
-| 8 | 1 | 8 | Miri | 2713.5 |
-| 9 | 1 | 9 | Dagger of the Mind | 2715.1 |
-| 10 | 1 | 10 | The Corbomite Maneuver | 1512.2 |
-+----+--------+-----+--------------------------------+----------+
-(10 rows)
-~~~
-
-Exit the SQL shell:
-
-{% include copy-clipboard.html %}
-~~~ sql
-> \q
-~~~
-
-## Step 7. Rejoin the node to the cluster
-
-Switch to the terminal for node 2, and rejoin the node to the cluster, using the same command that you used in step 1:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach start --insecure \
---store=fault-node2 \
---host=localhost \
---port=26258 \
---http-port=8081 \
---join=localhost:26257
-~~~
-
-~~~
-CockroachDB node starting at {{ now | date: "%Y-%m-%d %H:%M:%S.%6 +0000 UTC" }}
-build: CCL {{page.release_info.version}} @ {{page.release_info.build_time}}
-admin: http://localhost:8081
-sql: postgresql://root@localhost:26258?sslmode=disable
-logs: node2/logs
-store[0]: path=fault-node2
-status: restarted pre-existing node
-clusterID: {5638ba53-fb77-4424-ada9-8a23fbce0ae9}
-nodeID: 2
-~~~
-
-## Step 8. Verify that the rejoined node has caught up
-
-Switch to the terminal for the built-in SQL shell, connect the shell to the rejoined node 2 (port `26258`), and check for the `startrek` data that was added while the node was offline:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach sql --insecure --port=26258
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SELECT * FROM startrek.episodes LIMIT 10;
-~~~
-
-~~~
-+----+--------+-----+--------------------------------+----------+
-| id | season | num | title | stardate |
-+----+--------+-----+--------------------------------+----------+
-| 1 | 1 | 1 | The Man Trap | 1531.1 |
-| 2 | 1 | 2 | Charlie X | 1533.6 |
-| 3 | 1 | 3 | Where No Man Has Gone Before | 1312.4 |
-| 4 | 1 | 4 | The Naked Time | 1704.2 |
-| 5 | 1 | 5 | The Enemy Within | 1672.1 |
-| 6 | 1 | 6 | Mudd's Women | 1329.8 |
-| 7 | 1 | 7 | What Are Little Girls Made Of? | 2712.4 |
-| 8 | 1 | 8 | Miri | 2713.5 |
-| 9 | 1 | 9 | Dagger of the Mind | 2715.1 |
-| 10 | 1 | 10 | The Corbomite Maneuver | 1512.2 |
-+----+--------+-----+--------------------------------+----------+
-(10 rows)
-~~~
-
-At first, while node 2 is catching up, it acts as a proxy to one of the other nodes with the data. This shows that even when a copy of the data is not local to the node, it has seamless access.
-
-Soon enough, node 2 catches up entirely. To verify, open the Admin UI at `http://localhost:8080`, click **View nodes list** on the right, and you'll see that all three nodes are listed, and the replica count is identical for each. This means that all data in the cluster has been replicated 3 times; there's a copy of every piece of data on each node.
-
-{{site.data.alerts.callout_success}}CockroachDB replicates data 3 times by default. You can customize the number and location of replicas for the entire cluster or for specific sets of data using 
-
-## Step 9. Add another node
-
-Now, to prepare the cluster for a permanent node failure, open a new terminal and add a fourth node:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach start \
---insecure \
---store=fault-node4 \
---host=localhost \
---port=26260 \
---http-port=8083 \
---join=localhost:26257,localhost:26258,localhost:26259
-~~~
-
-~~~
-CockroachDB node starting at {{ now | date: "%Y-%m-%d %H:%M:%S.%6 +0000 UTC" }}
-build: CCL {{page.release_info.version}} @ {{page.release_info.build_time}}
-admin: http://localhost:8083
-sql: postgresql://root@localhost:26260?sslmode=disable
-logs: node4/logs
-store[0]: path=fault-node4
-status: initialized new node, joined pre-existing cluster
-clusterID: {5638ba53-fb77-4424-ada9-8a23fbce0ae9}
-nodeID: 4
-~~~
-
-## Step 10. Remove a node permanently
-
-Again, switch to the terminal running node 2 and press **CTRL-C** to stop it.
-
-Alternatively, you can open a new terminal and run the [`cockroach quit`](stop-a-node.html) command against port `26258`:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach quit --insecure --port=26258
-~~~
-
-~~~
-initiating graceful shutdown of server
-ok
-server drained and shutdown completed
-~~~
-
-## Step 11. Verify that the cluster re-replicates missing replicas
-
-Back in the Admin UI, you'll see 4 nodes listed. After about 1 minute, the dot next to node 2 will turn yellow, indicating that the node is not responding.
-
-
-
-After about 10 minutes, node 2 will move into a **Dead Nodes** section, indicating that the node is not expected to come back. At this point, in the **Live Nodes** section, you should also see that the **Replicas** count for node 4 matches the count for node 1 and 3, the other live nodes. This indicates that all missing replicas (those that were on node 2) have been re-replicated to node 4.
-
-
-
-## Step 12. Stop the cluster
-
-Once you're done with your test cluster, stop each node by switching to its terminal and pressing **CTRL-C**.
-
-{{site.data.alerts.callout_success}}For the last node, the shutdown process will take longer (about a minute) and will eventually force stop the node. This is because, with only 1 node still online, a majority of replicas are no longer available (2 of 3), and so the cluster is not operational. To speed up the process, press CTRL-C a second time.{{site.data.alerts.end}}
-
-If you do not plan to restart the cluster, you may want to remove the nodes' data stores:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ rm -rf fault-node1 fault-node2 fault-node3 fault-node4 fault-node5
-~~~
-
-## What's Next?
-
-Use a local cluster to explore these other core CockroachDB benefits:
-
-- [Data Replication](demo-data-replication.html)
-- [Automatic Rebalancing](demo-automatic-rebalancing.html)
-- [Cross-Cloud Migration](demo-automatic-cloud-migration.html)
-- [Follow-the-Workload](demo-follow-the-workload.html)
-- [Orchestration](orchestrate-a-local-cluster-with-kubernetes-insecure.html)
diff --git a/src/current/v1.1/demo-follow-the-workload.md b/src/current/v1.1/demo-follow-the-workload.md
deleted file mode 100644
index e8a19558c29..00000000000
--- a/src/current/v1.1/demo-follow-the-workload.md
+++ /dev/null
@@ -1,296 +0,0 @@
----
-title: Follow-the-Workload
-summary: CockroachDB can dynamically optimize read latency for the location from which most of the workload is originating.
-toc: true
----
-
-"Follow-the-workload" refers to CockroachDB's ability to dynamically optimize read latency for the location from which most of the workload is originating. This page explains how "follow-the-workload" works and walks you through a simple demonstration using a local cluster.
-
-
-## Overview
-
-### Basic Terms
-
-To understand how "follow-the-workload" works, it's important to start with some basic terms:
-
-Term | Description
------|------------
-**Range** | CockroachDB stores all user data and almost all system data in a giant sorted map of key-value pairs. This keyspace is divided into "ranges", contiguous chunks of the keyspace, so that every key can always be found in a single range.
-**Range Replica** | CockroachDB replicates each range (3 times by default) and stores each replica on a different node.
-**Range Lease** | 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.
-
-### How It Works
-
-"Follow-the-workload" is based on the way **range leases** handle read requests. Read requests bypass the Raft consensus protocol, accessing the range replica that holds the range lease (the leaseholder) and sending the results to the client without needing to coordinate with any of the other range replicas. Bypassing Raft, and the network round trips involved, 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.
-
-This increases the speed of reads, but it doesn't guarantee that the range lease will be anywhere close to the origin of requests. If requests are coming from the US West, for example, and the relevant range lease is on a node in the US East, the requests would likely enter a gateway node in the US West and then get routed to the node with the range lease in the US East.
-
-However, you can cause the cluster to actively move range leases for even better read performance by starting each node with the [`--locality`](start-a-node.html#locality) flag. With this flag specified, the cluster knows about the location of each node, so when there's high latency between nodes, the cluster will move active range leases to a node closer to the origin of the majority of the workload. This is especially helpful for applications with workloads that move around throughout the day (e.g., most of the traffic is in the US East in the morning and in the US West in the evening).
-
-{{site.data.alerts.callout_success}}To enable "follow-the-workload", you just need to start each node of the cluster with the 
-
-However, if the nodes were started with the [`--locality`](start-a-node.html#locality) flag, after a short while, the cluster would move range 3's lease to node 1, which is closer to the origin of the workload, thus reducing the network round trips and increasing the speed of reads.
-
-
-
-## Tutorial
-
-### Step 1. Install prerequisites
-
-In this tutorial, you'll use CockroachDB, the `comcast` network tool to simulate network latency on your local workstation, and the `kv` load generator to simulate client workloads. Before you begin, make sure these applications are installed:
-
-- Install the latest version of [CockroachDB](install-cockroachdb.html).
-- Install [Go](https://golang.org/doc/install) version 1.9 or higher. If you're on a Mac and using Homebrew, use `brew install go`. You can check your local version by running `go version`.
-- Install the [`comcast`](https://github.com/tylertreat/comcast) network simulation tool: `go get github.com/tylertreat/comcast`
-- Install the [`kv`](https://github.com/cockroachdb/loadgen/tree/master/kv) load generator: `go get github.com/cockroachdb/loadgen/kv`
-
-Also, to keep track of the data files and logs for your cluster, you may want to create a new directory (e.g., `mkdir follow-workload`) and start all your nodes in that directory.
-
-### Step 2. Start simulating network latency
-
-"Follow-the-workload" only kicks in when there's high latency between the nodes of the CockroachDB cluster. In this tutorial, you'll run 3 nodes on your local workstation, with each node pretending to be in a different region of the US. To simulate latency between the nodes, use the `comcast` tool that you installed earlier.
-
-In a new terminal, start `comcast` as follows:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ comcast --device lo0 --latency 100
-~~~
-
-For the `--device` flag, use `lo0` if you're on Mac or `lo` if you're on Linux. If neither works, run the `ifconfig` command and find the interface responsible for `127.0.0.1` in the output.
-
-This command causes a 100 millisecond delay for all requests on the loopback interface of your local workstation. It will only affect connections from the machine to itself, not to/from the Internet.
-
-### Step 3. Start the cluster
-
-Use the [`cockroach start`](start-a-node.html) command to start 3 nodes on your local workstation, using the [`--locality`](start-a-node.html#locality) flag to pretend that each node is in a different region of the US.
-
-1. In a new terminal, start a node in the "US West":
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ cockroach start \
- --insecure \
- --locality=region=us-west \
- --host=localhost \
- --store=follow1 \
- --port=26257 \
- --http-port=8080 \
- --join=localhost:26257,localhost:26258,localhost:26259
- ~~~
-
-2. In a new terminal, start a node in the "US Midwest":
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ cockroach start \
- --insecure \
- --locality=region=us-midwest \
- --host=localhost \
- --store=follow2 \
- --port=26258 \
- --http-port=8081 \
- --join=localhost:26257,localhost:26258,localhost:26259
- ~~~
-
-3. In a new terminal, start a node in the "US East":
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ cockroach start \
- --insecure \
- --locality=region=us-east \
- --host=localhost \
- --store=follow3 \
- --port=26259 \
- --http-port=8082 \
- --join=localhost:26257,localhost:26258,localhost:26259
- ~~~
-
-### Step 4. Initialize the cluster
-
-In a new terminal, use the [`cockroach init`](initialize-a-cluster.html) command to perform a one-time initialization of the cluster:
-
-{% include copy-clipboard.html %}
-~~~ shell
-$ cockroach init \
---insecure \
---host=localhost \
---port=26257
-~~~
-
-### Step 5. Simulate traffic in the US East
-
-Now that the cluster is live, use the `kv` load generator that you installed earlier to simulate multiple client connections to the node in the "US East".
-
-1. In a new terminal, start `kv`, pointing it at port `26259`, which is the port of the node with the `us-east` locality:
-
- {% include copy-clipboard.html %}
- ~~~ shell
- $ kv -duration 1m -concurrency 32 -read-percent 100 -max-rate 100 'postgresql://root@localhost:26259?sslmode=disable'
- ~~~
-
- This command initiates 32 concurrent read-only workloads for 1 minute but limits the entire `kv` process to 100 operations per second (since you're running everything on a single machine). While `kv` is running, it will print some stats to the terminal:
-
- ~~~
- _elapsed___errors__ops/sec(inst)___ops/sec(cum)__p95(ms)__p99(ms)_pMax(ms)
- 1s 0 23.0 23.0 838.9 838.9 838.9
- 2s 0 111.0 66.9 805.3 838.9 838.9
- 3s 0 100.0 78.0 209.7 209.7 209.7
- 4s 0 99.9 83.5 209.7 209.7 209.7
- 5s 0 100.0 86.8 209.7 209.7 209.7
- ...
- ~~~
-
- {{site.data.alerts.callout_info}}The latency numbers printed are over 200 milliseconds because the 100 millisecond delay in each direction (200ms round-trip) caused by the 
-
-## See Also
-
-- [How CockroachDB Does Distributed, Atomic Transactions](https://www.cockroachlabs.com/blog/how-cockroachdb-distributes-atomic-transactions/)
-- [Serializable, Lockless, Distributed: Isolation in CockroachDB](https://www.cockroachlabs.com/blog/serializable-lockless-distributed-isolation-cockroachdb/)
diff --git a/src/current/v1.1/drop-column.md b/src/current/v1.1/drop-column.md
deleted file mode 100644
index 71c6f014a72..00000000000
--- a/src/current/v1.1/drop-column.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: DROP COLUMN
-summary: Use the ALTER COLUMN statement to remove columns from tables.
-toc: true
----
-
-The `DROP COLUMN` [statement](sql-statements.html) is part of `ALTER TABLE` and removes columns from a table.
-
-
-## Synopsis
-
-{% include {{ page.version.version }}/sql/diagrams/drop_column.html %}
-
-## Required Privileges
-
-The user must have the `CREATE` [privilege](privileges.html) on the table.
-
-## Parameters
-
-| Parameter | Description |
-|-----------|-------------|
-| `table_name` | The name of the table with the column you want to drop. |
-| `name` | The name of the column you want to drop. |
-| `CASCADE` | Drop the column even if objects (such as [views](views.html)) depend on it; drop the dependent objects, as well.
-
-## See Also
-
-- [Why Go Was the Right Choice for CockroachDB](https://www.cockroachlabs.com/blog/why-go-was-the-right-choice-for-cockroachdb/)
-- [How to Optimize Garbage Collection in Go](https://www.cockroachlabs.com/blog/how-to-optimize-garbage-collection-in-go/)
-- [The Cost and Complexity of Cgo](https://www.cockroachlabs.com/blog/the-cost-and-complexity-of-cgo/)
-- [Outsmarting Go Dependencies in Testing Code](https://www.cockroachlabs.com/blog/outsmarting-go-dependencies-testing-code/)
diff --git a/src/current/v1.1/grant.md b/src/current/v1.1/grant.md
deleted file mode 100644
index 29165a41aa8..00000000000
--- a/src/current/v1.1/grant.md
+++ /dev/null
@@ -1,116 +0,0 @@
----
-title: GRANT
-summary: The GRANT statement grants user privileges for interacting with specific databases and tables.
-toc: true
----
-
-The `GRANT` [statement](sql-statements.html) lets you control each [user's](create-and-manage-users.html) SQL [privileges](privileges.html) for interacting with specific databases and tables.
-
-For privileges required by specific statements, see the documentation for the respective [SQL statement](sql-statements.html).
-
-
-## Synopsis
-
-{% include {{ page.version.version }}/sql/diagrams/grant.html %}
-
-## Required Privileges
-
-The user granting privileges must have the `GRANT` privilege on the target databases or tables.
-
-## Supported Privileges
-
-Users can be granted the following privileges. Some privileges are applicable both for databases and tables, while other are applicable only for tables (see **Levels** in the table below).
-
-- When a user is granted privileges for a database, new tables created in the database will inherit the privileges, but the privileges can then be changed.
-- When a user is granted privileges for a table, the privileges are limited to the table.
-- The `root` user is automatically assigned the `ALL` privilege for new databases and is the only user allowed to create databases.
-- For privileges required by specific statements, see the documentation for the respective [SQL statement](sql-statements.html).
-
-Privilege | Levels
-----------|------------
-`ALL` | Database, Table
-`CREATE` | Database, Table
-`DROP` | Database, Table
-`GRANT` | Database, Table
-`SELECT` | Table
-`INSERT` | Table
-`DELETE` | Table
-`UPDATE` | Table
-
-## Parameters
-
-Parameter | Description
-----------|------------
-`table_name` | A comma-separated list of table names. Alternately, to grant privileges to all tables, use `*`. `ON TABLE table.*` grants apply to all existing tables in a database but will not affect tables created after the grant.
-`database_name` | A comma-separated list of database names.| Required? | -Yes | -
| Key | -temp |
-
| Value | -The URL of the temp directory | -
| Example | -WITH temp = 'azure://acme-co/import-temp?AZURE_ACCOUNT_KEY=hash&AZURE_ACCOUNT_NAME=acme-co' |
-
| Required? | -No | -
| Key | -delimiter |
-
| Value | -The unicode character that delimits columns in your rows | -
| Example | -To use tab-delimited values: WITH temp = '...', delimiter = e'\t' |
-
| Required? | -No | -
| Key | -comment |
-
| Value | -The unicode character that identifies rows to skip | -
| Example | -WITH temp = '...', comment = '#' |
-
| Required? | -No | -
| Key | -nullif |
-
| Value | -The string that should be converted to NULL | -
| Example | -To use empty columns as NULL: WITH temp = '...', nullif = '' |
-
WHERE <indexed column> = 10, SQL can use the index to find values starting at 10 but less than 11. In contrast, without an index, SQL would have to evaluate _every_ row in the column for values equaling 10.
-
-### Creation
-
-Each table automatically has an index created called `primary`, which indexes either its [primary key](primary-key.html) or—if there is no primary key—a unique value for each row known as `rowid`. We recommend always defining a primary key because the index it creates provides much better performance than letting CockroachDB use `rowid`.
-
-The `primary` index helps filter a table's primary key but doesn't help SQL find values in any other columns. However, you can use secondary indexes to improve the performance of queries using columns not in a table's primary key. You can create them:
-
-- At the same time as the table with the `INDEX` clause of [`CREATE TABLE`](create-table.html#create-a-table-with-secondary-indexes). In addition to explicitly defined indexes, CockroachDB automatically creates secondary indexes for columns with the [Unique constraint](unique.html).
-- For existing tables with [`CREATE INDEX`](create-index.html).
-- By applying the Unique constraint to columns with [`ALTER TABLE`](alter-table.html), which automatically creates an index of the constrained columns.
-
-To create the most useful secondary indexes, you should also check out our [best practices](#best-practices).
-
-### Selection
-
-Because each query can use only a single index, CockroachDB selects the index it calculates will scan the fewest rows (i.e., the fastest). For more detail, check out our blog post [Index Selection in CockroachDB](https://www.cockroachlabs.com/blog/index-selection-cockroachdb-2/).
-
-To override CockroachDB's index selection, you can also force [queries to use a specific index](select.html#force-index-selection-index-hints) (also known as "index hinting").
-
-### Storage
-
-CockroachDB stores indexes directly in your key-value store. You can find more information in our blog post [Mapping Table Data to Key-Value Storage](https://www.cockroachlabs.com/blog/sql-in-cockroachdb-mapping-table-data-to-key-value-storage/).
-
-### Locking
-
-Tables are not locked during index creation thanks to CockroachDB's [schema change procedure](https://www.cockroachlabs.com/blog/how-online-schema-changes-are-possible-in-cockroachdb/).
-
-### Performance
-
-Indexes create a trade-off: they greatly improve the speed of queries, but slightly slow down writes (because new values have to be copied and sorted). The first index you create has the largest impact, but additional indexes only introduce marginal overhead.
-
-To maximize your indexes' performance, we recommend following a few [best practices](#best-practices).
-
-## Best Practices
-
-We recommend creating indexes for all of your common queries. To design the most useful indexes, look at each query's `WHERE` and `SELECT` clauses, and create indexes that:
-
-- [Index all columns](#indexing-columns) in the `WHERE` clause.
-- [Store columns](#storing-columns) that are _only_ in the `SELECT` clause.
-
-### Indexing Columns
-
-When designing indexes, it's important to consider which columns you index and the order you list them. Here are a few guidelines to help you make the best choices:
-
-- Each table's [primary key](primary-key.html) (which we recommend always [defining](create-table.html#create-a-table-primary-key-defined)) is automatically indexed. The index it creates (called `primary`) cannot be changed, nor can you change the primary key of a table after it's been created, so this is a critical decision for every table.
-- Queries can benefit from an index even if they only filter a prefix of its columns. For example, if you create an index of columns `(A, B, C)`, queries filtering `(A)` or `(A, B)` can still use the index. However, queries that do not filter `(A)` will not benefit from the index.This feature also lets you avoid using single-column indexes. Instead, use the column as the first column in a multiple-column index, which is useful to more queries. -- Columns filtered in the `WHERE` clause with the equality operators (`=` or `IN`) should come first in the index, before those referenced with inequality operators (`<`, `>`). -- Indexes of the same columns in different orders can produce different results for each query. For more information, see [our blog post on index selection](https://www.cockroachlabs.com/blog/index-selection-cockroachdb-2/)—specifically the section "Restricting the search space." - -### Storing Columns - -The `STORING` clause specifies columns which are not part of the index key but should be stored in the index. This optimizes queries which retrieve those columns without filtering on them, because it prevents the need to read the primary index. - -### Example - -Say we have a table with three columns, two of which are indexed: - -{% include copy-clipboard.html %} -~~~ sql -> CREATE TABLE tbl (col1 INT, col2 INT, col3 INT, INDEX (col1, col2)); -~~~ - -If we filter on the indexed columns but retrieve the unindexed column, this requires reading `col3` from the primary index via an "index join." - -{% include copy-clipboard.html %} -~~~ sql -> EXPLAIN SELECT col3 FROM tbl WHERE col1 = 10 AND col2 > 1; -~~~ - -~~~ - tree | field | description -+-----------------+-------------+-----------------------+ - render | | - └── index-join | | - │ | table | tbl@primary - │ | key columns | rowid - └── scan | | - | table | tbl@tbl_col1_col2_idx - | spans | /10/2-/11 -~~~ - -However, if we store `col3` in the index, the index join is no longer necessary. This means our query only needs to read from the secondary index, so it will be more efficient. - -{% include copy-clipboard.html %} -~~~ sql -> CREATE TABLE tbl (col1 INT, col2 INT, col3 INT, INDEX (col1, col2) STORING (col3)); -~~~ - -{% include copy-clipboard.html %} -~~~ sql -> EXPLAIN SELECT col3 FROM tbl WHERE col1 = 10 AND col2 > 1; -~~~ - -~~~ - tree | field | description -+-----------+-------------+-------------------+ - render | | - └── scan | | - | table | tbl@tbl_col1_col2_idx - | spans | /10/2-/11 -~~~ - -## See Also - -- [`CREATE INDEX`](create-index.html) -- [`DROP INDEX`](drop-index.html) -- [`RENAME INDEX`](rename-index.html) -- [`SHOW INDEX`](show-index.html) -- [SQL Statements](sql-statements.html) diff --git a/src/current/v1.1/information-schema.md b/src/current/v1.1/information-schema.md deleted file mode 100644 index e67b6165692..00000000000 --- a/src/current/v1.1/information-schema.md +++ /dev/null @@ -1,191 +0,0 @@ ---- -title: Information Schema -summary: The information_schema database contains read-only views that you can use for introspection into your database's tables, columns, indexes, and views. -toc: true ---- - -CockroachDB represents your cluster's schema in a database called `information_schema`, which contains read-only [views](views.html) that you can use for introspection into your database's tables, columns, indexes, and views. - -This notion of an information schema is part of the SQL standard, which means it is portable and will remain stable. This contrasts with other objects like `pg_catalog`, which is not part of the SQL standard and handles specific implementation issues. - -{{site.data.alerts.callout_info}}The
information_schema views typically represent objects that the current user has privilege to access. To ensure you can view your cluster's entire schema, access it as the root user.{{site.data.alerts.end}}
-
-
-## Objects
-
-To perform introspection on objects, you can either read from the related `information_schema` view or use one of CockroachDB's `SHOW` statements.
-
-Object | Information Schema View| SHOW .
--------|--------------|--------
-Columns | [columns](#columns)| [`SHOW COLUMNS`](show-columns.html)
-Constraints | [key_column_usage](#key_column_usage), [table_constraints](#table_constraints)| [`SHOW CONSTRAINTS`](show-constraints.html)
-Databases | [schemata](#schemata)| [`SHOW DATABASE`](show-vars.html)
-Indexes | [statistics](#statistics)| [`SHOW INDEX`](show-index.html)
-Privileges | [schema_privileges](#schema_privileges), [table_privileges](#table_privileges)| [`SHOW GRANTS`](show-grants.html)
-Tables | [tables](#tables)| [`SHOW TABLES`](show-tables.html)
-Views | [tables](#tables), [views](#views)| [`SHOW CREATE VIEW`](show-create-view.html)
-
-## Views
-
-The `information_schema` database is comprised of many views representing your cluster's schema, each of which is detailed below.
-
-### columns
-
-The `columns` view contains information about the columns in each table.
-
-Column | Description
--------|-----------
-`TABLE_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`TABLE_SCHEMA` | Name of the database containing the table.
-`TABLE_NAME` | Name of the table.
-`COLUMN_NAME` | Name of the column.
-`ORDINAL_POSITION` | Ordinal position of the column in the table (begins at 1).
-`COLUMN_DEFAULT` | Default Value for the column.
-`IS_NULLABLE` | `YES` if the column accepts *NULL* values; `NO` if it doesn't (e.g., it has the [Not Null constraint](not-null.html)).
-`DATA_TYPE` | [Data type](data-types.html) of the column.
-`CHARACTER_MAXIMUM_LENGTH` | If `DATA_TYPE` is `STRING`, the maximum length in characters of a value; otherwise *NULL*.
-`CHARACTER_OCTET_LENGTH` | If `DATA_TYPE` is `STRING`, the maximum length in octets (bytes) of a value; otherwise *NULL*.
-`NUMERIC_PRECISION` | If `DATA_TYPE` is numeric, the declared or implicit precision (i.e., number of significant digits); otherwise *NULL*.
-`NUMERIC_SCALE` | If `DATA_TYPE` is an exact numeric type, the scale (i.e., number of digits to the right of the decimal point); otherwise *NULL*.
-`DATETIME_PRECISION` | Always *NULL* (unsupported by CockroachDB).
-
-### key_column_usage
-
-The `key_column_usage` view identifies columns with [Primary Key](primary-key.html), [Unique](unique.html), or [Foreign Key](foreign-key.html) constraints.
-
-Column | Description
--------|-----------
-`CONSTRAINT_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`CONSTRAINT_SCHEMA` | Name of the database containing the constraint.
-`CONSTRAINT_NAME` | Name of the constraint.
-`TABLE_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`TABLE_SCHEMA` | Name of the database that contains the constrained table.
-`TABLE_NAME` | Name of the constrained table.
-`COLUMN_NAME` | Name of the constrained column.
-`ORDINAL_POSITION` | Ordinal position of the column within the constraint (begins at 1).
-`POSITION_IN_UNIQUE_CONSTRAINT` | For Foreign Key constraints, ordinal position of the referenced column within its Unique constraint (begins at 1).
-
-### schema_privileges
-
-The `schema_privileges` view identifies which [privileges](privileges.html) have been granted to each user at the database level.
-
-Column | Description
--------|-----------
-`GRANTEE` | Username of user with grant.
-`TABLE_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`TABLE_SCHEMA` | Name of the database that contains the constrained table.
-`PRIVILEGE_TYPE` | Name of the [privilege](privileges.html).
-`IS_GRANTABLE` | Always *NULL* (unsupported by CockroachDB).
-
-### schemata
-
-The `schemata` view identifies the cluster's databases.
-
-Column | Description
--------|-----------
-`TABLE_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`SCHEMA_NAME` | Name of the database.
-`DEFAULT_CHARACTER_SET_NAME` | Always *NULL* (unsupported by CockroachDB).
-`SQL_PATH` | Always *NULL* (unsupported by CockroachDB).
-
-### statistics
-
-The `statistics` view identifies table's [indexes](indexes.html).
-
-Column | Description
--------|-----------
-`TABLE_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`TABLE_SCHEMA` | Name of the database that contains the constrained table.
-`TABLE_NAME` | Name of the table .
-`NON_UNIQUE` | `false` if the index was created by a Unique constraint; `true` if the index was not created by a Unique constraint.
-`INDEX_SCHEMA` | Name of the database that contains the index.
-`INDEX_NAME` | Name of the index.
-`SEQ_IN_INDEX` | Ordinal position of the column within the index (begins at 1).
-`COLUMN_NAME` | Name of the column being indexed.
-`COLLATION` | Always *NULL* (unsupported by CockroachDB).
-`CARDINALITY` | Always *NULL* (unsupported by CockroachDB).
-`DIRECTION` | `ASC` (ascending) or `DESC` (descending) order.
-`STORING` | `true` if column is [stored](create-index.html#store-columns); `false` if it's indexed.
-
-### table_constraints
-
-The `table_constraints` view identifies [constraints](constraints.html) applied to tables.
-
-Column | Description
--------|-----------
-`CONSTRAINT_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`CONSTRAINT_SCHEMA` | Name of the database that contains the constraint.
-`CONSTRAINT_NAME` | Name of the constraint.
-`TABLE_SCHEMA` | Name of the database that contains the constrained table.
-`TABLE_NAME` | Name of the constrained table.
-`CONSTRAINT_TYPE` | Type of [constraint](constraints.html): `CHECK`, `FOREIGN KEY`, `PRIMARY KEY`, or `UNIQUE`.
-
-### table_privileges
-
-The `table_privileges` view identifies which [privileges](privileges.html) have been granted to each user at the table level.
-
-Column | Description
--------|-----------
-`GRANTOR` | Always *NULL* (unsupported by CockroachDB).
-`GRANTEE` | Username of user with grant.
-`TABLE_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`TABLE_SCHEMA` | Name of the database that the grant applies to.
-`TABLE_NAME` | Name of the table that the grant applies to.
-`PRIVILEGE_TYPE` | Type of [privilege](privileges.html): `SELECT`, `INSERT`, `UPDATE`, `DELETE`, `TRUNCATE`, `REFERENCES`, or `TRIGGER`.
-`IS_GRANTABLE` | Always *NULL* (unsupported by CockroachDB).
-`WITH_HIERARCHY` | Always *NULL* (unsupported by CockroachDB).
-
-### tables
-
-The `tables` view identifies tables and views in the cluster.
-
-Column | Description
--------|-----------
-`TABLE_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`TABLE_SCHEMA` | Name of the database that contains the table.
-`TABLE_NAME` | Name of the table.
-`TABLE_TYPE` | Type of the table: `BASE TABLE` for a normal table, `VIEW` for a view, or `SYSTEM VIEW` for a view created by CockroachDB.
-`VERSION` | Version number of the table; versions begin at 1 and are incremented each time an `ALTER TABLE` statement is issued on the table.
-
-### user_privileges New in v1.1
-
-The `user_privileges` view identifies global [privileges](privileges.html).
-
-{{site.data.alerts.callout_info}}Currently, CockroachDB does not support global privileges for non-root users. Therefore, this view contains global privileges only for root.
-{{site.data.alerts.end}}
-
-Column | Description
--------|-----------
-`GRANTEE` | Username of user with grant.
-`TABLE_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`PRIVELEGE_TYPE` | Type of [privilege](privileges.html).
-`IS_GRANTABLE` | Always *NULL* (unsupported by CockroachDB).
-
-### views
-
-The `views` view identifies [views](views.html) in the cluster.
-
-Column | Description
--------|-----------
-`TABLE_CATALOG` | Always equal to `def` (CockroachDB does not support the notion of catalogs).
-`TABLE_SCHEMA` | Name of the database that the view reads from.
-`TABLE_NAME` | Name of the table the view reads from.
-`VIEW_DEFINITION` | `AS` clause used to [create the view](views.html#creating-views).
-`CHECK_OPTION` | Always *NULL* (unsupported by CockroachDB).
-`IS_UPDATABLE` | Always *NULL* (unsupported by CockroachDB).
-`IS_INSERTABLE_INTO` | Always *NULL* (unsupported by CockroachDB).
-`IS_TRIGGER_UPDATABLE` | Always *NULL* (unsupported by CockroachDB).
-`IS_TRIGGER_DELETABLE` | Always *NULL* (unsupported by CockroachDB).
-`IS_TRIGGER_INSERTABLE_INTO` | Always *NULL* (unsupported by CockroachDB).
-
-## See Also
-
-- [`SHOW`](show-vars.html)
-- [`SHOW COLUMNS`](show-columns.html)
-- [`SHOW CONSTRAINTS`](show-constraints.html)
-- [`SHOW CREATE TABLE`](show-create-table.html)
-- [`SHOW CREATE VIEW`](show-create-view.html)
-- [`SHOW DATABASES`](show-databases.html)
-- [`SHOW GRANTS`](show-grants.html)
-- [`SHOW INDEX`](show-index.html)
-- [`SHOW TABLES`](show-tables.html)
diff --git a/src/current/v1.1/initialize-a-cluster.md b/src/current/v1.1/initialize-a-cluster.md
deleted file mode 100644
index 784ea676e76..00000000000
--- a/src/current/v1.1/initialize-a-cluster.md
+++ /dev/null
@@ -1,114 +0,0 @@
----
-title: Initialize a Cluster
-summary: Perform a one-time-only initialization of a CockroachDB cluster.
-toc: true
----
-
-New in v1.1: This page explains the `cockroach init` [command](cockroach-commands.html), which you use to perform a one-time initialization of a new multi-node cluster. For a full walk-through of the cluster startup and initialization process, see one of the [Manual Deployment](manual-deployment.html) tutorials.
-
-{{site.data.alerts.callout_info}}When starting a single-node cluster, you do not need to use the cockroach init command. You can simply run the cockroach start command without the --join flag to start and initialize the single-node cluster.{{site.data.alerts.end}}
-
-
-## Synopsis
-
-~~~ shell
-# Perform a one-time initialization of a cluster:
-$ cockroach init
-
-
-
-
-
-1. SSH to the machine where the node has been started.
-
-2. Make sure the `client.root.crt` and `client.root.key` files for the `root` user are on the machine.
-
-3. Run the `cockroach init` command with the `--certs-dir` flag set to the directory containing the `ca.crt` file and the files for the `root` user, and with the `--host` flag set to the address of the current node:
-
- ~~~ shell
- $ cockroach init --certs-dir=certs --host=
- ~~~
-
- At this point, all the nodes complete startup and print helpful details to the [standard output](start-a-node.html#standard-output), such as the CockroachDB version, the URL for the admin UI, and the SQL URL for clients.
-
-
-
-1. SSH to the machine where the node has been started.
-
-2. Run the `cockroach init` command with the `--host` flag set to the address of the current node:
-
- ~~~ shell
- $ cockroach init --insecure --host=
- ~~~
-
- At this point, all the nodes complete startup and print helpful details to the [standard output](start-a-node.html#standard-output), such as the CockroachDB version, the URL for the admin UI, and the SQL URL for clients.
-
-
-### Initialize a Cluster from Another Machine
-
-
-
-
-
-
-
-1. [Install the `cockroach` binary](install-cockroachdb.html) on a machine separate from the node.
-
-2. Create a `certs` directory and copy the CA certificate and the client certificate and key for the `root` user into the directory.
-
-3. Run the `cockroach init` command with the `--certs-dir` flag set to the directory containing the `ca.crt` file and the files for the `root` user, and with the `--host` flag set to the address of any node:
-
- ~~~ shell
- $ cockroach init --certs-dir=certs --host=
- ~~~
-
- At this point, all the nodes complete startup and print helpful details to the [standard output](start-a-node.html#standard-output), such as the CockroachDB version, the URL for the admin UI, and the SQL URL for clients.
-
-
-
-1. [Install the `cockroach` binary](install-cockroachdb.html) on a machine separate from the node.
-
-2. Run the `cockroach init` command with the `--host` flag set to the address of any node:
-
- ~~~ shell
- $ cockroach init --insecure --host=
- ~~~
-
- At this point, all the nodes complete startup and print helpful details to the [standard output](start-a-node.html#standard-output), such as the CockroachDB version, the URL for the admin UI, and the SQL URL for clients.
-
-
-## See Also
-
-- [Manual Deployment](manual-deployment.html)
-- [Orchestrated Deployment](orchestration.html)
-- [Local Deployment](start-a-local-cluster.html)
-- [`cockroach start`](start-a-node.html)
-- [Other Cockroach Commands](cockroach-commands.html)
diff --git a/src/current/v1.1/insert.md b/src/current/v1.1/insert.md
deleted file mode 100644
index d2dcf10adf4..00000000000
--- a/src/current/v1.1/insert.md
+++ /dev/null
@@ -1,566 +0,0 @@
----
-title: INSERT
-summary: The INSERT statement inserts one or more rows into a table.
-toc: true
----
-
-The `INSERT` [statement](sql-statements.html) inserts one or more rows into a table. In cases where inserted values conflict with uniqueness constraints, the `ON CONFLICT` clause can be used to update rather than insert rows.
-
-
-## Performance Best Practices
-
-- A single [multi-row `INSERT`](#insert-multiple-rows-into-an-existing-table) statement is faster than multiple single-row `INSERT` statements. To bulk-insert data into an existing table, use a multi-row `INSERT` instead of multiple single-row `INSERT` statements.
-- The experimental [`IMPORT`](import.html) statement performs better than `INSERT` when inserting into a new table.
-- In traditional SQL databases, generating and retrieving unique IDs involves using `INSERT` with `SELECT`. In CockroachDB, use `RETURNING` clause with `INSERT` instead. See [Insert and Return Values](#insert-and-return-values) for more details.
-
-## Required Privileges
-
-The user must have the `INSERT` [privilege](privileges.html) on the table. To use `ON CONFLICT DO UPDATE`, the user must also have the `UPDATE` privilege on the table.
-
-## Synopsis
-
-{% include {{ page.version.version }}/sql/diagrams/insert.html %}
-
-
-
-## Parameters
-
-
-
-Parameter | Description
-----------|------------
-`qualified_name` | The table you want to write data to.|
-`AS name` | An alias for the table name. When an alias is provided, it completely hides the actual table name.
-`qualified_name_list` | A comma-separated list of column names, in parentheses.
-`select_stmt` | A [selection clause](selection-clauses.html). Each value must match the [data type](data-types.html) of its column. Also, if column names are listed (`qualified_name_list`), values must be in corresponding order; otherwise, they must follow the declared order of the columns in the table.
-`DEFAULT VALUES` | To fill all columns with their [default values](default-value.html), use `DEFAULT VALUES` in place of `select_stmt`. To fill a specific column with its default value, leave the value out of the `select_stmt` or use `DEFAULT` at the appropriate position. See the [Insert Default Values](#insert-default-values) examples below.
-`on_conflict` | Normally, when inserted values conflict with a Unique constraint on one or more columns, CockroachDB returns an error. To update the affected rows instead, use an `ON CONFLICT` clause containing the column(s) with the unique constraint and the `DO UPDATE SET` expression set to the column(s) to be updated (any `SET` expression supported by the [`UPDATE`](update.html) statement is also supported here, including those with `WHERE` clauses). To prevent the affected rows from updating while allowing new rows to be inserted, set `ON CONFLICT` to `DO NOTHING`. See the [Update Values `ON CONFLICT`](#update-values-on-conflict) and [Do Not Update Values `ON CONFLICT`](#do-not-update-values-on-conflict) examples below.
Note that it's not possible to update the same row twice with a single `INSERT ON CONFLICT` statement. Also, if the values in the `SET` expression cause uniqueness conflicts, CockroachDB will return an error.
As a short-hand alternative to the `ON CONFLICT` clause, you can use the [`UPSERT`](upsert.html) statement. However, `UPSERT` does not let you specify the column with the unique constraint; it assumes that the column is the primary key. Using `ON CONFLICT` is therefore more flexible. -`RETURNING target_list` | Return values based on rows inserted, where `target_list` can be specific column names from the table, `*` for all columns, or a computation on specific columns. See the [Insert and Return Values](#insert-and-return-values) example below.
Within a [transaction](transactions.html), use `RETURNING NOTHING` to return nothing in the response, not even the number of rows affected. - -## Examples - -All of the examples below assume you've already created a table `accounts`: - -~~~ sql -> CREATE TABLE accounts( - id INT DEFAULT unique_rowid(), - balance DECIMAL -); -~~~ - -### Insert a Single Row - -~~~ sql -> INSERT INTO accounts (balance, id) VALUES (10000.50, 1); - -> SELECT * FROM accounts; -~~~ -~~~ -+----+---------+ -| id | balance | -+----+---------+ -| 1 | 10000.5 | -+----+---------+ -~~~ - -If you do not list column names, the statement will use the columns of the table in their declared order: - -~~~ sql -> SHOW COLUMNS FROM accounts; -~~~ -~~~ -+---------+---------+-------+----------------+ -| Field | Type | Null | Default | -+---------+---------+-------+----------------+ -| id | INT | false | unique_rowid() | -| balance | DECIMAL | true | NULL | -+---------+---------+-------+----------------+ -~~~ -~~~ sql -> INSERT INTO accounts VALUES (2, 20000.75); - -> SELECT * FROM accounts; -+----+----------+ -| id | balance | -+----+----------+ -| 1 | 10000.50 | -| 2 | 20000.75 | -+----+----------+ -~~~ - -### Insert Multiple Rows into an Existing Table - -{{site.data.alerts.callout_success}} Multi-row inserts are faster than multiple single-row
-
-{{site.data.alerts.callout_success}}This use of Note that it's not possible to update the same row twice with a single `INSERT ON CONFLICT` statement. Also, if the values in the `SET` expression cause uniqueness conflicts, CockroachDB will return an error.
As a short-hand alternative to the `ON CONFLICT` clause, you can use the [`UPSERT`](upsert.html) statement. However, `UPSERT` does not let you specify the column with the unique constraint; it assumes that the column is the primary key. Using `ON CONFLICT` is therefore more flexible. -`RETURNING target_list` | Return values based on rows inserted, where `target_list` can be specific column names from the table, `*` for all columns, or a computation on specific columns. See the [Insert and Return Values](#insert-and-return-values) example below.
Within a [transaction](transactions.html), use `RETURNING NOTHING` to return nothing in the response, not even the number of rows affected. - -## Examples - -All of the examples below assume you've already created a table `accounts`: - -~~~ sql -> CREATE TABLE accounts( - id INT DEFAULT unique_rowid(), - balance DECIMAL -); -~~~ - -### Insert a Single Row - -~~~ sql -> INSERT INTO accounts (balance, id) VALUES (10000.50, 1); - -> SELECT * FROM accounts; -~~~ -~~~ -+----+---------+ -| id | balance | -+----+---------+ -| 1 | 10000.5 | -+----+---------+ -~~~ - -If you do not list column names, the statement will use the columns of the table in their declared order: - -~~~ sql -> SHOW COLUMNS FROM accounts; -~~~ -~~~ -+---------+---------+-------+----------------+ -| Field | Type | Null | Default | -+---------+---------+-------+----------------+ -| id | INT | false | unique_rowid() | -| balance | DECIMAL | true | NULL | -+---------+---------+-------+----------------+ -~~~ -~~~ sql -> INSERT INTO accounts VALUES (2, 20000.75); - -> SELECT * FROM accounts; -+----+----------+ -| id | balance | -+----+----------+ -| 1 | 10000.50 | -| 2 | 20000.75 | -+----+----------+ -~~~ - -### Insert Multiple Rows into an Existing Table - -{{site.data.alerts.callout_success}} Multi-row inserts are faster than multiple single-row
INSERT statements. As a performance best practice, we recommend batching multiple rows in one multi-row INSERT statement instead of using multiple single-row INSERT statements. Experimentally determine the optimal batch size for your application by monitoring the performance for different batch sizes (10 rows, 100 rows, 1000 rows). {{site.data.alerts.end}}
-
-~~~ sql
-> INSERT INTO accounts (id, balance) VALUES (3, 8100.73), (4, 9400.10);
-
-> SELECT * FROM accounts;
-~~~
-~~~
-+----+----------+
-| id | balance |
-+----+----------+
-| 1 | 10000.50 |
-| 2 | 20000.75 |
-| 3 | 8100.73 |
-| 4 | 9400.10 |
-+----+----------+
-~~~
-
-### Insert Multiple Rows into a New Table
-
-The experimental [`IMPORT`](import.html) statement performs better than `INSERT` when inserting into a new table.
-
-### Insert from a `SELECT` Statement
-
-~~~ sql
-> SHOW COLUMS FROM other_accounts;
-~~~
-~~~
-+--------+---------+-------+---------+
-| Field | Type | Null | Default |
-+--------+---------+-------+---------+
-| number | INT | false | NULL |
-| amount | DECIMAL | true | NULL |
-+--------+---------+-------+---------+
-~~~
-~~~ sql
-> INSERT INTO accounts (id, balance) SELECT number, amount FROM other_accounts WHERE id > 4;
-
-> SELECT * FROM accounts;
-~~~
-~~~
-+----+----------+
-| id | balance |
-+----+----------+
-| 1 | 10000.5 |
-| 2 | 20000.75 |
-| 3 | 8100.73 |
-| 4 | 9400.1 |
-| 5 | 350.1 |
-| 6 | 150 |
-| 7 | 200.1 |
-+----+----------+
-~~~
-
-### Insert Default Values
-
-~~~ sql
-> INSERT INTO accounts (id) VALUES (8);
-> INSERT INTO accounts (id, balance) VALUES (9, DEFAULT);
-
-> SELECT * FROM accounts WHERE id in (8, 9);
-~~~
-~~~
-+----+---------+
-| id | balance |
-+----+---------+
-| 8 | NULL |
-| 9 | NULL |
-+----+---------+
-~~~
-~~~ sql
-> INSERT INTO accounts DEFAULT VALUES;
-
-> SELECT * FROM accounts;
-~~~
-~~~
-+--------------------+----------+
-| id | balance |
-+--------------------+----------+
-| 1 | 10000.5 |
-| 2 | 20000.75 |
-| 3 | 8100.73 |
-| 4 | 9400.1 |
-| 5 | 350.1 |
-| 6 | 150 |
-| 7 | 200.1 |
-| 8 | NULL |
-| 9 | NULL |
-| 142933248649822209 | NULL |
-+--------------------+----------+
-~~~
-
-### Insert and Return Values
-
-In this example, the `RETURNING` clause returns the `id` values of the rows inserted, which are generated server-side by the `unique_rowid()` function. The language-specific versions assume that you have installed the relevant [client drivers](install-client-drivers.html).
-
-RETURNING mirrors the behavior of MySQL's last_insert_id() function.{{site.data.alerts.end}}
-
-{{site.data.alerts.callout_info}}When a driver provides a query() method for statements that return results and an exec() method for statements that do not (e.g., Go), it's likely necessary to use the query() method for INSERT statements with RETURNING.{{site.data.alerts.end}}
-
-
-
-
-
-
-
-
-
-
-
-~~~ sql
-> INSERT INTO accounts (id, balance)
- VALUES (DEFAULT, 1000), (DEFAULT, 250)
- RETURNING id;
-~~~
-
-~~~
-+--------------------+
-| id |
-+--------------------+
-| 190018410823680001 |
-| 190018410823712769 |
-+--------------------+
-(2 rows)
-~~~
-
-
-
-
-
-
-~~~ python
-# Import the driver.
-import psycopg2
-
-# Connect to the "bank" database.
-conn = psycopg2.connect(
- database='bank',
- user='root',
- host='localhost',
- port=26257
-)
-
-# Make each statement commit immediately.
-conn.set_session(autocommit=True)
-
-# Open a cursor to perform database operations.
-cur = conn.cursor()
-
-# Insert two rows into the "accounts" table
-# and return the "id" values generated server-side.
-cur.execute(
- 'INSERT INTO accounts (id, balance) '
- 'VALUES (DEFAULT, 1000), (DEFAULT, 250) '
- 'RETURNING id'
-)
-
-# Print out the returned values.
-rows = cur.fetchall()
-print('IDs:')
-for row in rows:
- print([str(cell) for cell in row])
-
-# Close the database connection.
-cur.close()
-conn.close()
-~~~
-
-The printed values would look like:
-
-~~~
-IDs:
-['190019066706952193']
-['190019066706984961']
-~~~
-
-
-
-
-
-
-~~~ ruby
-# Import the driver.
-require 'pg'
-
-# Connect to the "bank" database.
-conn = PG.connect(
- user: 'root',
- dbname: 'bank',
- host: 'localhost',
- port: 26257
-)
-
-# Insert two rows into the "accounts" table
-# and return the "id" values generated server-side.
-conn.exec(
- 'INSERT INTO accounts (id, balance) '\
- 'VALUES (DEFAULT, 1000), (DEFAULT, 250) '\
- 'RETURNING id'
-) do |res|
-
-# Print out the returned values.
-puts "IDs:"
- res.each do |row|
- puts row
- end
-end
-
-# Close communication with the database.
-conn.close()
-~~~
-
-The printed values would look like:
-
-~~~
-IDs:
-{"id"=>"190019066706952193"}
-{"id"=>"190019066706984961"}
-~~~
-
-
-
-
-
-~~~ go
-package main
-
-import (
- "database/sql"
- "fmt"
- "log"
-
- _ "github.com/lib/pq"
-)
-
-func main() {
- //Connect to the "bank" database.
- db, err := sql.Open(
- "postgres",
- "postgresql://root@localhost:26257/bank?sslmode=disable"
- )
- if err != nil {
- log.Fatal("error connecting to the database: ", err)
- }
-
- // Insert two rows into the "accounts" table
- // and return the "id" values generated server-side.
- rows, err := db.Query(
- "INSERT INTO accounts (id, balance) " +
- "VALUES (DEFAULT, 1000), (DEFAULT, 250) " +
- "RETURNING id",
- )
- if err != nil {
- log.Fatal(err)
- }
-
- // Print out the returned values.
- defer rows.Close()
- fmt.Println("IDs:")
- for rows.Next() {
- var id int
- if err := rows.Scan(&id); err != nil {
- log.Fatal(err)
- }
- fmt.Printf("%d\n", id)
- }
-}
-~~~
-
-The printed values would look like:
-
-~~~
-IDs:
-190019066706952193
-190019066706984961
-~~~
-
-
-
-
-
-
-~~~ js
-var async = require('async');
-
-// Require the driver.
-var pg = require('pg');
-
-// Connect to the "bank" database.
-var config = {
- user: 'root',
- host: 'localhost',
- database: 'bank',
- port: 26257
-};
-
-pg.connect(config, function (err, client, done) {
- // Closes communication with the database and exits.
- var finish = function () {
- done();
- process.exit();
- };
-
- if (err) {
- console.error('could not connect to cockroachdb', err);
- finish();
- }
- async.waterfall([
- function (next) {
- // Insert two rows into the "accounts" table
- // and return the "id" values generated server-side.
- client.query(
- `INSERT INTO accounts (id, balance)
- VALUES (DEFAULT, 1000), (DEFAULT, 250)
- RETURNING id;`,
- next
- );
- }
- ],
- function (err, results) {
- if (err) {
- console.error('error inserting into and selecting from accounts', err);
- finish();
- }
- // Print out the returned values.
- console.log('IDs:');
- results.rows.forEach(function (row) {
- console.log(row);
- });
-
- finish();
- });
-});
-~~~
-
-The printed values would look like:
-
-~~~
-IDs:
-{ id: '190019066706952193' }
-{ id: '190019066706984961' }
-~~~
-
-
-
-### Update Values `ON CONFLICT`
-
-When a uniqueness conflict is detected, CockroachDB stores the row in a temporary table called `excluded`. This example demonstrates how you use the columns in the temporary `excluded` table to apply updates on conflict:
-
-~~~ sql
-> INSERT INTO accounts (id, balance)
- VALUES (8, 500.50)
- ON CONFLICT (id)
- DO UPDATE SET balance = excluded.balance;
-
-> SELECT * FROM accounts WHERE id = 8;
-~~~
-~~~
-+----+---------+
-| id | balance |
-+----+---------+
-| 8 | 500.50 |
-+----+---------+
-~~~
-
-
-You can also update the row using an existing value:
-
-~~~ sql
-> INSERT INTO accounts (id, balance)
- VALUES (8, 500.50)
- ON CONFLICT (id)
- DO UPDATE SET balance = accounts.balance + excluded.balance;
-
-> SELECT * FROM accounts WHERE id = 8;
-~~~
-~~~
-+----+---------+
-| id | balance |
-+----+---------+
-| 8 | 1001.00 |
-+----+---------+
-~~~
-
-New in v1.1: You can also use a `WHERE` clause to apply the `DO UPDATE SET` expression conditionally:
-
-~~~ sql
-> INSERT INTO accounts (id, balance)
- VALUES (8, 700)
- ON CONFLICT (id)
- DO UPDATE SET balance = excluded.balance
- WHERE excluded.balance > accounts.balance;
-
-> SELECT * FROM accounts WHERE id = 8;
-~~~
-
-~~~
-+----+---------+
-| id | balance |
-+----+---------+
-| 8 | 800 |
-+----+---------+
-(1 row)
-~~~
-
-### Do Not Update Values `ON CONFLICT`
-
-In this example, we get an error from a uniqueness conflict:
-
-~~~ sql
-> SELECT * FROM accounts WHERE id = 8;
-~~~
-~~~
-+----+---------+
-| id | balance |
-+----+---------+
-| 8 | 500.5 |
-+----+---------+
-~~~
-~~~ sql
-> INSERT INTO accounts (id, balance) VALUES (8, 125.50);
-~~~
-~~~
-pq: duplicate key value (id)=(8) violates unique constraint "primary"
-~~~
-
-In this example, we use `ON CONFLICT DO NOTHING` to ignore the uniqueness error and prevent the affected row from being updated:
-
-~~~ sql
-> INSERT INTO accounts (id, balance)
- VALUES (8, 125.50)
- ON CONFLICT (id)
- DO NOTHING;
-
-> SELECT * FROM accounts WHERE id = 8;
-~~~
-~~~
-+----+---------+
-| id | balance |
-+----+---------+
-| 8 | 500.5 |
-+----+---------+
-~~~
-
-In this example, `ON CONFLICT DO NOTHING` prevents the first row from updating while allowing the second row to be inserted:
-
-~~~ sql
-> INSERT INTO accounts (id, balance)
- VALUES (8, 125.50), (10, 450)
- ON CONFLICT (id)
- DO NOTHING;
-
-> SELECT * FROM accounts WHERE id in (8, 10);
-~~~
-~~~
-+----+---------+
-| id | balance |
-+----+---------+
-| 8 | 500.5 |
-| 10 | 450 |
-+----+---------+
-~~~
-
-## See Also
-
-- [Selection Clauses](selection-clauses.html)
-- [`UPSERT`](upsert.html)
-- [Other SQL Statements](sql-statements.html)
diff --git a/src/current/v1.1/install-client-drivers.md b/src/current/v1.1/install-client-drivers.md
deleted file mode 100644
index b201c1567c9..00000000000
--- a/src/current/v1.1/install-client-drivers.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Install Client Drivers
-summary: CockroachDB supports the PostgreSQL wire protocol, so you can use any available PostgreSQL client drivers.
-toc: false
----
-
-CockroachDB supports the PostgreSQL wire protocol, so most available PostgreSQL client drivers should work with CockroachDB.
-
-{{site.data.alerts.callout_info}}This page features drivers that we have tested enough to claim beta-level support. This means that applications using advanced or obscure features of a driver may encounter incompatibilities. If you encounter problems, please open an issue with details to help us make progress toward full support.{{site.data.alerts.end}}
-
-{{site.data.alerts.callout_success}}For code samples using these drivers, see the Build an App with CockroachDB tutorials.{{site.data.alerts.end}}
-
-App Language | Recommended Driver
--------------|-------------------
-Go | [pq](https://godoc.org/github.com/lib/pq)
-Python | [psycopg2](http://initd.org/psycopg/)
-Ruby | [pg](https://rubygems.org/gems/pg)
-Java | [jdbc](https://jdbc.postgresql.org)
-Node.js | [pg](https://www.npmjs.com/package/pg)
-C | [libpq](http://www.postgresql.org/docs/9.5/static/libpq.html)
-C++ | [libpqxx](https://github.com/jtv/libpqxx)
-C# (.NET) | [Npgsql](http://www.npgsql.org/)
-Clojure | [java.jdbc](https://clojure-doc.org/articles/ecosystem/java_jdbc/home/)
-PHP | [php-pgsql](https://www.php.net/manual/en/book.pgsql.php)
-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 %}
diff --git a/src/current/v1.1/install-cockroachdb.html b/src/current/v1.1/install-cockroachdb.html
deleted file mode 100644
index d443a6619e5..00000000000
--- a/src/current/v1.1/install-cockroachdb.html
+++ /dev/null
@@ -1,452 +0,0 @@
----
-title: Install CockroachDB
-summary: Install CockroachDB on Mac, Linux, or Windows. Sign up for product release notes.
-tags: download, binary, homebrew
-toc: false
-allowed_hashes: [os-mac, os-linux, os-windows]
----
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/src/current/v1.1/int.md b/src/current/v1.1/int.md
deleted file mode 100644
index bc21c97573d..00000000000
--- a/src/current/v1.1/int.md
+++ /dev/null
@@ -1,106 +0,0 @@
----
-title: INT
-summary: CockroachDB supports various signed integer data types.
-toc: true
----
-
-CockroachDB supports various signed integer [data types](data-types.html).
-
-{{site.data.alerts.callout_info}}To auto-generate globally unique values, use the See Release Notes for what's new in the latest release, {{ page.release_info.version }}.
- -
-{% if page.version.stable %}
-Use
-
-{% if page.version.stable %}
-Homebrew
-{% endif %}
-Download the Binary
-Build from Source
-Use Docker
-
-
-{% endif %}
-
--
-
- - - -
-
-
Instruct Homebrew to install CockroachDB:
- -- - ---$ brew install cockroach
- -
-
Keep up-to-date with CockroachDB releases and best practices:
-{% include marketo-install.html uid="1" %} -
-
What's Next?
-Quick start a single- or multi-node cluster locally and talk to it via the built-in SQL client.
- -{% include {{ page.version.version }}/misc/diagnostics-callout.html %} - -
-
-
-
-
-
--
-
-
-
Download the CockroachDB archive for OS X, and extract the binary:
- -- - ---$ curl https://binaries.cockroachdb.com/cockroach-{{page.release_info.version}}.darwin-10.9-amd64.tgz | tar -xz
- -
-
Copy the binary into your
- - {% include copy-clipboard.html %}PATHso it's easy to execute cockroach commands from any shell:-cp -i cockroach-{{ page.release_info.version }}.darwin-10.9-amd64/cockroach /usr/local/bin/If you get a permissions error, prefix the command with
-sudo.
- -
-
Keep up-to-date with CockroachDB releases and best practices:
-{% include marketo-install.html uid="2" %} -
-
What's Next?
-Quick start a single- or multi-node cluster locally and talk to it via the built-in SQL client.
- -{% include {{ page.version.version }}/misc/diagnostics-callout.html %} - -UUID or SERIAL data type.{{site.data.alerts.end}}
-
-
-## Names and Aliases
-
-Name | Allowed Width | Aliases
------|-------|--------
-`INT` | 64-bit | `INTEGER``INT8`
`INT64`
`BIGINT` -`INT4` | 32-bit | None -`INT2` | 16-bit | `SMALLINT` -`BIT` | 1-bit | None -`BIT(n)` | n-bit | None - -## Syntax - -A constant value of type `INT` can be entered as a [numeric literal](sql-constants.html#numeric-literals). -For example: `42`, `-1234`, or `0xCAFE`. - -## Size - -The different integer types place different constraints on the range of allowable values, but all integers are stored in the same way regardless of type. Smaller values take up less space than larger ones (based on the numeric value, not the data type). - -You can use the `BIT(n)` type, with `n` from 1 to 64, to constrain integers based on their corresponding binary values. For example, `BIT(5)` would allow `31` because it corresponds to the five-digit binary integer `11111`, but would not allow `32` because it corresponds to the six-digit binary integer `100000`, which is 1 bit too long. See the [example](#examples) below for a demonstration. - -{{site.data.alerts.callout_info}}
BIT values are input and displayed in decimal format by default like all other integers, not in binary format. Also note that BIT is equivalent to BIT(1).{{site.data.alerts.end}}
-
-## Examples
-
-{% include copy-clipboard.html %}
-~~~ sql
-> CREATE TABLE ints (a INT PRIMARY KEY, b SMALLINT, c BIT(5));
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SHOW COLUMNS FROM ints;
-~~~
-
-~~~
-+-------+----------+-------+---------+-------------+
-| Field | Type | Null | Default | Indices |
-+-------+----------+-------+---------+-------------+
-| a | INT | false | NULL | {"primary"} |
-| b | SMALLINT | true | NULL | {} |
-| c | BIT(5) | true | NULL | {} |
-+-------+----------+-------+---------+-------------+
-(3 rows)
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> INSERT INTO ints VALUES (1, 32, 32);
-~~~
-
-~~~
-pq: bit string too long for type BIT(5) (column "c")
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> INSERT INTO ints VALUES (1, 32, 31);
-~~~
-
-~~~
-INSERT 1
-~~~
-
-{% include copy-clipboard.html %}
-~~~ sql
-> SELECT * FROM ints;
-~~~
-
-~~~
-+---+----+----+
-| a | b | c |
-+---+----+----+
-| 1 | 32 | 31 |
-+---+----+----+
-(1 row)
-~~~
-
-## Supported Casting & Conversion
-
-`INT` values can be [cast](data-types.html#data-type-conversions-casts) to any of the following data types:
-
-Type | Details
------|--------
-`DECIMAL` | ––
-`FLOAT` | Loses precision if the `INT` value is larger than 2^53 in magnitude
-`BOOL` | **0** converts to `false`; all other values convert to `true`
-`DATE` | Converts to days since the Unix epoch (Jan. 1, 1970)
-`TIMESTAMP` | Converts to seconds since the Unix epoch (Jan. 1, 1970)
-`INTERVAL` | Converts to microseconds
-`STRING` | ––
-
-## See Also
-
-[Data Types](data-types.html)
diff --git a/src/current/v1.1/interleave-in-parent.md b/src/current/v1.1/interleave-in-parent.md
deleted file mode 100644
index 3b72d2f8109..00000000000
--- a/src/current/v1.1/interleave-in-parent.md
+++ /dev/null
@@ -1,166 +0,0 @@
----
-title: INTERLEAVE IN PARENT
-summary: Interleaving tables improves query performance by optimizing the key-value structure of closely related table's data.
-toc: true
-toc_not_nested: true
----
-
-Interleaving tables improves query performance by optimizing the key-value structure of closely related tables, attempting to keep data on the same [key-value range](frequently-asked-questions.html#how-does-cockroachdb-scale) if it's likely to be read and written together.
-
-{{site.data.alerts.callout_info}}Interleaving tables does not affect their behavior within SQL.{{site.data.alerts.end}}
-
-
-## How Interleaved Tables Work
-
-When tables are interleaved, data written to one table (known as the **child**) is inserted directly into another (known as the **parent**) in the key-value store. This is accomplished by matching the child table's Primary Key to the parent's.
-
-### Interleave Prefix
-
-For interleaved tables to have Primary Keys that can be matched, the child table must use the parent table's entire Primary Key as a prefix of its own Primary Key––these matching columns are referred to as the **interleave prefix**. It's easiest to think of these columns as representing the same data, which is usually implemented with Foreign Keys.
-
-{{site.data.alerts.callout_success}}To formally enforce the relationship between each table's interleave prefix columns, we recommend using Foreign Key constraints.{{site.data.alerts.end}}
-
-For example, if you want to interleave `orders` into `customers` and the Primary Key of customers is `id`, you need to create a column representing `customers.id` as the first column in the Primary Key of `orders`—e.g., with a column called `customer`. So the data representing `customers.id` is the interleave prefix, which exists in the `orders` table as the `customer` column.
-
-### Key-Value Structure
-
-When you write data into the child table, it is inserted into the key-value store immediately after the parent table's key matching the interleave prefix.
-
-For example, if you interleave `orders` into `customers`, the `orders` data is written directly within the `customers` table in the key-value store. The following is a crude, illustrative example of what the keys would look like in this structure:
-
-~~~
-/customers/1
-/customers/1/orders/1000
-/customers/1/orders/1002
-/customers/2
-/customers/2/orders/1001
-/customers/2/orders/1003
-...
-/customers/n/
-/customers/n/orders/For example, if the interleave prefix of `packages` is `(customer, order)`, filtering on `customer` would be fast, but filtering on `customer` *and* `order` would be faster. -- Using only tables in the interleaved hierarchy. - -### Tradeoffs - -- In general, reads and deletes over ranges of table values (e.g., `WHERE column > value`) in interleaved tables are slower.
However, an exception to this is performing operations on ranges of table values in the greatest descendant in the interleaved hierarchy that filters on all columns of the interleave prefix with constant values.
For example, if the interleave prefix of `packages` is `(customer, order)`, filtering on the entire interleave prefix with constant values while calculating a range of table values on another column, like `WHERE customer = 1 AND order = 1001 AND delivery_date > DATE '2016-01-25'`, would still be fast. -- If the amount of interleaved data stored for any Primary Key value of the root table is larger than [a key-value range's maximum size](configure-replication-zones.html#replication-zone-format) (64MB by default), the interleaved optimizations will be diminished.
For example, if one customer has 200MB of order data, their data is likely to be spread across multiple key-value ranges and CockroachDB will not be able to access it as quickly, despite it being interleaved. - -## Syntax - -{% include {{ page.version.version }}/sql/diagrams/interleave.html %} - -## Parameters - -| Parameter | Description | -|-----------|-------------| -| `CREATE TABLE ...` | For help with this section of the syntax, [`CREATE TABLE`](create-table.html). -| `parent_table` | The name of the parent table you want to interleave the new child table into. | -| `interleave_prefix` | A comma-separated list of columns from the child table's Primary Key that represent the parent table's Primary Key (i.e., the interleave prefix). | - -## Requirements - -- You can only interleave tables when creating the child table. -- Each child table's Primary Key must contain its parent table's Primary Key as a prefix (known as the **interleave prefix**).
For example, if the parent table's primary key is `(a INT, b STRING)`, the child table's primary key could be `(a INT, b STRING, c DECIMAL)`. - {{site.data.alerts.callout_info}}This requirement is enforced only by ensuring that the columns use the same data types. However, we recommend ensuring the columns refer to the same values by using the Foreign Key constraint.{{site.data.alerts.end}} -- Interleaved tables cannot be the child of more than 1 parent table. However, each parent table can have many children tables. Children tables can also be parents of interleaved tables. - -## Recommendations - -- Use interleaved tables when your schema forms a hierarchy, and the Primary Key of the root table (for example, a "user ID" or "account ID") is a parameter to most of your queries. -- To enforce the relationship between the parent and children table's Primary Keys, use [Foreign Key constraints](foreign-key.html) on the child table. -- In cases where you're uncertain if interleaving tables will improve your queries' performance, test how tables perform under load when they're interleaved and when they aren't. - -## Examples - -### Interleaving Tables - -This example creates an interleaved hierarchy between `customers`, `orders`, and `packages`, as well as the appropriate Foreign Key constraints. You can see that each child table uses its parent table's Primary Key as a prefix of its own Primary Key (the **interleave prefix**). - -~~~ sql -> CREATE TABLE customers ( - id INT PRIMARY KEY, - name STRING(50) - ); - -> CREATE TABLE orders ( - customer INT, - id INT, - total DECIMAL(20, 5), - PRIMARY KEY (customer, id), - CONSTRAINT fk_customer FOREIGN KEY (customer) REFERENCES customers - ) INTERLEAVE IN PARENT customers (customer) - ; - -> CREATE TABLE packages ( - customer INT, - "order" INT, - id INT, - address STRING(50), - delivered BOOL, - delivery_date DATE, - PRIMARY KEY (customer, "order", id), - CONSTRAINT fk_order FOREIGN KEY (customer, "order") REFERENCES orders - ) INTERLEAVE IN PARENT orders (customer, "order") - ; -~~~ - -### Key-Value Storage Example - -It can be easier to understand what interleaving tables does by seeing what it looks like in the key-value store. For example, using the above example of interleaving `orders` in `customers`, we could insert the following values: - -~~~ sql -> INSERT INTO customers - (id, name) VALUES - (1, 'Ha-Yun'), - (2, 'Emanuela'); - -> INSERT INTO orders - (customer, id, total) VALUES - (1, 1000, 100.00), - (2, 1001, 90.00), - (1, 1002, 80.00), - (2, 1003, 70.00); -~~~ - -Using an illustrative format of the key-value store (keys are on the left; values are represented by `-> value`), the data would be written like this: - -~~~ -/customers/
customers.id and orders.customer and inserted orders.customer = 3, the data would still get written into the key-value in the expected location next to the customers table identifier, but SELECT * FROM customers WHERE id = 3 would not return any values.{{site.data.alerts.end}}
-
-To better understand how CockroachDB writes key-value data, see our blog post [Mapping Table Data to Key-Value Storage](https://www.cockroachlabs.com/blog/sql-in-cockroachdb-mapping-table-data-to-key-value-storage/).
-
-## See Also
-
-- [`CREATE TABLE`](create-table.html)
-- [Foreign Keys](foreign-key.html)
-- [Column Families](column-families.html)
-
diff --git a/src/current/v1.1/internal/version-switcher-page-data.json b/src/current/v1.1/internal/version-switcher-page-data.json
deleted file mode 100644
index 5ec30bf893f..00000000000
--- a/src/current/v1.1/internal/version-switcher-page-data.json
+++ /dev/null
@@ -1,17 +0,0 @@
----
-layout: none
----
-
-{%- capture page_folder -%}/{{ page.version.version }}/{%- endcapture -%}
-{%- assign pages = site.pages | where_exp: "pages", "pages.url contains page_folder" | where_exp: "pages", "pages.name != '404.md'" -%}
-{
-{%- for x in pages -%}
-{%- assign key = x.url | replace: page_folder, "" -%}
-{%- if x.key -%}
- {%- assign key = x.key -%}
-{%- endif %}
- {{ key | jsonify }}: {
- "url": {{ x.url | jsonify }}
- }{% unless forloop.last %},{% endunless -%}
-{% endfor %}
-}
\ No newline at end of file
diff --git a/src/current/v1.1/interval.md b/src/current/v1.1/interval.md
deleted file mode 100644
index 79b31d167ae..00000000000
--- a/src/current/v1.1/interval.md
+++ /dev/null
@@ -1,101 +0,0 @@
----
-title: INTERVAL
-summary: The INTERVAL data type stores a value that represents a span of time.
-toc: true
----
-
-The `INTERVAL` [data type](data-types.html) stores a value that represents a span of time.
-
-
-## Syntax
-
-A constant value of type `INTERVAL` can be expressed using an
-[interpreted literal](sql-constants.html#interpreted-literals), or a
-string literal
-[annotated with](sql-expressions.html#explicitly-typed-expressions)
-type `INTERVAL` or
-[coerced to](sql-expressions.html#explicit-type-coercions) type
-`INTERVAL`.
-
-`INTERVAL` constants can be expressed using the following formats:
-
-Format | Description
--------|--------
-SQL Standard | `INTERVAL 'Y-M D H:M:S'``Y-M D`: Using a single value defines days only; using two values defines years and months. Values must be integers.
`H:M:S`: Using a single value defines seconds only; using two values defines hours and minutes. Values can be integers or floats.
Note that each side is optional. -ISO 8601 | `INTERVAL 'P1Y2M3DT4H5M6S'` -Traditional PostgreSQL | `INTERVAL '1 year 2 months 3 days 4 hours 5 minutes 6 seconds'` -Golang | `INTERVAL '1h2m3s4ms5us6ns'`
Note that `ms` is milliseconds, `us` is microseconds, and `ns` is nanoseconds. Also, all fields support both integers and floats. - -CockroachDB also supports using uninterpreted -[string literals](sql-constants.html#string-literals) in contexts -where a `INTERVAL` value is otherwise expected. - -Intervals are stored internally as months, days, and nanoseconds. - -## Size - -An `INTERVAL` column supports values up to 24 bytes in width, but the total storage size is likely to be larger due to CockroachDB metadata. - -## Example - -~~~ sql -> CREATE TABLE intervals (a INT PRIMARY KEY, b INTERVAL); -~~~ - -~~~ -CREATE TABLE -~~~ - -~~~ sql -> SHOW COLUMNS FROM intervals; -~~~ - -~~~ -+-------+----------+-------+---------+ -| Field | Type | Null | Default | -+-------+----------+-------+---------+ -| a | INT | false | NULL | -| b | INTERVAL | true | NULL | -+-------+----------+-------+---------+ -~~~ - -~~~ sql -> INSERT INTO intervals VALUES - (1, INTERVAL '1h2m3s4ms5us6ns'), - (2, INTERVAL '1 year 2 months 3 days 4 hours 5 minutes 6 seconds'), - (3, INTERVAL '1-2 3 4:5:6'); -~~~ - -~~~ -INSERT 3 -~~~ - -~~~ sql -> SELECT * FROM intervals; -~~~ - -~~~ -+---+------------------+ -| a | b | -+---+------------------+ -| 1 | 1h2m3.004005006s | -| 2 | 14m3d4h5m6s | -| 3 | 14m3d4h5m6s | -+---+------------------+ -(3 rows) -~~~ - -## Supported Casting & Conversion - -`INTERVAL` values can be [cast](data-types.html#data-type-conversions-casts) to any of the following data types: - -Type | Details ------|-------- -`INT` | Converts to number of seconds (second precision) -`DECIMAL` | Converts to number of seconds (nanosecond precision) -`FLOAT` | Converts to number of picoseconds -`STRING` | Converts to `h-m-s` format (nanosecond precision) - -## See Also - -[Data Types](data-types.html) diff --git a/src/current/v1.1/keywords-and-identifiers.md b/src/current/v1.1/keywords-and-identifiers.md deleted file mode 100644 index e1ab13e979d..00000000000 --- a/src/current/v1.1/keywords-and-identifiers.md +++ /dev/null @@ -1,47 +0,0 @@ ---- -title: Keywords & Identifiers -toc: false ---- - -SQL statements consist of two fundamental components: - -- [__Keywords__](#keywords): Words with specific meaning in SQL like `CREATE`, `INDEX`, and `BOOL` -- [__Identifiers__](#identifiers): Names for things like databases and some functions - -## Keywords - -Keywords make up SQL's vocabulary and can have specific meaning in statements. Each SQL keyword that CockroachDB supports is on one of four lists: - -- [Reserved Keywords](sql-grammar.html#reserved_keyword) -- [Type Function Name Keywords](sql-grammar.html#type_func_name_keyword) -- [Column Name Keywords](sql-grammar.html#col_name_keyword) -- [Unreserved Keywords](sql-grammar.html#unreserved_keyword) - -Reserved keywords have fixed meanings and are not typically allowed as identifiers. All other types of keywords are considered non-reserved; they have special meanings in certain contexts and can be used as identifiers in other contexts. - -### Keyword Uses - -Most users asking about keywords want to know more about them in terms of: - -- __Names of objects__, covered on this page in [Identifiers](#identifiers) -- __Syntax__, covered in our pages [SQL Statements](sql-statements.html) and [SQL Grammar](sql-grammar.html) - -## Identifiers - -Identifiers are most commonly used as names of objects like databases, tables, or columns—because of this, the terms "name" and "identifier" are often used interchangeably. However, identifiers also have less-common uses, such as changing column labels with `SELECT`. - -### Rules for Identifiers - -In our [SQL grammar](sql-grammar.html), all values that accept an `identifier` must: - -- Begin with a Unicode letter or an underscore (_). Subsequent characters can be letters, underscores, digits (0-9), or dollar signs ($). -- Not equal any [SQL keyword](#keywords) unless the keyword is accepted by the element's syntax. For example, [`name`](sql-grammar.html#name) accepts Unreserved or Column Name keywords. - -To bypass either of these rules, simply surround the identifier with double-quotes ("). You can also use double-quotes to preserve case-sensitivity in database, table, view, and column names. However, all references to such identifiers must also include double-quotes. - -{{site.data.alerts.callout_info}}Some statements have additional requirements for identifiers. For example, each table in a database must have a unique name. These requirements are documented on each statement's page.{{site.data.alerts.end}} - -## See Also - -- [SQL Statements](sql-statements.html) -- [Full SQL Grammar](sql-grammar.html) diff --git a/src/current/v1.1/known-limitations.md b/src/current/v1.1/known-limitations.md deleted file mode 100644 index 1b9f6cf3d94..00000000000 --- a/src/current/v1.1/known-limitations.md +++ /dev/null @@ -1,193 +0,0 @@ ---- -title: Known Limitations in CockroachDB v1.1 -summary: Learn about newly identified limitations in CockroachDB as well as unresolved limitations identified in earlier releases. -toc: true ---- - -This page describes newly identified limitations in the CockroachDB v1.1 release as well as unresolved limitations identified in earlier releases. - - -## New Limitations - -### Enterprise restores after creating, dropping, or truncating tables - -{{site.data.alerts.callout_info}}As of v1.1.1, it is no longer possible to create an incremental backup if a table has been created, dropped, or truncated after the full backup. This prevents attempts to restore from a broken backup. See #19286.{{site.data.alerts.end}} - -It is not possible to perform an [enterprise `RESTORE`](restore.html) from a full [`BACKUP`](backup.html) with incremental backups if you [created](create-table.html), [dropped](drop-table.html), or [truncated](truncate.html) any tables after the full backup. Attempting to restore in this case will fail with an error. - -As a workaround, any time you create, drop, or truncate a table, perform another full `BACKUP` of your cluster. - -### Maximum cluster size - -{{site.data.alerts.callout_info}} -Resolved as of v1.2-alpha.20171026. See #17016. -{{site.data.alerts.end}} - -The locations of all ranges in a cluster are stored in a two-level index at the beginning of the key-space, known as [meta ranges](architecture/distribution-layer.html#meta-ranges), where the first level (`meta1`) addresses the second, and the second level (`meta2`) addresses data in the cluster. A limitation in v1.1 prevents `meta2` from being split; thus, the max size of a single range, 64MiB by default, limits the overall size of a cluster to 64TB. Clusters beyond this size will experience problems. - -### Available capacity metric in the Admin UI - -{% include v1.1/misc/available-capacity-metric.md %} - -### Downgrading to v1.1.0 from a later v1.1.x patch release - -If you have started or [upgraded](upgrade-cockroach-version.html#finalize-the-upgrade) a cluster using v1.1.1 or a later release, then you will not be able to downgrade the cluster to the v1.1.0 binary. This is due to an issue with the `version` setting in the v1.1.0 release that was fixed in v1.1.1. Changing between different `x.y.z` versions of the same `x.y` release is typically safe. - -## Unresolved Limitations - -### Schema changes within transactions - -Within a single [transaction](transactions.html): - -- DDL statements cannot be mixed with DML statements. As a workaround, you can split the statements into separate transactions. -- A [`CREATE TABLE`](create-table.html) statement containing [`FOREIGN KEY`](foreign-key.html) or [`INTERLEAVE`](interleave-in-parent.html) clauses cannot be followed by statements that reference the new table. This also applies to running [`TRUNCATE`](truncate.html) on such a table because `TRUNCATE` implicitly drops and recreates the table. -- A table cannot be dropped and then recreated with the same name. This is not possible within a single transaction because `DROP TABLE` does not immediately drop the name of the table. As a workaround, split the [`DROP TABLE`](drop-table.html) and [`CREATE TABLE`](create-table.html) statements into separate transactions. - -### Schema changes between executions of prepared statements - -When the schema of a table targeted by a prepared statement changes after the prepared statement is created, future executions of the prepared statement could result in an error. For example, adding a column to a table referenced in a prepared statement with a `SELECT *` clause will result in an error: - -{% include_cached copy-clipboard.html %} -~~~ sql -CREATE TABLE users (id INT PRIMARY KEY); -~~~ - -{% include_cached copy-clipboard.html %} -~~~ sql -PREPARE prep1 AS SELECT * FROM users; -~~~ - -{% include_cached copy-clipboard.html %} -~~~ sql -ALTER TABLE users ADD COLUMN name STRING; -~~~ - -{% include_cached copy-clipboard.html %} -~~~ sql -INSERT INTO users VALUES (1, 'Max Roach'); -~~~ - -{% include_cached copy-clipboard.html %} -~~~ sql -EXECUTE prep1; -~~~ - -~~~ -ERROR: cached plan must not change result type -SQLSTATE: 0A000 -~~~ - -It's therefore recommended to explicitly list result columns instead of using `SELECT *` in prepared statements, when possible. - - -## Join flags when restarting a cluster with different addresses - -In all our deployment tutorials, we provide the addresses of the first few nodes in the cluster to the `--join` flag when starting each node. In a new cluster, this ensures that all nodes are able to learn the location of the first key-value range, which is part of a meta-index identifying where all range replicas are stored, and which nodes require to initialize themselves and start accepting incoming connections. Each node also persists the addresses of all other nodes in the cluster on disk such that it can reconnect to them if the nodes in the `--join` flag ever happen to be unavailable when restarting. This ensures that a restarting node will always be able to connect to a node with a copy of the first range even if they're no longer located on the nodes in the `--join` flag. - -However, if the nodes in a cluster are restarted with different addresses for some reason, then it's not guaranteed that a copy of the first range will be on the nodes in the join flags. In such cases, the `--join` flags must form a fully-connected directed graph. The easiest way to do this is to put all of the new nodes' addresses into each node's `--join` flag, which ensures all nodes can join a node with a copy of the first key-value range. - -### `INSERT ON CONFLICT` vs. `UPSERT` - -When inserting/updating all columns of a table, and the table has no secondary indexes, we recommend using an [`UPSERT`](upsert.html) statement instead of the equivalent [`INSERT ON CONFLICT`](insert.html) statement. Whereas `INSERT ON CONFLICT` always performs a read to determine the necessary writes, the `UPSERT` statement writes without reading, making it faster. - -This issue is particularly relevant when using a simple SQL table of two columns to [simulate direct KV access](frequently-asked-questions.html#can-i-use-cockroachdb-as-a-key-value-store). In this case, be sure to use the `UPSERT` statement. - -### Repeated or combined commands in the SQL shell history - -{{site.data.alerts.callout_info}}Resolved as of v2.0.{{site.data.alerts.end}} - -Our [built-in SQL shell](use-the-built-in-sql-client.html) stores previously executed commands in the shell's history. In some cases, these commands are unexpectedly duplicated. - -Also, in some terminals, such as `st` or `xterm` without `tmux`, previously executed commands are combined into a single command in the SQL shell history. - -### Using `\|` to perform a large input in the SQL shell - -In the [built-in SQL shell](use-the-built-in-sql-client.html), using the [`\|`](use-the-built-in-sql-client.html#sql-shell-commands) operator to perform a large number of inputs from a file can cause the server to close the connection. This is because `\|` sends the entire file as a single query to the server, which can exceed the upper bound on the size of a packet the server can accept from any client (16MB). - -As a workaround, [execute the file from the command line](use-the-built-in-sql-client.html#execute-sql-statements-from-a-file) with `cat data.sql | cockroach sql` instead of from within the interactive shell. - -### New values generated by `DEFAULT` expressions during `ALTER TABLE ADD COLUMN` - -When executing an [`ALTER TABLE ADD COLUMN`](add-column.html) statement with a [`DEFAULT`](default-value.html) expression, new values generated: - -- use the default [search path](sql-name-resolution.html#search-path) regardless of the search path configured in the current session via `SET SEARCH_PATH`. -- use the UTC time zone regardless of the time zone configured in the current session via [`SET TIME ZONE`](set-vars.html). -- have no default database regardless of the default database configured in the current session via [`SET DATABASE`](set-vars.html), so you must specify the database of any tables they reference. -- use the transaction timestamp for the `statement_timestamp()` function regardless of the time at which the `ALTER` statement was issued. - -### Load-based lease rebalancing in uneven latency deployments - -When nodes are started with the [`--locality`](start-a-node.html#flags-changed-in-v1-1) flag, CockroachDB attempts to place the replica lease holder (the replica that client requests are forwarded to) on the node closest to the source of the request. This means as client requests move geographically, so too does the replica lease holder. - -However, you might see increased latency caused by a consistently high rate of lease transfers between datacenters in the following case: - -- Your cluster runs in datacenters which are very different distances away from each other. -- Each node was started with a single tier of `--locality`, e.g., `--locality=datacenter=a`. -- Most client requests get sent to a single datacenter because that's where all your application traffic is. - -To detect if this is happening, open the [Admin UI](admin-ui-access-and-navigate.html), select the **Queues** dashboard, hover over the **Replication Queue** graph, and check the **Leases Transferred / second** data point. If the value is consistently larger than 0, you should consider stopping and restarting each node with additional tiers of locality to improve request latency. - -For example, let's say that latency is 10ms from nodes in datacenter A to nodes in datacenter B but is 100ms from nodes in datacenter A to nodes in datacenter C. To ensure A's and B's relative proximity is factored into lease holder rebalancing, you could restart the nodes in datacenter A and B with a common region, `--locality=region=foo,datacenter=a` and `--locality=region=foo,datacenter=b`, while restarting nodes in datacenter C with a different region, `--locality=region=bar,datacenter=c`. - -### Overload resolution for collated strings - -Many string operations are not properly overloaded for [collated strings](collate.html), for example: - -~~~ sql -> SELECT 'string1' || 'string2'; -~~~ - -~~~ -+------------------------+ -| 'string1' || 'string2' | -+------------------------+ -| string1string2 | -+------------------------+ -(1 row) -~~~ - -~~~ sql -> SELECT ('string1' collate en) || ('string2' collate en); -~~~ - -~~~ -pq: unsupported binary operator: