23.1 GA Release Notes

_config_base.yml

@@ -152,12 +152,12 @@ release_info:
     start_time: 2023-05-03 12:20:58.860667 +0000 UTC
     version: v22.2.9
   v23.1:
-    build_time: 2023-05-04 00:00:00 (go1.19)
+    build_time: 2023-05-15 00:00:00 (go1.19)
     crdb_branch_name: release-23.1
-    docker_image: cockroachdb/cockroach-unstable
-    name: v23.1.0-rc.2
-    start_time: 2023-05-03 16:33:03.563820 +0000 UTC
-    version: v23.1.0-rc.2
+    docker_image: cockroachdb/cockroach
+    name: v23.1.0
+    start_time: 2023-05-15 16:33:03.563820 +0000 UTC
+    version: v23.1.0
 sass:
   quiet_deps: 'true'
   sass_dir: css

_config_cockroachdb.yml

@@ -7,4 +7,4 @@ destination: _site/docs
 homepage_title: CockroachDB Docs
 versions:
   dev: v23.1
-  stable: v22.2
+  stable: v23.1

_data/releases.yml

@@ -4314,8 +4314,6 @@
   source: true
   previous_release: v22.2.8
 
-
-
 - release_name: v22.1.20
   major_version: v22.1
   release_date: '2023-05-12'
@@ -4336,3 +4334,24 @@
     docker_arm: false
   source: true
   previous_release: v22.1.19
+
+- release_name: v23.1.0
+  major_version: v23.1
+  release_date: '2023-05-15'
+  release_type: Production
+  go_version: go1.18
+  sha: 358e0d87912365b8976c55ab9b3292e999cf720d
+  has_sql_only: true
+  has_sha256sum: true
+  mac:
+    mac_arm: true
+  windows: true
+  linux:
+    linux_arm: true
+    linux_intel_fips: true
+    linux_arm_fips: false
+  docker:
+    docker_image: cockroachdb/cockroach
+    docker_arm: true
+  source: true
+  previous_release: v23.1.0-rc.2

_data/versions.csv

@@ -11,4 +11,4 @@ v21.1,2021-05-18,2022-05-18,2022-11-18,v20.2
 v21.2,2021-11-16,2022-11-16,2023-05-16,v21.1
 v22.1,2022-05-24,2023-05-24,2023-11-24,v21.2
 v22.2,2022-12-05,2023-12-05,2024-06-05,v22.1
-v23.1,N/A,N/A,N/A,v22.2
+v23.1,2023-05-10,2024-05-15,2024-11-15,v22.2

_includes/releases/v23.1/v23.1.0-alpha.4.md

@@ -9,7 +9,7 @@ Release Date: February 27, 2023
 - Some of the transformations specific to changefeeds have been deprecated and replaced. These functions were released in limited access in v22.2.  Deprecated changefeed transformations continue to function. Closely monitor changefeeds that are created during upgrade. While effort was made to maintain backward compatibility, the updated changefeed transformation may produce slightly different output, such as different column names. [#96295][#96295]
 - Add support for implicit authentication to Azure Storage and KMS. [#96825][#96825]
 - Add support for `CREATE EXTERNAL CONNECTION ... AS "postgresql://"` or `"postgres://"`. These external connections may be specified as the source in streaming replication. [#96551][#96551]
-- Add support for referencing [user defined functions (UDFs)](../{{site.versions["stable"]}}/user-defined-functions.html) from other objects. Backup and restore operations can now read and write UDF descriptors. [#97038][#97038]
+- Add support for referencing [user defined functions (UDFs)](../v23.1/user-defined-functions.html) from other objects. Backup and restore operations can now read and write UDF descriptors. [#97038][#97038]
 
 <h3 id="v23-1-0-alpha-4-sql-language-changes">SQL language changes</h3>
 

_includes/v23.1/performance/sql-trace-txn-enable-threshold.md

@@ -1 +1,6 @@
-The default tracing behavior captures a small percent of transactions, so not all contention events will be recorded. When investigating transaction contention, you can set the `sql.trace.txn.enable_threshold` [cluster setting](cluster-settings.html#setting-sql-trace-txn-enable-threshold) to always capture contention events.
+{% if include.version_prefix != nil %}
+    {% assign url = include.version_prefix | append: "cluster-settings.html#setting-sql-trace-txn-enable-threshold" | absolute_url %}
+{% else %}
+    {% assign url = "cluster-settings.html#setting-sql-trace-txn-enable-threshold" %}
+{% endif %}
+The default tracing behavior captures a small percent of transactions, so not all contention events will be recorded. When investigating transaction contention, you can set the `sql.trace.txn.enable_threshold` [cluster setting]({{ url }}) to always capture contention events.

_includes/v23.1/ui/insights.md

@@ -84,7 +84,11 @@ To display this view, click **Insights** in the left-hand navigation of the Clou
 The rows in this page are populated from the [`crdb_internal.cluster_execution_insights`]({{ link_prefix }}crdb-internal.html) table.
 
 - The results displayed on the **Statement Executions** view will be available as long as the number of rows in each node is less than the [`sql.insights.execution_insights_capacity` cluster setting]({{ link_prefix }}cluster-settings.html#setting-sql-insights-execution-insights-capacity).
+{% if include.version_prefix != nil %}
+- {% include {{ include.version_prefix }}performance/sql-trace-txn-enable-threshold.md version_prefix=version_prefix %}
+{% else %}
 - {% include {{ page.version.version }}/performance/sql-trace-txn-enable-threshold.md %}
+{% endif %}
 {{site.data.alerts.end}}
 
 {% if page.cloud != true -%}

cockroachcloud/insights-page.md

@@ -23,7 +23,7 @@ The **Insights** page of the {{ site.data.products.db }} Console helps you:
 
 To view this page, select a cluster from the [**Clusters** page](cluster-management.html#view-clusters-page), and click **Insights** in the **Monitoring** section of the left side navigation.
 
-{% include {{version_prefix}}ui/insights.md %}
+{% include {{version_prefix}}ui/insights.md version_prefix=version_prefix %}
 
 ## See also
 

cockroachcloud/metrics-page.md

@@ -72,7 +72,7 @@ This graph shows a moving average of the number of statements with [full table a
 
 ### SQL Statement Contention 
 
-This graph shows a moving average of the number of SQL statements that experienced [contention](../{{site.versions["stable"]}}/transactions.html#transaction-contention) across the cluster.
+This graph shows a moving average of the number of SQL statements that experienced [contention](../{{site.versions["stable"]}}/performance-best-practices-overview.html#transaction-contention) across the cluster.
 
 See the [Statements page](statements-page.html) for more details on the cluster's SQL statements.
 

css/customstyles.scss

@@ -101,4 +101,13 @@ table {
   width: 100%;
   display: block;
   border: none;
+  tbody {
+    tr {
+      td {
+        strong {
+          line-height: 22px;
+        }
+      }
+    }
+  }
 }

v23.1/upgrade-cockroach-version.md

@@ -63,6 +63,12 @@ When you are ready to upgrade to {{ latest.release_name }}, continue to [step 2]
 
 Before starting the upgrade, complete the following steps.
 
+### Review breaking changes
+
+{% assign rd = site.data.versions | where_exp: "rd", "rd.major_version == page.version.version" | first %}
+
+Review the [backward-incompatible changes](../releases/{{ page.version.version }}.html{% unless rd.release_date == "N/A" or rd.release_date > today %}#{{ page.version.version | replace: ".", "-" }}-0-backward-incompatible-changes{% endunless %}), [deprecated features](../releases/{{ page.version.version }}.html#{% unless rd.release_date == "N/A" or rd.release_date > today %}{{ page.version.version | replace: ".", "-" }}-0-deprecations{% endunless %}), and [key cluster setting changes](../releases/{{ page.version.version }}.html#{% unless rd.release_date == "N/A" or rd.release_date > today %}{{ page.version.version | replace: ".", "-" }}-0-cluster-settings{% endunless %}) in {{ page.version.version }}. If any affect your deployment, make the necessary changes before starting the rolling upgrade to {{ page.version.version }}.
+
 ### Check load balancing
 
 Make sure your cluster is behind a [load balancer](recommended-production-settings.html#load-balancing), or your clients are configured to talk to multiple nodes. If your application communicates with a single node, stopping that node to upgrade its CockroachDB binary will cause your application to fail.
@@ -99,12 +105,6 @@ If your cluster contains partially-decommissioned nodes, they will block an upgr
     1. First, reissue the [decommission command](node-shutdown.html?filters=decommission#decommission-the-node). The second command typically succeeds within a few minutes.
     1. If the second decommission command does not succeed, [recommission](node-shutdown.html?filters=decommission#recommission-nodes) and then decommission it again. Before continuing the upgrade, the node must be marked as `decommissioned`.
 
-### Review breaking changes
-
-{% assign rd = site.data.versions | where_exp: "rd", "rd.major_version == page.version.version" | first %}
-
-Review the [backward-incompatible changes in {{ page.version.version }}](../releases/{{ page.version.version }}.html{% unless rd.release_date == "N/A" or rd.release_date > today %}#{{ page.version.version | replace: ".", "-" }}-0-backward-incompatible-changes{% endunless %}) and [deprecated features](../releases/{{ page.version.version }}.html#{% unless rd.release_date == "N/A" or rd.release_date > today %}{{ page.version.version | replace: ".", "-" }}-0-deprecations{% endunless %}). If any affect your deployment, make the necessary changes before starting the rolling upgrade to {{ page.version.version }}.
-
 ## Step 3. Decide how the upgrade will be finalized
 
 {{site.data.alerts.callout_info}}