Merge branch 'main' into update-yaml-data-links

Author: ebembi-crdb

src/current/_includes/v20.2/known-limitations/copy-from-clients.md

@@ -1,5 +1,3 @@
 The built-in SQL shell provided with CockroachDB ([`cockroach sql`](cockroach-sql.html) / [`cockroach demo`](cockroach-demo.html)) does not currently support importing data with the `COPY` statement.
 
-To load data into CockroachDB, we recommend that you use an [`IMPORT`](import.html). If you must use a `COPY` statement, you can issue the statement from the [`psql` client](https://www.postgresql.org/docs/current/app-psql.html) command provided with PostgreSQL, or from another third-party client.
-
-[Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/16392)
+To load data into CockroachDB, we recommend that you use an [`IMPORT`](import.html). If you must use a `COPY` statement, you can issue the statement from the [`psql` client](https://www.postgresql.org/docs/current/app-psql.html) command provided with PostgreSQL, or from another third-party client.

src/current/_includes/v20.2/known-limitations/copy-syntax.md

@@ -2,16 +2,8 @@ CockroachDB does not yet support the following `COPY` syntax:
 
 - `COPY ... TO`. To copy data from a CockroachDB cluster to a file, use an [`EXPORT`](export.html) statement.
 
-    [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/41608)
-
 - `COPY ... FROM CSV`
 
-    [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/51891)
-
 - `COPY ... FROM STDIN` with a delimiter other than the default tab delimiter.
 
-    [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/16407)
-
-- `COPY ... FROM ... WHERE <expr>`
-
-    [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/54580)
+- `COPY ... FROM ... WHERE <expr>`

src/current/_includes/v20.2/known-limitations/old-multi-col-stats.md

@@ -1,3 +1 @@
 When a column is dropped from a multi-column index, the {% if page.name == "cost-based-optimizer.md" %} optimizer {% else %} [optimizer](cost-based-optimizer.html) {% endif %} will not collect new statistics for the deleted column. However, the optimizer never deletes the old [multi-column statistics](create-statistics.html#create-statistics-on-multiple-columns). This can cause a buildup of statistics in `system.table_statistics` leading the optimizer to use stale statistics, which could result in sub-optimal plans. To workaround this issue and avoid these scenarios, explicitly [delete those statistics](create-statistics.html#delete-statistics) from the `system.table_statistics` table.
-
-    [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/67407)

src/current/_includes/v20.2/known-limitations/set-transaction-no-rollback.md

@@ -13,5 +13,3 @@ timezone
 ------------
 3
 ~~~
-
-[Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/69396)

src/current/_includes/v20.2/known-limitations/single-col-stats-deletion.md

@@ -1,3 +1 @@
 [Single-column statistics](create-statistics.html#create-statistics-on-a-single-column) are not deleted when columns are dropped, which could cause minor performance issues.
-
-    [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/67407)

src/current/_includes/v20.2/known-limitations/stats-refresh-upgrade.md

@@ -1,3 +1 @@
 The [automatic statistics refresher](cost-based-optimizer.html#control-statistics-refresh-rate) automatically checks whether it needs to refresh statistics for every table in the database upon startup of each node in the cluster. If statistics for a table have not been refreshed in a while, this will trigger collection of statistics for that table. If statistics have been refreshed recently, it will not force a refresh. As a result, the automatic statistics refresher does not necessarily perform a refresh of statistics after an [upgrade](upgrade-cockroach-version.html). This could cause a problem, for example, if the upgrade moves from a version without [histograms](cost-based-optimizer.html#control-histogram-collection) to a version with histograms. To refresh statistics manually, use [`CREATE STATISTICS`](create-statistics.html).
-
-    [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/issues/54816)

src/current/_includes/v20.2/known-limitations/unordered-operations.md

@@ -4,4 +4,4 @@ Unordered aggregation operations do not support disk spilling, and are limited b
 Setting `--max-sql-memory` too high could result in performance problems due to increased memory consumption.
 {{site.data.alerts.end}}
 
-See the [GitHub tracking issue](https://github.com/cockroachdb/cockroach/issues/42485) for details.
+See the for details.

src/current/_includes/v20.2/known-limitations/userfile-upload-non-recursive.md

@@ -1 +1 @@
-- `cockroach userfile upload` does not not currently allow for recursive uploads from a directory. This feature will be present with the `--recursive` flag in future versions. [Tracking GitHub Issue](https://github.com/cockroachdb/cockroach/pull/65307)
+- `cockroach userfile upload` does not not currently allow for recursive uploads from a directory. This feature will be present with the `--recursive` flag in future versions.

src/current/_includes/v20.2/orchestration/start-cockroachdb-helm-secure.md

@@ -3,7 +3,7 @@ The CockroachDB Helm chart is undergoing maintenance for compatibility with Kube
 {{site.data.alerts.end}}
 
 {{site.data.alerts.callout_info}}
-Secure CockroachDB deployments on Amazon EKS via Helm are [not yet supported](https://github.com/cockroachdb/cockroach/issues/38847).
+Secure CockroachDB deployments on Amazon EKS via Helm are not yet supported.
 {{site.data.alerts.end}}
 
 1. [Install the Helm client](https://helm.sh/docs/intro/install) (version 3.0 or higher) and add the `cockroachdb` chart repository:

src/current/_includes/v20.2/sql/savepoints-and-high-priority-transactions.md

@@ -1 +1 @@
-[`ROLLBACK TO SAVEPOINT`](rollback-transaction.html#rollback-a-nested-transaction) (for either regular savepoints or "restart savepoints" defined with `cockroach_restart`) causes a "feature not supported" error after a DDL statement in a [`HIGH PRIORITY` transaction](transactions.html#transaction-priorities), in order to avoid a transaction deadlock. For more information, see GitHub issue [#46414](https://www.github.com/cockroachdb/cockroach/issues/46414).
+[`ROLLBACK TO SAVEPOINT`](rollback-transaction.html#rollback-a-nested-transaction) (for either regular savepoints or "restart savepoints" defined with `cockroach_restart`) causes a "feature not supported" error after a DDL statement in a [`HIGH PRIORITY` transaction](transactions.html#transaction-priorities), in order to avoid a transaction deadlock.