From 4eb0901ac938ec1039c36a5fc5480be209b202fa Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Fri, 9 May 2025 14:58:24 -0400 Subject: [PATCH 01/20] Add initial, unconfirmed cluster setting change output --- .../releases/v25.2/cluster-setting-changes.md | 119 ++++++++++++++---- 1 file changed, 93 insertions(+), 26 deletions(-) diff --git a/src/current/_includes/releases/v25.2/cluster-setting-changes.md b/src/current/_includes/releases/v25.2/cluster-setting-changes.md index e25eaf685ce..a9f55f02684 100644 --- a/src/current/_includes/releases/v25.2/cluster-setting-changes.md +++ b/src/current/_includes/releases/v25.2/cluster-setting-changes.md @@ -1,49 +1,116 @@ -Changes to [cluster settings]({% link v25.1/cluster-settings.md %}) should be reviewed prior to upgrading. New default cluster setting values will be used unless you have manually set a value for a setting. This can be confirmed by running the SQL statement `SELECT * FROM system.settings` to view the non-default settings. +Changes to [cluster settings]({% link v25.2/cluster-settings.md %}) should be reviewed prior to upgrading. New default cluster setting values will be used unless you have manually set a value for a setting. This can be confirmed by running the SQL statement `SELECT * FROM system.settings` to view the non-default settings. -- Bullet -- Bullet -- Bullet -- Bullet -- Bullet +- [Settings added](#v25-2-0-settings-added) +- [Settings with changed defaults](#v25-2-0-settings-with-changed-defaults) +- [Settings with changed visibility](#v25-2-0-settings-with-changed-visibility) +- [Additional setting changes](#v25-2-0-additional-cluster-setting-changes) -
Settings added
+
Settings added
-- Bullet +- `backup.compaction.threshold` (reserved) -- Bullet +- `backup.compaction.window_size` (reserved) -- Bullet +- `backup.restore.online_layer_limit` (reserved) -- Bullet +- `bulkio.index_backfill.merge_max_kv_auto_retries` (reserved) -
Settings with changed defaults
+- `feature.vector_index.enabled` -- Bullet +- `kv.closed_timestamp.lead_for_global_reads_auto_tune.enabled` -- Bullet +- `kv.closed_timestamp.policy_latency_refresh_interval` (reserved) -- Bullet +- `kv.closed_timestamp.policy_refresh_interval` (reserved) -- Bullet +- `kv.lock_table.unreplicated_lock_reliability.lease_transfer.enabled` (reserved) -
Settings with changed visibility
+- `kv.lock_table.unreplicated_lock_reliability.max_flush_size` (reserved) + +- `kv.lock_table.unreplicated_lock_reliability.merge.enabled` (reserved) + +- `kv.lock_table.unreplicated_lock_reliability.split.enabled` (reserved) + +- `kv.raft.store_liveness.quiescence.enabled` (reserved) + +- `kv.replica_raft.leaderless_unavailable_threshold` + +- `kv.transaction.write_buffering.enabled` + +- `kv.transaction.write_buffering.max_buffer_size` + +- `logical_replication.consumer.immediate_mode_writer` (reserved) + +- `restore.compacted_backups.enabled` (reserved) + +- `server.child_metrics.include_aggregate.enabled` + - Introduced the cluster setting `server.child_metrics.include_aggregate.enabled`, which modifies the behavior of Prometheus metric reporting (`/_status/vars`). By default, it is set to `true`, which maintains the existing behavior. It can be sert to `false` to stop the reporting of the aggregate time series that prevents issues with double counting when querying metrics. [#141601][#141601] + +- `server.grpc.request_metrics.enabled` (reserved) + +- `server.jemalloc_purge_overhead_percent` (reserved) + +- `server.jemalloc_purge_period` (reserved) + +- `server.oidc_authentication.provider.custom_ca` + - Added the `server.oidc_authentication.provider.custom_ca` cluster setting to support custom root CA for verifying certificates while authenticating with the OIDC provider. [#140583][#140583] + +- `sql.statement_bundle.include_all_references.enabled` (reserved) + +- `sql.stats.automatic_full_collection.enabled` + +- `sql.stats.flush.batch_size` (reserved) + +- `sql.ttl.max_kv_auto_retries` (reserved) + +- `sql.vecindex.stalled_op.timeout` + +- `sql.zone_configs.default_range_modifiable_by_non_root.enabled` (reserved) + +- `sql.zone_configs.max_replicas_per_region` (reserved) + +- `ui.default_timezone` + +
Settings with changed defaults
+ +- `kv.raft.leader_fortification.fraction_enabled` has had its default changed to `1` + +- `rpc.batch_stream_pool.enabled` (reserved) has had its default changed to `true` + +- `sql.defaults.plan_cache_mode` (reserved) has had its default changed to `auto` + +- `version` has had its default changed to `25.1-upgrading-to-25.2-step-008` + - Additional [documentation]({{% cockroachcloud/provision-a-cluster-with-terraform.md %}}) is available for this setting. + +
Settings with changed visibility
The following settings are now marked `public` after previously being `reserved`. Reserved settings are not documented and their tuning by customers is not supported. -- Bullet +- `sql.stats.detailed_latency_metrics.enabled` + - Percentile latencies are no longer available for **SQL Activity**. The implementation of these percentiles was error-prone and difficult to understand because it was computed differently from the other SQL statistics collected. Customers interested in viewing percentile latencies per statement fingerprint are encouraged to use the experimental per-fingerprint histograms that can be enabled with the `sql.stats.detailed_latency_metrics.enabled` cluster setting. This will enable externalized histogram metrics via the Prometheus scrape endpoint. [#139500][#139500] + +
Additional setting changes
+ +- `ui.display_timezone` description has been updated + +- The `server.client_cert_expiration_cache.capacity` cluster setting has been removed. The `security.certificate.expiration.client` and `security.certificate.ttl.client` metrics now report the lowest value observed for a user in the last 24 hours. + +- The `kv.mvcc_gc.queue_kv_admission_control.enabled` cluster setting was retired. + +- MVCC garbage collection is now fully subject to IO admission control. Previously, it was possible for MVCC GC to cause store overload (such as LSM inversion) when a large amount of data would become eligible for garbage collection. Should any issues arise from subjecting MVCC GC to admission control, the `kv.mvcc_gc.queue_kv_admission_control.enabled` cluster setting can be set to `false` to restore the previous behavior. -
Renamed settings
+- Previously, statement bundle collection could encounter `not enough privileges` errors when retrieving necessary information (e.g., cluster settings, table statistics, etc.) when the user that requested the bundle was different from the user that actually ran the query. This is now fixed. The bug was present since v20.2 and would result in partially incomplete bundles. -- Bullet +- MVCC garbage collection is now fully subject to IO admission control. Previously, it was possible for MVCC GC to cause store overload (such as LSM inversion) when a large amounts of data would become eligible for garbage collection. Should any issues arise from subjecting MVCC GC to admission control, the `kv.mvcc_gc.queue_kv_admission_control.enabled` cluster setting can be set to `false` to restore the previous behavior. [#143122][#143122] -- Bullet +- Since v23.2 table statistics histograms have been collected for non-indexed JSON columns. Histograms are no longer collected for these columns. This reduces memory usage during table statistics collection, for both automatic and manual collection via `ANALYZE` and `CREATE STATISTICS`. This can be reverted by setting the cluster setting `sql.stats.non_indexed_json_histograms.enabled` to `true`. [#139766][#139766] -
Additional setting changes
+- Removed the `kv.snapshot_receiver.excise.enable` cluster setting. Excise is now enabled unconditionally. [#142651][#142651] -- Bullet +- When configuring the `sql.ttl.default_delete_rate_limit` cluster setting, a notice is displayed informing that the TTL rate limit is per leaseholder per node with a link to the docs. [#142061][#142061] -- Bullet +- The cluster setting `changefeed.new_webhook_sink_enabled`/`changefeed.new_webhook_sink.enabled` is no longer supported. The new webhook sink has been enabled by default since v23.2, and the first version webhook sink has been removed. [#141940][#141940] -- Bullet +- The cluster setting `changefeed.new_pubsub_sink_enabled`/`changefeed.new_pubsub_sink.enabled` is no longer supported. The new Google Cloud Pub/Sub sink has been enabled by default since v23.2, and the first version Pub/Sub sink has been removed. [#141948][#141948] -- Bullet +- The `/_admin/v1/settings` API (and therefore cluster settings console page) now returns cluster settings using the same redaction logic as querying `SHOW CLUSTER SETTINGS` and `crdb_internal.cluster_settings`. This means that only settings flagged as "sensitive" will be redacted, all other settings will be visible. The same authorization is required for this endpoint, meaning the user must be an `admin`, have `MODIFYCLUSTERSETTINGS`, or `VIEWCLUSTERSETTINGS` roles to use this API. The exception is that if the user has `VIEWACTIVITY` or `VIEWACTIVITYREDACTED`, they will see console-only settings. [#138688][#138688] From bf3099bece6d7011689da4f4c5652134fc447aee Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Fri, 9 May 2025 15:10:11 -0400 Subject: [PATCH 02/20] Add 25.2.0 file and features needing finalization --- .../releases/v25.2/upgrade-finalization.md | 12 +-- .../_includes/releases/v25.2/v25.2.0.md | 97 +++++++++++++++++++ 2 files changed, 101 insertions(+), 8 deletions(-) create mode 100644 src/current/_includes/releases/v25.2/v25.2.0.md diff --git a/src/current/_includes/releases/v25.2/upgrade-finalization.md b/src/current/_includes/releases/v25.2/upgrade-finalization.md index dded24379fa..e57478607bf 100644 --- a/src/current/_includes/releases/v25.2/upgrade-finalization.md +++ b/src/current/_includes/releases/v25.2/upgrade-finalization.md @@ -1,9 +1,5 @@ -During a major-version upgrade, certain features and performance improvements may not be available until the upgrade is finalized. In v25.1, these are: +During a major-version upgrade, certain features and performance improvements may not be available until the upgrade is finalized. In v25.2, these are: -- Bullet -- Bullet -- Bullet -- Bullet - - `SHOW JOBS` is now based on a new mechanism for storing information about the progress and status of running jobs. [#](https://github.com/cockroachdb/cockroach/pull/) - - `ALTER JOB ... OWNER TO` can now be used to transfer ownership of a job between users/roles. [#](https://github.com/cockroachdb/cockroach/pull/) - - Users can now always see and control (pause/resume/cancel) jobs that they own. [#](https://github.com/cockroachdb/cockroach/pull/) +- Row-level security +- Creating a set-returning PL/pgSQL function +- Support for the `jsonpath` data type \ No newline at end of file diff --git a/src/current/_includes/releases/v25.2/v25.2.0.md b/src/current/_includes/releases/v25.2/v25.2.0.md new file mode 100644 index 00000000000..07f320d60a6 --- /dev/null +++ b/src/current/_includes/releases/v25.2/v25.2.0.md @@ -0,0 +1,97 @@ +## v25.2.0 + +Release Date: May 12, 2025 + +With the release of CockroachDB v25.2, we've added new capabilities to help you migrate, build, and operate more efficiently. + +For a summary of the most significant changes, refer to [Feature Highlights](#v25-2-0-feature-highlights). + +{% include releases/new-release-downloads-docker-image.md release=include.release %} + +

Feature highlights

+ +This section summarizes the most significant user-facing changes in v25.2.0 and other features recently made available to CockroachDB users across versions. For a complete list of features and changes in v25.2, including bug fixes and performance improvements, refer to the [release notes]({% link releases/index.md %}#testing-releases) for previous v25.2 testing releases. You can also search the docs for sections labeled [New in v25.2](https://www.cockroachlabs.com/docs/search?query=new+in+v25.2). + +- **Feature categories** + - [CockroachDB Cloud](#v25-2-0-cloud) + - [Change Data Capture](#v25-2-0-change-data-capture) + - [Cloud File Storage](#v25-2-0-disaster-recovery) + - [SQL](#v25-2-0-sql) + - [KV](#v25-2-0-kv) + +- **Additional information** + - [Backward-incompatible changes](#v25-2-0-backward-incompatible-changes) + - [Key cluster setting changes](#v25-2-0-key-cluster-setting-changes) + - [Deprecations] (#v25-2-0-deprecations) + - [Known limitations](#v25-2-0-known-limitations) + - [Additional resources](#v25-2-0-additional-resources) + + +
+ +

CockroachDB Cloud

+ +{% include releases/v25.2/feature-highlights-cloud.html %} + +

Change Data Capture

+ +{% include releases/v25.2/feature-highlights-change-data-capture.html %} + +

Cloud File Storage

+ +{% include releases/v25.2/feature-highlights-disaster-recovery.html %} + +

SQL

+ +{% include releases/v25.2/feature-highlights-sql.html %} + +

KV

+ +{% include releases/v25.2/feature-highlights-kv.html %} + + +{% include releases/v25.2/feature-detail-key.html %} + +
+ + + +

Backward-incompatible changes

+ +{% include releases/v25.2/backward-incompatible.md %} + + + +

Features that Require Upgrade Finalization

+ +{% include releases/v25.2/upgrade-finalization.md %} + + + +

Key Cluster Setting Changes

+ +{% include releases/v25.2/cluster-setting-changes.md %} + + + +

Deprecations

+ +{% include releases/v25.2/deprecations.md %} + +

Known limitations

+ +For information about new and unresolved limitations in CockroachDB v25.2, with suggested workarounds where applicable, refer to [Known Limitations]({% link v25.2/known-limitations.md %}). + +

Additional resources

+ +Resource | Topic | Description +---------------------+--------------------------------------------+------------- +Cockroach University | [Introduction to Distributed SQL and CockroachDB](https://university.cockroachlabs.com/courses/course-v1:crl+intro-to-distributed-sql-and-cockroachdb+self-paced/about) | This course introduces the core concepts behind distributed SQL databases and describes how CockroachDB fits into this landscape. You will learn what differentiates CockroachDB from both legacy SQL and NoSQL databases and how CockroachDB ensures consistent transactions without sacrificing scale and resiliency. You'll learn about CockroachDB's seamless horizontal scalability, distributed transactions with strict ACID guarantees, and high availability and resilience. +Cockroach University | [Practical First Steps with CockroachDB](https://university.cockroachlabs.com/courses/course-v1:crl+practical-first-steps-with-crdb+self-paced/about) | This course will give you the tools you need to get started with CockroachDB. During the course, you will learn how to spin up a cluster, use the Admin UI to monitor cluster activity, and use SQL shell to solve a set of hands-on exercises. +Cockroach University | [Enterprise Application Development with CockroachDB](https://university.cockroachlabs.com/courses/course-v1:crl+client-side-txn-handling+self-paced/about) | This course is the first in a series designed to equip you with best practices for mastering application-level (client-side) transaction management in CockroachDB. We'll dive deep on common differences between CockroachDB and legacy SQL databases and help you sidestep challenges you might encounter when migrating to CockroachDB from Oracle, PostgreSQL, and MySQL. +Cockroach University | [Building a Highly Resilient Multi-region Database using CockroachDB](https://university.cockroachlabs.com/courses/course-v1:crl+intro-to-resilience-in-multi-region+self-paced/about) | This course is part of a series introducing solutions to running low-latency, highly resilient applications for data-intensive workloads on CockroachDB. In this course we focus on surviving large-scale infrastructure failures like losing an entire cloud region without losing data during recovery. We'll show you how to use CockroachDB survival goals in a multi-region cluster to implement a highly resilient database that survives node or network failures across multiple regions with zero data loss. +Docs | [Migration Overview]({% link v25.2/migration-overview.md %}) | This page summarizes the steps of migrating a database to CockroachDB, which include testing and updating your schema to work with CockroachDB, moving your data into CockroachDB, and testing and updating your application. +Docs | [Architecture Overview](https://www.cockroachlabs.com/docs/v25.2/architecture/overview) | This page provides a starting point for understanding the architecture and design choices that enable CockroachDB's scalability and consistency capabilities. +Docs | [SQL Feature Support]({% link v25.2/sql-feature-support.md %}) | The page summarizes the standard SQL features CockroachDB supports as well as common extensions to the standard. +Docs | [Change Data Capture Overview]({% link v25.2/change-data-capture-overview.md %}) | This page summarizes CockroachDB's data streaming capabilities. Change data capture (CDC) provides efficient, distributed, row-level changefeeds into a configurable sink for downstream processing such as reporting, caching, or full-text indexing. +Docs | [Backup Architecture]({% link v25.2/backup-architecture.md %}) | This page describes the backup job workflow with a high-level overview, diagrams, and more details on each phase of the job. From 97fdeda5a9e2d568e01852b6855f725e8f3c9df4 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Fri, 9 May 2025 15:18:11 -0400 Subject: [PATCH 03/20] Update stable and cloud versions --- src/current/_config_cockroachdb.yml | 4 ++-- src/current/_includes/releases/v25.2/v25.2.0.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/src/current/_config_cockroachdb.yml b/src/current/_config_cockroachdb.yml index 787f34c6185..ed575e7e25d 100644 --- a/src/current/_config_cockroachdb.yml +++ b/src/current/_config_cockroachdb.yml @@ -1,7 +1,7 @@ baseurl: /docs -current_cloud_version: v25.1 +current_cloud_version: v25.2 destination: _site/docs homepage_title: CockroachDB Docs versions: - stable: v25.1 + stable: v25.2 dev: v25.2 diff --git a/src/current/_includes/releases/v25.2/v25.2.0.md b/src/current/_includes/releases/v25.2/v25.2.0.md index 07f320d60a6..761905f1a2f 100644 --- a/src/current/_includes/releases/v25.2/v25.2.0.md +++ b/src/current/_includes/releases/v25.2/v25.2.0.md @@ -10,7 +10,7 @@ For a summary of the most significant changes, refer to [Feature Highlights](#v2

Feature highlights

-This section summarizes the most significant user-facing changes in v25.2.0 and other features recently made available to CockroachDB users across versions. For a complete list of features and changes in v25.2, including bug fixes and performance improvements, refer to the [release notes]({% link releases/index.md %}#testing-releases) for previous v25.2 testing releases. You can also search the docs for sections labeled [New in v25.2](https://www.cockroachlabs.com/docs/search?query=new+in+v25.2). +This section summarizes the most significant user-facing changes in v25.2.0 and other features recently made available to CockroachDB users across versions. For a complete list of features and changes in v25.2, including bug fixes and performance improvements, refer to the [release notes]({% link releases/index.md %}#testing-releases) for v25.2 testing releases. You can also search the docs for sections labeled [New in v25.2](https://www.cockroachlabs.com/docs/search?query=new+in+v25.2). - **Feature categories** - [CockroachDB Cloud](#v25-2-0-cloud) From 72615d533a1229972ee992270310b3b805984274 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Fri, 9 May 2025 15:25:10 -0400 Subject: [PATCH 04/20] Update releases.yml --- src/current/_data/releases.yml | 37 ++++++++++++++++++++++++++++++++-- 1 file changed, 35 insertions(+), 2 deletions(-) diff --git a/src/current/_data/releases.yml b/src/current/_data/releases.yml index db3a57ddd6b..c3eb211f138 100644 --- a/src/current/_data/releases.yml +++ b/src/current/_data/releases.yml @@ -9071,13 +9071,12 @@ a CockroachDB self-hosted cluster to this version, [contact support](https://support.cockroachlabs.com/hc/requests/new). - - release_name: v25.2.0-rc.1 major_version: v25.2 release_date: '2025-05-12' release_type: Testing go_version: go1.23.7 - sha: 4377500860ff39cc5ddf7954079ced214bd788dc + sha: TBD has_sql_only: true has_sha256sum: true mac: @@ -9098,3 +9097,37 @@ docker_arm_limited_access: false source: true previous_release: v25.2.0-beta.3 + +- release_name: v25.2.0 + major_version: v25.2 + release_date: '2025-05-12' + release_type: Production + go_version: go1.23.7 + sha: TBD + has_sql_only: true + has_sha256sum: true + mac: + mac_arm: true + mac_arm_experimental: true + mac_arm_limited_access: false + windows: true + linux: + linux_arm: true + linux_arm_experimental: false + linux_arm_limited_access: false + linux_intel_fips: true + linux_arm_fips: false + docker: + docker_image: cockroachdb/cockroach + docker_arm: true + docker_arm_experimental: false + docker_arm_limited_access: false + source: true + previous_release: v25.2.0-rc.1 + cloud_only: true + cloud_only_message_short: 'Available only for select CockroachDB Cloud clusters' + cloud_only_message: > + This version is currently available only for select + CockroachDB Cloud clusters. To request to upgrade + a CockroachDB self-hosted cluster to this version, + [contact support](https://support.cockroachlabs.com/hc/requests/new). From cedc68f99bf4dcbc0fbd7385632986716fdcaf31 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Fri, 9 May 2025 15:29:09 -0400 Subject: [PATCH 05/20] Update versions.csv major-version data --- src/current/_data/versions.csv | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/_data/versions.csv b/src/current/_data/versions.csv index 3c937caf518..28e8a899dc6 100644 --- a/src/current/_data/versions.csv +++ b/src/current/_data/versions.csv @@ -17,4 +17,4 @@ v24.1,2024-05-20,2025-05-20,2025-11-20,24.1.5,24.1.6,2024-10-21,2025-10-21,2026- v24.2,2024-08-12,2025-02-12,N/A,N/A,N/A,N/A,N/A,N/A,v24.1,release-24.2,2028-08-12 v24.3,2024-11-18,2025-11-18,2026-05-18,24.3.11,24.3.12,2025-05-05,2026-05-05,2027-05-05,v24.2,release-24.3,N/A v25.1,2025-02-18,2026-08-18,N/A,N/A,N/A,N/A,N/A,N/A,v24.3,release-25.1,N/A -v25.2,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,v25.1,release-25.2,N/A +v25.2,2025-05-12,2026-05-12,2026-11-12,N/A,N/A,N/A,N/A,N/A,v25.1,release-25.2,N/A From d97ae1cbe3a842e56a9c5ebd296ab2b3adeb9117 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Fri, 9 May 2025 15:44:57 -0400 Subject: [PATCH 06/20] Updates to releases/index.md --- src/current/releases/index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/current/releases/index.md b/src/current/releases/index.md index 17c1a81355a..7a532a84a14 100644 --- a/src/current/releases/index.md +++ b/src/current/releases/index.md @@ -113,6 +113,7 @@ As of 2024, CockroachDB is released under a staged delivery process. New release | Version | Release Type | GA date | | :---: | :---: | :---: | +| [v25.2](#v25-2) | Regular | 2025-05-12 | | [v25.1](#v25-1) | Innovation | 2025-02-18 | | [v24.3](#v24-3) | Regular | 2024-11-18 | | [v24.2]({% link releases/unsupported-versions.md %}#v24-2) | Innovation | 2024-08-12 | @@ -126,11 +127,10 @@ The following releases and their descriptions represent proposed plans that are | Version | Release Type | Expected GA date | | :---: | :---: | :---: | -| v25.2 | Regular | 2025 Q2 | | v25.3 | Innovation | 2025 Q3 | | v25.4 | Regular | 2025 Q4 | | v26.1 | Innovation | 2026 Q1 | - +| v26.2 | Regular | 2026 Q2 | ## Downloads @@ -717,5 +717,5 @@ To review the CCL, refer to the [CockroachDB Community License](https://www.cock ## Unsupported versions -Release notes for unsupported CockroachDB versions are found on [Unsupported Versions]({% link releases/unsupported-versions.md %}). +Release notes for unsupported CockroachDB versions are found on the [Unsupported Versions]({% link releases/unsupported-versions.md %}) page. From ba6530e8d752b9ba1e4985ce96f61c19e0f2a82f Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Fri, 9 May 2025 17:09:31 -0400 Subject: [PATCH 07/20] Temporarily change to today's date for preview --- src/current/_config_cockroachdb.yml | 2 +- src/current/_data/releases.yml | 31 ++--------------------------- src/current/_data/versions.csv | 2 +- 3 files changed, 4 insertions(+), 31 deletions(-) diff --git a/src/current/_config_cockroachdb.yml b/src/current/_config_cockroachdb.yml index ed575e7e25d..2f5b1787337 100644 --- a/src/current/_config_cockroachdb.yml +++ b/src/current/_config_cockroachdb.yml @@ -4,4 +4,4 @@ destination: _site/docs homepage_title: CockroachDB Docs versions: stable: v25.2 - dev: v25.2 + dev: v25.2 \ No newline at end of file diff --git a/src/current/_data/releases.yml b/src/current/_data/releases.yml index c3eb211f138..96cccf4c465 100644 --- a/src/current/_data/releases.yml +++ b/src/current/_data/releases.yml @@ -9071,36 +9071,9 @@ a CockroachDB self-hosted cluster to this version, [contact support](https://support.cockroachlabs.com/hc/requests/new). -- release_name: v25.2.0-rc.1 - major_version: v25.2 - release_date: '2025-05-12' - release_type: Testing - go_version: go1.23.7 - sha: TBD - has_sql_only: true - has_sha256sum: true - mac: - mac_arm: true - mac_arm_experimental: true - mac_arm_limited_access: false - windows: true - linux: - linux_arm: true - linux_arm_experimental: false - linux_arm_limited_access: false - linux_intel_fips: true - linux_arm_fips: false - docker: - docker_image: cockroachdb/cockroach-unstable - docker_arm: true - docker_arm_experimental: false - docker_arm_limited_access: false - source: true - previous_release: v25.2.0-beta.3 - - release_name: v25.2.0 major_version: v25.2 - release_date: '2025-05-12' + release_date: '2025-05-09' release_type: Production go_version: go1.23.7 sha: TBD @@ -9123,7 +9096,7 @@ docker_arm_experimental: false docker_arm_limited_access: false source: true - previous_release: v25.2.0-rc.1 + previous_release: v25.2.0-beta.3 cloud_only: true cloud_only_message_short: 'Available only for select CockroachDB Cloud clusters' cloud_only_message: > diff --git a/src/current/_data/versions.csv b/src/current/_data/versions.csv index 28e8a899dc6..eda70e218da 100644 --- a/src/current/_data/versions.csv +++ b/src/current/_data/versions.csv @@ -17,4 +17,4 @@ v24.1,2024-05-20,2025-05-20,2025-11-20,24.1.5,24.1.6,2024-10-21,2025-10-21,2026- v24.2,2024-08-12,2025-02-12,N/A,N/A,N/A,N/A,N/A,N/A,v24.1,release-24.2,2028-08-12 v24.3,2024-11-18,2025-11-18,2026-05-18,24.3.11,24.3.12,2025-05-05,2026-05-05,2027-05-05,v24.2,release-24.3,N/A v25.1,2025-02-18,2026-08-18,N/A,N/A,N/A,N/A,N/A,N/A,v24.3,release-25.1,N/A -v25.2,2025-05-12,2026-05-12,2026-11-12,N/A,N/A,N/A,N/A,N/A,v25.1,release-25.2,N/A +v25.2,2025-05-09,2026-05-12,2026-11-12,N/A,N/A,N/A,N/A,N/A,v25.1,release-25.2,N/A From 8c89ba1b72992f54fa00d88809ca898fc9899673 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Fri, 9 May 2025 17:46:07 -0400 Subject: [PATCH 08/20] Remove outdated licensing note --- src/current/releases/index.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/src/current/releases/index.md b/src/current/releases/index.md index 7a532a84a14..cac6d2ea253 100644 --- a/src/current/releases/index.md +++ b/src/current/releases/index.md @@ -23,10 +23,6 @@ indented in relation to the other Liquid. Please try to keep the indentation con ## Overview -{{site.data.alerts.callout_info}} -{% include common/license/evolving.md %} -{{site.data.alerts.end}} - This page explains the types and naming of CockroachDB releases and provides access to the release notes and downloads for all CockroachDB [releases](#downloads). A new major version of CockroachDB is released quarterly. After a series of testing releases, each major version receives an initial production release, followed by a series of patch releases. @@ -715,7 +711,8 @@ All binaries available on this page released prior to the release date of 24.3.0 To review the CCL, refer to the [CockroachDB Community License](https://www.cockroachlabs.com/cockroachdb-community-license) page. You can find the applicable Business Source License or third party licenses by reviewing these in the `licenses` folder for the applicable version of CockroachDB in the GitHub repository [cockroachdb/cockroach](https://github.com/cockroachdb/cockroach). See individual files for details. -## Unsupported versions + In late 2024, we retired our Core offering to consolidate on a single CockroachDB Enterprise offering under the CockroachDB Software License. This license is available at no charge for individual users and small businesses, and offers all users, free and paid, the full breadth of CockroachDB capabilities. For details, refer to the [CockroachDB licensing update](https://www.cockroachlabs.com/enterprise-license-update/) and [Licensing FAQs]({% link {{ page.version.version }}/licensing-faqs.md %}). -Release notes for unsupported CockroachDB versions are found on the [Unsupported Versions]({% link releases/unsupported-versions.md %}) page. +## Unsupported versions +Release notes for CockroachDB versions that are no longer supported are available on the [Unsupported Versions]({% link releases/unsupported-versions.md %}) page. From 0cde481703ef25bbde273caa5d0f285672df590d Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Sun, 11 May 2025 23:59:56 -0400 Subject: [PATCH 09/20] Fix link to use stable version --- src/current/releases/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/releases/index.md b/src/current/releases/index.md index cac6d2ea253..bdfaa61b702 100644 --- a/src/current/releases/index.md +++ b/src/current/releases/index.md @@ -711,7 +711,7 @@ All binaries available on this page released prior to the release date of 24.3.0 To review the CCL, refer to the [CockroachDB Community License](https://www.cockroachlabs.com/cockroachdb-community-license) page. You can find the applicable Business Source License or third party licenses by reviewing these in the `licenses` folder for the applicable version of CockroachDB in the GitHub repository [cockroachdb/cockroach](https://github.com/cockroachdb/cockroach). See individual files for details. - In late 2024, we retired our Core offering to consolidate on a single CockroachDB Enterprise offering under the CockroachDB Software License. This license is available at no charge for individual users and small businesses, and offers all users, free and paid, the full breadth of CockroachDB capabilities. For details, refer to the [CockroachDB licensing update](https://www.cockroachlabs.com/enterprise-license-update/) and [Licensing FAQs]({% link {{ page.version.version }}/licensing-faqs.md %}). +In late 2024, we retired our Core offering to consolidate on a single CockroachDB Enterprise offering under the CockroachDB Software License. This license is available at no charge for individual users and small businesses, and offers all users, free and paid, the full breadth of CockroachDB capabilities. For details, refer to the [CockroachDB licensing update](https://www.cockroachlabs.com/enterprise-license-update/) and [Licensing FAQs]({% link {{site.versions["stable"]}}/licensing-faqs.md %}). ## Unsupported versions From a778efd69ab06b20e3d159297917170a0d46411d Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 00:09:06 -0400 Subject: [PATCH 10/20] Add to Cloud Release Notes --- src/current/releases/cloud.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/src/current/releases/cloud.md b/src/current/releases/cloud.md index b326971b2e3..6cb0665c50d 100644 --- a/src/current/releases/cloud.md +++ b/src/current/releases/cloud.md @@ -14,6 +14,14 @@ Get future release notes emailed to you: {% include marketo.html formId=1083 %} +## May 12, 2025 + +CockroachDB v25.2 is now generally available for select CockroachDB Cloud {{ site.data.products.advanced }} clusters. CockroachDB v25.2 is a [Regular release]({% link releases/release-support-policy.md %}#release-types). + +For release notes, refer to [What's New in v25.2]({% link releases/v25.2.md %}). + +To get started with version 25.2, refer to [Create a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/create-an-advanced-cluster.md %}) or [Upgrade a Cluster in CockroachDB Cloud]({% link cockroachcloud/upgrade-cockroach-version.md %}). + ## April 30, 2025 You can now use the CockroachDB {{ site.data.products.cloud }} Console to [edit the labels of a cluster or folder]({% link cockroachcloud/labels.md %}). From 69f87abb42a3c4108456c5b1d159103394ce1cc9 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 14:38:07 -0400 Subject: [PATCH 11/20] Add cluster setting changes, deprecations, cloud RN --- .../releases/v25.2/cluster-setting-changes.md | 112 +----------------- .../_includes/releases/v25.2/deprecations.md | 6 +- src/current/releases/cloud.md | 2 +- 3 files changed, 9 insertions(+), 111 deletions(-) diff --git a/src/current/_includes/releases/v25.2/cluster-setting-changes.md b/src/current/_includes/releases/v25.2/cluster-setting-changes.md index a9f55f02684..279d1a361d3 100644 --- a/src/current/_includes/releases/v25.2/cluster-setting-changes.md +++ b/src/current/_includes/releases/v25.2/cluster-setting-changes.md @@ -1,116 +1,16 @@ Changes to [cluster settings]({% link v25.2/cluster-settings.md %}) should be reviewed prior to upgrading. New default cluster setting values will be used unless you have manually set a value for a setting. This can be confirmed by running the SQL statement `SELECT * FROM system.settings` to view the non-default settings. -- [Settings added](#v25-2-0-settings-added) -- [Settings with changed defaults](#v25-2-0-settings-with-changed-defaults) -- [Settings with changed visibility](#v25-2-0-settings-with-changed-visibility) -- [Additional setting changes](#v25-2-0-additional-cluster-setting-changes) -
Settings added
-- `backup.compaction.threshold` (reserved) - -- `backup.compaction.window_size` (reserved) - -- `backup.restore.online_layer_limit` (reserved) - -- `bulkio.index_backfill.merge_max_kv_auto_retries` (reserved) - -- `feature.vector_index.enabled` - -- `kv.closed_timestamp.lead_for_global_reads_auto_tune.enabled` - -- `kv.closed_timestamp.policy_latency_refresh_interval` (reserved) - -- `kv.closed_timestamp.policy_refresh_interval` (reserved) - -- `kv.lock_table.unreplicated_lock_reliability.lease_transfer.enabled` (reserved) - -- `kv.lock_table.unreplicated_lock_reliability.max_flush_size` (reserved) - -- `kv.lock_table.unreplicated_lock_reliability.merge.enabled` (reserved) - -- `kv.lock_table.unreplicated_lock_reliability.split.enabled` (reserved) - -- `kv.raft.store_liveness.quiescence.enabled` (reserved) - -- `kv.replica_raft.leaderless_unavailable_threshold` - -- `kv.transaction.write_buffering.enabled` - -- `kv.transaction.write_buffering.max_buffer_size` - -- `logical_replication.consumer.immediate_mode_writer` (reserved) - -- `restore.compacted_backups.enabled` (reserved) - -- `server.child_metrics.include_aggregate.enabled` - - Introduced the cluster setting `server.child_metrics.include_aggregate.enabled`, which modifies the behavior of Prometheus metric reporting (`/_status/vars`). By default, it is set to `true`, which maintains the existing behavior. It can be sert to `false` to stop the reporting of the aggregate time series that prevents issues with double counting when querying metrics. [#141601][#141601] - -- `server.grpc.request_metrics.enabled` (reserved) - -- `server.jemalloc_purge_overhead_percent` (reserved) - -- `server.jemalloc_purge_period` (reserved) - -- `server.oidc_authentication.provider.custom_ca` - - Added the `server.oidc_authentication.provider.custom_ca` cluster setting to support custom root CA for verifying certificates while authenticating with the OIDC provider. [#140583][#140583] - -- `sql.statement_bundle.include_all_references.enabled` (reserved) - -- `sql.stats.automatic_full_collection.enabled` - -- `sql.stats.flush.batch_size` (reserved) - -- `sql.ttl.max_kv_auto_retries` (reserved) - -- `sql.vecindex.stalled_op.timeout` - -- `sql.zone_configs.default_range_modifiable_by_non_root.enabled` (reserved) - -- `sql.zone_configs.max_replicas_per_region` (reserved) - -- `ui.default_timezone` - -
Settings with changed defaults
- -- `kv.raft.leader_fortification.fraction_enabled` has had its default changed to `1` - -- `rpc.batch_stream_pool.enabled` (reserved) has had its default changed to `true` - -- `sql.defaults.plan_cache_mode` (reserved) has had its default changed to `auto` - -- `version` has had its default changed to `25.1-upgrading-to-25.2-step-008` - - Additional [documentation]({{% cockroachcloud/provision-a-cluster-with-terraform.md %}}) is available for this setting. +- `feature.vector_index.enabled` - Set to `TRUE` to enable vector indexes. Default is `FALSE` (not enabled). +- `server.child_metrics.include_aggregate.enabled` - When `TRUE`, reports both aggregate and child Prometheus metrics, which can be helpful for quick top-level insights or backward compatibility, but should be disabled if you’re seeing inflated values in Prometheus queries due to double counting. Defaults to `TRUE`. +- `ui.default_timezone` - Allows you to set the time zone for displayed timestamps in the DB Console. (Refer to [DB Console timezone configuration]({% link v25.2/ui-overview.md %}#db-console-timezone-configuration).) Replaces the deprecated [`ui.display_timezone` cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}#setting-ui-display-timezone). If that value had been set, it will automatically be applied to the new setting `ui.default_timezone`, which takes precedence. +- `server.oidc_authentication.provider.custom_ca`- Supports a custom root CA for verifying certificates while authenticating with an OIDC provider. +- `sql.stats.automatic_full_collection.enabled` - It is now possible to automatically collect partial table statistics, but disable automatic collection of full table statistics. To do so, change this setting to `FALSE`. It defaults to `TRUE`. In addition to this cluster setting, you can use the table setting `sql_stats_automatic_full_collection_enabled`.
Settings with changed visibility
The following settings are now marked `public` after previously being `reserved`. Reserved settings are not documented and their tuning by customers is not supported. - `sql.stats.detailed_latency_metrics.enabled` - - Percentile latencies are no longer available for **SQL Activity**. The implementation of these percentiles was error-prone and difficult to understand because it was computed differently from the other SQL statistics collected. Customers interested in viewing percentile latencies per statement fingerprint are encouraged to use the experimental per-fingerprint histograms that can be enabled with the `sql.stats.detailed_latency_metrics.enabled` cluster setting. This will enable externalized histogram metrics via the Prometheus scrape endpoint. [#139500][#139500] - -
Additional setting changes
- -- `ui.display_timezone` description has been updated - -- The `server.client_cert_expiration_cache.capacity` cluster setting has been removed. The `security.certificate.expiration.client` and `security.certificate.ttl.client` metrics now report the lowest value observed for a user in the last 24 hours. - -- The `kv.mvcc_gc.queue_kv_admission_control.enabled` cluster setting was retired. - -- MVCC garbage collection is now fully subject to IO admission control. Previously, it was possible for MVCC GC to cause store overload (such as LSM inversion) when a large amount of data would become eligible for garbage collection. Should any issues arise from subjecting MVCC GC to admission control, the `kv.mvcc_gc.queue_kv_admission_control.enabled` cluster setting can be set to `false` to restore the previous behavior. - -- Previously, statement bundle collection could encounter `not enough privileges` errors when retrieving necessary information (e.g., cluster settings, table statistics, etc.) when the user that requested the bundle was different from the user that actually ran the query. This is now fixed. The bug was present since v20.2 and would result in partially incomplete bundles. - -- MVCC garbage collection is now fully subject to IO admission control. Previously, it was possible for MVCC GC to cause store overload (such as LSM inversion) when a large amounts of data would become eligible for garbage collection. Should any issues arise from subjecting MVCC GC to admission control, the `kv.mvcc_gc.queue_kv_admission_control.enabled` cluster setting can be set to `false` to restore the previous behavior. [#143122][#143122] - -- Since v23.2 table statistics histograms have been collected for non-indexed JSON columns. Histograms are no longer collected for these columns. This reduces memory usage during table statistics collection, for both automatic and manual collection via `ANALYZE` and `CREATE STATISTICS`. This can be reverted by setting the cluster setting `sql.stats.non_indexed_json_histograms.enabled` to `true`. [#139766][#139766] - -- Removed the `kv.snapshot_receiver.excise.enable` cluster setting. Excise is now enabled unconditionally. [#142651][#142651] - -- When configuring the `sql.ttl.default_delete_rate_limit` cluster setting, a notice is displayed informing that the TTL rate limit is per leaseholder per node with a link to the docs. [#142061][#142061] - -- The cluster setting `changefeed.new_webhook_sink_enabled`/`changefeed.new_webhook_sink.enabled` is no longer supported. The new webhook sink has been enabled by default since v23.2, and the first version webhook sink has been removed. [#141940][#141940] - -- The cluster setting `changefeed.new_pubsub_sink_enabled`/`changefeed.new_pubsub_sink.enabled` is no longer supported. The new Google Cloud Pub/Sub sink has been enabled by default since v23.2, and the first version Pub/Sub sink has been removed. [#141948][#141948] - -- The `/_admin/v1/settings` API (and therefore cluster settings console page) now returns cluster settings using the same redaction logic as querying `SHOW CLUSTER SETTINGS` and `crdb_internal.cluster_settings`. This means that only settings flagged as "sensitive" will be redacted, all other settings will be visible. The same authorization is required for this endpoint, meaning the user must be an `admin`, have `MODIFYCLUSTERSETTINGS`, or `VIEWCLUSTERSETTINGS` roles to use this API. The exception is that if the user has `VIEWACTIVITY` or `VIEWACTIVITYREDACTED`, they will see console-only settings. [#138688][#138688] + - Percentile latencies are no longer available for **SQL Activity**. The implementation of these percentiles was error-prone and difficult to understand because it was computed differently from the other SQL statistics collected. Customers interested in viewing percentile latencies per statement fingerprint are encouraged to use the experimental per-fingerprint histograms that can be enabled with the `sql.stats.detailed_latency_metrics.enabled` cluster setting. This will enable externalized histogram metrics via the Prometheus scrape endpoint. [#139500](https://github.com/cockroachdb/cockroach/pulls/139500) diff --git a/src/current/_includes/releases/v25.2/deprecations.md b/src/current/_includes/releases/v25.2/deprecations.md index 4a0964d1b6e..d9eea7d91dd 100644 --- a/src/current/_includes/releases/v25.2/deprecations.md +++ b/src/current/_includes/releases/v25.2/deprecations.md @@ -1,5 +1,3 @@ -The following deprecations are announced in v25.1. +The following deprecations are announced in v25.2. -- Bullet - -[#]: https://github.com/cockroachdb/cockroach/pull/ +- The [`ui.display_timezone` cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}#setting-ui-display-timezone) is now deprecated and will be removed in a future release. If it has been set, its value will automatically be applied to the new setting `ui.default_timezone`, which takes precedence. For further detail, refer to [DB Console timezone configuration]({% link v25.2/ui-overview.md %}#db-console-timezone-configuration). \ No newline at end of file diff --git a/src/current/releases/cloud.md b/src/current/releases/cloud.md index 6cb0665c50d..9f193536ee0 100644 --- a/src/current/releases/cloud.md +++ b/src/current/releases/cloud.md @@ -16,7 +16,7 @@ Get future release notes emailed to you: ## May 12, 2025 -CockroachDB v25.2 is now generally available for select CockroachDB Cloud {{ site.data.products.advanced }} clusters. CockroachDB v25.2 is a [Regular release]({% link releases/release-support-policy.md %}#release-types). +CockroachDB v25.2 is now generally available (GA) for CockroachDB Cloud {{ site.data.products.advanced }} clusters. CockroachDB v25.2 is a [Regular release]({% link releases/release-support-policy.md %}#release-types). For release notes, refer to [What's New in v25.2]({% link releases/v25.2.md %}). From ff7cc32f8ad98ecacb5e764c514fb3a985b61250 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 16:02:22 -0400 Subject: [PATCH 12/20] Add feature highlights --- ...ts-performance-and-high-availability.html} | 0 .../_includes/releases/v25.2/v25.2.0.md | 331 +++++++++++++++++- 2 files changed, 317 insertions(+), 14 deletions(-) rename src/current/_includes/releases/v25.2/{feature-highlights-disaster-recovery.html => feature-highlights-performance-and-high-availability.html} (100%) diff --git a/src/current/_includes/releases/v25.2/feature-highlights-disaster-recovery.html b/src/current/_includes/releases/v25.2/feature-highlights-performance-and-high-availability.html similarity index 100% rename from src/current/_includes/releases/v25.2/feature-highlights-disaster-recovery.html rename to src/current/_includes/releases/v25.2/feature-highlights-performance-and-high-availability.html diff --git a/src/current/_includes/releases/v25.2/v25.2.0.md b/src/current/_includes/releases/v25.2/v25.2.0.md index 761905f1a2f..efc9df61fba 100644 --- a/src/current/_includes/releases/v25.2/v25.2.0.md +++ b/src/current/_includes/releases/v25.2/v25.2.0.md @@ -14,10 +14,12 @@ This section summarizes the most significant user-facing changes in v25.2.0 and - **Feature categories** - [CockroachDB Cloud](#v25-2-0-cloud) + - [Performance and High Availability](#v25-2-0-performance-ha)> - [Change Data Capture](#v25-2-0-change-data-capture) - - [Cloud File Storage](#v25-2-0-disaster-recovery) + - [Observability](#v25-2-0-observability) + - [Security](#v25-2-0-security) - [SQL](#v25-2-0-sql) - - [KV](#v25-2-0-kv) + - [Licensing](#v25-2-0-licensing) - **Additional information** - [Backward-incompatible changes](#v25-2-0-backward-incompatible-changes) @@ -31,24 +33,325 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

CockroachDB Cloud

-{% include releases/v25.2/feature-highlights-cloud.html %} + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
+

Organize your cloud resources with labels

+

+ You can categorize your clusters & folders with custom key-value labels. Use labels to add metadata to your clusters, such as environments, teams, or applications. +

+ 		All{% include icon-no.html %}{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}
+

Switch between Basic and Standard plans in the Cloud Console

+

+ You can now change cluster plans between Basic and Standard from the CockroachDB Cloud Console. +

+ 		All{% include icon-no.html %}{% include icon-no.html %}{% include icon-yes.html %}{% include icon-yes.html %}
+ +

Performance and High Availability

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
+

Logical Data Replication is now Generally Available (GA)

+

+ Logical Data Replication (LDR) enables asynchronous data replication between CockroachDB clusters. LDR supports active-active deployments, allowing both source and destination clusters to serve traffic simultaneously, making it ideal for 2DC architectures, low-latency reads/writes, multi-cloud strategies, and workload isolation. For more information, refer to the latest documentation and an earlier blog post. +

+ 		25.2{% include icon-yes.html %}{% include icon-no.html %}{% include icon-no.html %}{% include icon-no.html %}

Change Data Capture

-{% include releases/v25.2/feature-highlights-change-data-capture.html %} - -

Cloud File Storage

- -{% include releases/v25.2/feature-highlights-disaster-recovery.html %} + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
+

Major Reduction in Duplicate Messages for Changefeeds

+

+ We’ve introduced a major improvement to changefeeds that significantly reduces the number of duplicate messages emitted during restarts and retries. This means more accurate data delivery, lower processing overhead for downstream consumers, and a smoother experience overall. This improvement is especially beneficial in systems with large tables or uneven processing speeds, where legacy checkpointing often led to unnecessary message duplication. With this update, your changefeeds are more reliable, efficient, and production-ready than ever. +

+ 		25.2{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-no.html %}
+

Enriched Changefeed format for easier integration and richer metadata

+

+ In 25.2 we’re introducing a preview of an enriched changefeed format that aligns with the Debezium message structure, making it significantly easier for to integrate CockroachDB into your existing CDC pipelines. This new format adds structured metadata and flexibility to the changefeed message body, allowing teams to seamlessly migrate from PostgreSQL or Debezium-based systems without re-architecting downstream services. Whether you're working with real-time analytics, event-driven systems, or audit logs, the enriched format provides clear context about each change event—including source information, schema, operation type, and timestamps. It simplifies debugging, enhances observability, and makes changefeeds more useful in complex, distributed architectures. This new metadata envelope is in preview in 25.2. +

+ 		25.2{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-no.html %}
+ +

Observability

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
+

Additional logs and metrics to identify and detect hotspots.

+

+ In 25.2.1, additional logs and metrics will be available to help you detect performance hotspots. During high CPU load, range logs will be emitted more frequently to the Ops channel, with added fields that highlight potential hot row and index scenarios. +

+ 		25.2{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-no.html %}
+

Configure DB Console to display timestamps in any time zone

+

+ Using a new cluster setting, you can now configure DB Console to display timestamps in any time zone. If the former cluster setting was set, its value is applied to the new setting when you upgrade to v25.2. For details, refer to [DB Console Timezone Configuration](https://www.cockroachlabs.com/docs/v25.2/ui-overview#db-console-timezone-configuration). +

+ 		25.2{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-no.html %}{% include icon-no.html %}
+

Multi-dimensional metrics

+

+ In v25.2.1, multi-dimensional metrics by application name and database name will be available in Preview, enabling you to segment and track critical SQL metrics by database or application. +

+ 		25.2{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-no.html %}
+ +

Security

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
+

Configurable TLS cipher suite restrictions

+

+ A new `cockroach start` flag, `--tls-cipher-suites`, allows administrators to restrict which supported TLS cipher suites are permitted for incoming SQL, RPC, and HTTP connections. Connections using disallowed cipher suites are rejected and logged. The restriction applies to both TLS 1.2 and TLS 1.3, enabling tighter control over cryptographic standards in secure clusters. +

+ 		25.2{% include icon-yes.html %}{% include icon-no.html %}{% include icon-no.html %}{% include icon-no.html %}
+

Row-Level Security

+

+ Controlling who can access what data is more important than ever as organizations scale and modernize their data infrastructure. As enterprises move to modernize their critical databases, they need fine-grained, built-in access controls that go beyond table-level permissions. That’s why, with the 25.2 release of CockroachDB, we’re introducing Row-Level Security — a powerful feature that allows you to define and enforce access policies at the row level, directly within the database. This form of mandatory access control enables developers and operators to tightly govern data visibility based on user roles or attributes — making it a natural fit for securing sensitive workloads and building robust multi-tenant applications. With row-level security, CockroachDB makes it simple to isolate data, comply with regulatory requirements, and reduce application-side complexity — all while maintaining performance at scale and with minimal application changes. +

+ 		25.2{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}

SQL

-{% include releases/v25.2/feature-highlights-sql.html %} - -

KV

- -{% include releases/v25.2/feature-highlights-kv.html %} - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
+

Faster index creation on large tables

+

+ Schema change operations such as index creations are now up to 30% faster based on our testing with a sample workload on a 1TB table. +

+ 		25.2{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}
+

Vector Indexing available in Preview

+

+ CockroachDB now offers [vector indexing](https://www.cockroachlabs.com/docs/v25.2/vector-indexes) in preview, enabling efficient storage and similarity search over high-dimensional data. This feature simplifies building recommendation engines, semantic search, and other machine-learning workflows directly in the database—letting you prototype and integrate advanced vector-based applications without external tooling while taking advantage of powerful SQL semantics. +

+ 		25.2{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}
+

JSONPath support in Preview

+

+ Preview support for [JSONPath](https://www.cockroachlabs.com/docs/v25.2/jsonpath) enables powerful, declarative querying and manipulation of deeply nested JSON structures—making it easier to work with complex JSON data and prototype advanced JSON-based workflows. +

+ 		25.2{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}{% include icon-yes.html %}
+ +

Licensing

+ + + + + + + + + + + + + + + + + + + + + + + + + +
FeatureAvailability
Ver.Self-hostedAdvancedStandardBasic
+

Manage Enterprise license keys in the Cloud Console

+

+ You can now manage new [Enterprise license keys](https://www.cockroachlabs.com/docs/v25.2/licensing-faqs) for CockroachDB Self-Hosted in the CockroachDB Cloud Console. This feature can help you keep better track of your license keys, their expiration dates, and important notifications. +

+ 		All{% include icon-yes.html %}{% include icon-no.html %}{% include icon-no.html %}{% include icon-no.html %}
{% include releases/v25.2/feature-detail-key.html %} From 3d91beb8e0c065f5a3b6eec8f6c95e9dc7b5df78 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 16:20:03 -0400 Subject: [PATCH 13/20] Fix links --- src/current/_includes/releases/v25.2/cluster-setting-changes.md | 2 +- src/current/_includes/releases/v25.2/deprecations.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/current/_includes/releases/v25.2/cluster-setting-changes.md b/src/current/_includes/releases/v25.2/cluster-setting-changes.md index 279d1a361d3..43ff8c1468a 100644 --- a/src/current/_includes/releases/v25.2/cluster-setting-changes.md +++ b/src/current/_includes/releases/v25.2/cluster-setting-changes.md @@ -4,7 +4,7 @@ Changes to [cluster settings]({% link v25.2/cluster-settings.md %}) should be re - `feature.vector_index.enabled` - Set to `TRUE` to enable vector indexes. Default is `FALSE` (not enabled). - `server.child_metrics.include_aggregate.enabled` - When `TRUE`, reports both aggregate and child Prometheus metrics, which can be helpful for quick top-level insights or backward compatibility, but should be disabled if you’re seeing inflated values in Prometheus queries due to double counting. Defaults to `TRUE`. -- `ui.default_timezone` - Allows you to set the time zone for displayed timestamps in the DB Console. (Refer to [DB Console timezone configuration]({% link v25.2/ui-overview.md %}#db-console-timezone-configuration).) Replaces the deprecated [`ui.display_timezone` cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}#setting-ui-display-timezone). If that value had been set, it will automatically be applied to the new setting `ui.default_timezone`, which takes precedence. +- `ui.default_timezone` - Allows you to set the time zone for displayed timestamps in the DB Console. (Refer to [DB Console timezone configuration]({% link v25.2/ui-overview.md %}#db-console-timezone-configuration).) Replaces the deprecated [`ui.display_timezone` cluster setting]({% link v25.2/cluster-settings.md %}#setting-ui-display-timezone). If that value had been set, it will automatically be applied to the new setting `ui.default_timezone`, which takes precedence. - `server.oidc_authentication.provider.custom_ca`- Supports a custom root CA for verifying certificates while authenticating with an OIDC provider. - `sql.stats.automatic_full_collection.enabled` - It is now possible to automatically collect partial table statistics, but disable automatic collection of full table statistics. To do so, change this setting to `FALSE`. It defaults to `TRUE`. In addition to this cluster setting, you can use the table setting `sql_stats_automatic_full_collection_enabled`. diff --git a/src/current/_includes/releases/v25.2/deprecations.md b/src/current/_includes/releases/v25.2/deprecations.md index d9eea7d91dd..4e322d50d81 100644 --- a/src/current/_includes/releases/v25.2/deprecations.md +++ b/src/current/_includes/releases/v25.2/deprecations.md @@ -1,3 +1,3 @@ The following deprecations are announced in v25.2. -- The [`ui.display_timezone` cluster setting]({% link {{ page.version.version }}/cluster-settings.md %}#setting-ui-display-timezone) is now deprecated and will be removed in a future release. If it has been set, its value will automatically be applied to the new setting `ui.default_timezone`, which takes precedence. For further detail, refer to [DB Console timezone configuration]({% link v25.2/ui-overview.md %}#db-console-timezone-configuration). \ No newline at end of file +- The [`ui.display_timezone` cluster setting]({% link v25.2/cluster-settings.md %}#setting-ui-display-timezone) is now deprecated and will be removed in a future release. If it has been set, its value will automatically be applied to the new setting `ui.default_timezone`, which takes precedence. For further detail, refer to [DB Console timezone configuration]({% link v25.2/ui-overview.md %}#db-console-timezone-configuration). \ No newline at end of file From f59a97367e63f2ac42dd5c0e2edb9b51915c9274 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 16:28:08 -0400 Subject: [PATCH 14/20] Fix markdown links --- src/current/_includes/releases/v25.2/v25.2.0.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/current/_includes/releases/v25.2/v25.2.0.md b/src/current/_includes/releases/v25.2/v25.2.0.md index efc9df61fba..b6e6ed0a1ed 100644 --- a/src/current/_includes/releases/v25.2/v25.2.0.md +++ b/src/current/_includes/releases/v25.2/v25.2.0.md @@ -52,7 +52,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

Organize your cloud resources with labels

- You can categorize your clusters & folders with custom key-value labels. Use labels to add metadata to your clusters, such as environments, teams, or applications. + You can categorize your clusters & folders with custom key-value labels. Use labels to add metadata to your clusters, such as environments, teams, or applications.

All @@ -190,7 +190,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

Configure DB Console to display timestamps in any time zone

- Using a new cluster setting, you can now configure DB Console to display timestamps in any time zone. If the former cluster setting was set, its value is applied to the new setting when you upgrade to v25.2. For details, refer to [DB Console Timezone Configuration](https://www.cockroachlabs.com/docs/v25.2/ui-overview#db-console-timezone-configuration). + Using a new cluster setting, you can now configure DB Console to display timestamps in any time zone. If the former cluster setting was set, its value is applied to the new setting when you upgrade to v25.2. For details, refer to DB Console Timezone Configuration).

25.2 @@ -236,7 +236,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

Configurable TLS cipher suite restrictions

- A new `cockroach start` flag, `--tls-cipher-suites`, allows administrators to restrict which supported TLS cipher suites are permitted for incoming SQL, RPC, and HTTP connections. Connections using disallowed cipher suites are rejected and logged. The restriction applies to both TLS 1.2 and TLS 1.3, enabling tighter control over cryptographic standards in secure clusters. + A new cockroach start flag, --tls-cipher-suites, allows administrators to restrict which supported TLS cipher suites are permitted for incoming SQL, RPC, and HTTP connections. Connections using disallowed cipher suites are rejected and logged. The restriction applies to both TLS 1.2 and TLS 1.3, enabling tighter control over cryptographic standards in secure clusters.

25.2 @@ -295,7 +295,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

Vector Indexing available in Preview

- CockroachDB now offers [vector indexing](https://www.cockroachlabs.com/docs/v25.2/vector-indexes) in preview, enabling efficient storage and similarity search over high-dimensional data. This feature simplifies building recommendation engines, semantic search, and other machine-learning workflows directly in the database—letting you prototype and integrate advanced vector-based applications without external tooling while taking advantage of powerful SQL semantics. + CockroachDB now offers vector indexing in preview, enabling efficient storage and similarity search over high-dimensional data. This feature simplifies building recommendation engines, semantic search, and other machine-learning workflows directly in the database—letting you prototype and integrate advanced vector-based applications without external tooling while taking advantage of powerful SQL semantics.

25.2 @@ -308,7 +308,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

JSONPath support in Preview

- Preview support for [JSONPath](https://www.cockroachlabs.com/docs/v25.2/jsonpath) enables powerful, declarative querying and manipulation of deeply nested JSON structures—making it easier to work with complex JSON data and prototype advanced JSON-based workflows. + Preview support for JSONPath enables powerful, declarative querying and manipulation of deeply nested JSON structures—making it easier to work with complex JSON data and prototype advanced JSON-based workflows.

25.2 @@ -341,7 +341,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

Manage Enterprise license keys in the Cloud Console

- You can now manage new [Enterprise license keys](https://www.cockroachlabs.com/docs/v25.2/licensing-faqs) for CockroachDB Self-Hosted in the CockroachDB Cloud Console. This feature can help you keep better track of your license keys, their expiration dates, and important notifications. + You can now manage new Enterprise license keys for CockroachDB Self-Hosted in the CockroachDB Cloud Console. This feature can help you keep better track of your license keys, their expiration dates, and important notifications.

All From 5c5b011f741d9cbffb30649c0b8ad3861fde7e92 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 16:43:13 -0400 Subject: [PATCH 15/20] Fix release page and add backward incompatible changes --- .../releases/v25.2/backward-incompatible.md | 43 +++++-------------- .../_includes/releases/v25.2/v25.2.0.md | 7 ++- 2 files changed, 13 insertions(+), 37 deletions(-) diff --git a/src/current/_includes/releases/v25.2/backward-incompatible.md b/src/current/_includes/releases/v25.2/backward-incompatible.md index 46a1d73ac04..ef5831eaa34 100644 --- a/src/current/_includes/releases/v25.2/backward-incompatible.md +++ b/src/current/_includes/releases/v25.2/backward-incompatible.md @@ -1,33 +1,10 @@ -Before [upgrading to CockroachDB v25.1]({% link v25.1/upgrade-cockroach-version.md %}), be sure to review the following backward-incompatible changes, as well as [key cluster setting changes](#v25-1-0-cluster-settings), and adjust your deployment as necessary. - -- Bullet - -- Bullet - -- Bullet - -- Bullet - -- Bullet - - Removed `sql.schema_changer.running`, which is redundant with `jobs.schema_change.currently_running`. - - Removed `sql.schema_changer.successes`, which is redundant with `jobs.schema_change.resume_completed`. - - Removed `sql.schema_changer.retry_errors`, which is redundant with `jobs.schema_change.resume_retry_error`. - - Removed `sql.schema_changer.permanent_errors`, which is redundant with `jobs.schema_change.resume_failed`. - -- Bullet - - This change is being made because CockroachDB does not have full support for multiple schema changes in a transaction, as described [here]({% link v25.1/online-schema-changes.md %}#schema-changes-within-transactions). - - Users who do not desire the autocommit behavior can preserve the old behavior by changing the default value of `autocommit_before_ddl` with a command such as: - - ``` ALTER ROLE ALL SET autocommit_before_ddl = false; ``` - - [#][#] - - -[#]: https://github.com/cockroachdb/cockroach/pull/ -[#]: https://github.com/cockroachdb/cockroach/pull/ -[#]: https://github.com/cockroachdb/cockroach/pull/ -[#]: https://github.com/cockroachdb/cockroach/pull/ -[#]: https://github.com/cockroachdb/cockroach/pull/ -[#]: https://github.com/cockroachdb/cockroach/pull/ \ No newline at end of file +Before [upgrading to CockroachDB v25.2]({% link v25.2/upgrade-cockroach-version.md %}), be sure to review the following backward-incompatible changes, as well as [key cluster setting changes](#v25-2-0-cluster-settings), and adjust your deployment as necessary. + +- Removed the `storage.queue.store-failures` metric. [#139150](https://github.com/cockroachdb/cockroach/pull/139150) +- Removed the `kv.snapshot_receiver.excise.enable` cluster setting. Excise is now enabled unconditionally. [#142651](https://github.com/cockroachdb/cockroach/pull/142651) +- The cluster setting `changefeed.new_webhook_sink_enabled`/`changefeed.new_webhook_sink.enabled` is no longer supported. The new webhook sink has been enabled by default since v23.2, and the first version webhook sink has been removed. [#141940](https://github.com/cockroachdb/cockroach/pull/141940) +- The cluster setting `changefeed.new_pubsub_sink_enabled`/`changefeed.new_pubsub_sink.enabled` is no longer supported. The new Google Cloud Pub/Sub sink has been enabled by default since v23.2, and the first version Pub/Sub sink has been removed. [#141948](https://github.com/cockroachdb/cockroach/pull/141948) +- Removed the deprecated `--storage-engine` parameter from the CLI. [#139744](https://github.com/cockroachdb/cockroach/pull/139744) +- Removed the **Paused Follower** graph from the **Replication** dashboard in the DB Console as followers are no longer paused by default from v25.1. [#141427](https://github.com/cockroachdb/cockroach/pull/141427) +- The `server.client_cert_expiration_cache.capacity` cluster setting has been removed. The `security.certificate.expiration.client` and `security.certificate.ttl.client` metrics now report the lowest value observed for a user in the last 24 hours. +- Removed the `ST_3DLength` function. \ No newline at end of file diff --git a/src/current/_includes/releases/v25.2/v25.2.0.md b/src/current/_includes/releases/v25.2/v25.2.0.md index b6e6ed0a1ed..e119ea82442 100644 --- a/src/current/_includes/releases/v25.2/v25.2.0.md +++ b/src/current/_includes/releases/v25.2/v25.2.0.md @@ -28,7 +28,6 @@ This section summarizes the most significant user-facing changes in v25.2.0 and - [Known limitations](#v25-2-0-known-limitations) - [Additional resources](#v25-2-0-additional-resources) -

CockroachDB Cloud

@@ -55,7 +54,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and You can categorize your clusters & folders with custom key-value labels. Use labels to add metadata to your clusters, such as environments, teams, or applications.

- All + All* {% include icon-no.html %} {% include icon-yes.html %} {% include icon-yes.html %} @@ -68,7 +67,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and You can now change cluster plans between Basic and Standard from the CockroachDB Cloud Console.

- All + All* {% include icon-no.html %} {% include icon-no.html %} {% include icon-yes.html %} @@ -344,7 +343,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and You can now manage new Enterprise license keys for CockroachDB Self-Hosted in the CockroachDB Cloud Console. This feature can help you keep better track of your license keys, their expiration dates, and important notifications.

- All + All* {% include icon-yes.html %} {% include icon-no.html %} {% include icon-no.html %} From e0cb314827097a278a30b595f6ea78ce3201b40a Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 16:45:40 -0400 Subject: [PATCH 16/20] Fix asterisks/key --- src/current/_includes/releases/v24.2/feature-detail-key.html | 4 ++-- src/current/_includes/releases/v24.3/feature-detail-key.html | 4 ++-- src/current/_includes/releases/v25.1/feature-detail-key.html | 4 ++-- src/current/_includes/releases/v25.2/feature-detail-key.html | 4 ++-- 4 files changed, 8 insertions(+), 8 deletions(-) diff --git a/src/current/_includes/releases/v24.2/feature-detail-key.html b/src/current/_includes/releases/v24.2/feature-detail-key.html index 3f8cccf7a37..f84c1b185a4 100644 --- a/src/current/_includes/releases/v24.2/feature-detail-key.html +++ b/src/current/_includes/releases/v24.2/feature-detail-key.html @@ -7,11 +7,11 @@ ★ - Features marked "All★" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. + Features marked "All*" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. ★★ - Features marked "All★★" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. + Features marked "All**" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. {% include icon-yes.html %} diff --git a/src/current/_includes/releases/v24.3/feature-detail-key.html b/src/current/_includes/releases/v24.3/feature-detail-key.html index e11ead7e232..95d79284eb4 100644 --- a/src/current/_includes/releases/v24.3/feature-detail-key.html +++ b/src/current/_includes/releases/v24.3/feature-detail-key.html @@ -7,11 +7,11 @@ ★ - Features marked "All★" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. + Features marked "All*" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. ★★ - Features marked "All★★" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. + Features marked "All**" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. {% include icon-yes.html %} diff --git a/src/current/_includes/releases/v25.1/feature-detail-key.html b/src/current/_includes/releases/v25.1/feature-detail-key.html index e11ead7e232..95d79284eb4 100644 --- a/src/current/_includes/releases/v25.1/feature-detail-key.html +++ b/src/current/_includes/releases/v25.1/feature-detail-key.html @@ -7,11 +7,11 @@ ★ - Features marked "All★" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. + Features marked "All*" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. ★★ - Features marked "All★★" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. + Features marked "All**" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. {% include icon-yes.html %} diff --git a/src/current/_includes/releases/v25.2/feature-detail-key.html b/src/current/_includes/releases/v25.2/feature-detail-key.html index e11ead7e232..95d79284eb4 100644 --- a/src/current/_includes/releases/v25.2/feature-detail-key.html +++ b/src/current/_includes/releases/v25.2/feature-detail-key.html @@ -7,11 +7,11 @@ ★ - Features marked "All★" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. + Features marked "All*" were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. ★★ - Features marked "All★★" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. + Features marked "All**" were recently made available via tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability. {% include icon-yes.html %} From 4f2747d2aa52a678b4b5f97e35fc5d31d8f4ede4 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 17:14:10 -0400 Subject: [PATCH 17/20] Fix links --- src/current/releases/cloud.md | 2 +- src/current/v25.2/vector-indexes.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/current/releases/cloud.md b/src/current/releases/cloud.md index 9f193536ee0..2847071b7dc 100644 --- a/src/current/releases/cloud.md +++ b/src/current/releases/cloud.md @@ -16,7 +16,7 @@ Get future release notes emailed to you: ## May 12, 2025 -CockroachDB v25.2 is now generally available (GA) for CockroachDB Cloud {{ site.data.products.advanced }} clusters. CockroachDB v25.2 is a [Regular release]({% link releases/release-support-policy.md %}#release-types). +CockroachDB v25.2 is now generally available (GA) for CockroachDB Cloud {{ site.data.products.advanced }} clusters. CockroachDB v25.2 is a [Regular release]({% link releases/index.md %}#release-types). For release notes, refer to [What's New in v25.2]({% link releases/v25.2.md %}). diff --git a/src/current/v25.2/vector-indexes.md b/src/current/v25.2/vector-indexes.md index c67e8cebd12..2f8cbea4bf9 100644 --- a/src/current/v25.2/vector-indexes.md +++ b/src/current/v25.2/vector-indexes.md @@ -147,7 +147,7 @@ For example, the following statement creates a vector index with a custom partit CREATE VECTOR INDEX ON items (category, embedding) WITH (min_partition_size=16, max_partition_size=128); ~~~ -Set the [`vector_search_beam_size` session setting]({% link {{ page.version.version }}/session-variables.md %}#vector-search-beam-size) to determine how many vector partitions will be considered during query execution. The default value is `32`, which represents the number of partitions that are explored at each level of the k-means tree. +Set the [`vector_search_beam_size` session setting]({% link {{ page.version.version }}/session-vars.md %}#vector-search-beam-size) to determine how many vector partitions will be considered during query execution. The default value is `32`, which represents the number of partitions that are explored at each level of the k-means tree. For example: From d3736d183b94dd135167aa00968c9cc67b6147b5 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 17:30:24 -0400 Subject: [PATCH 18/20] Fix backward incompatible changes --- .../releases/v25.2/backward-incompatible.md | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) diff --git a/src/current/_includes/releases/v25.2/backward-incompatible.md b/src/current/_includes/releases/v25.2/backward-incompatible.md index ef5831eaa34..33e6451cfa3 100644 --- a/src/current/_includes/releases/v25.2/backward-incompatible.md +++ b/src/current/_includes/releases/v25.2/backward-incompatible.md @@ -1,10 +1,11 @@ Before [upgrading to CockroachDB v25.2]({% link v25.2/upgrade-cockroach-version.md %}), be sure to review the following backward-incompatible changes, as well as [key cluster setting changes](#v25-2-0-cluster-settings), and adjust your deployment as necessary. -- Removed the `storage.queue.store-failures` metric. [#139150](https://github.com/cockroachdb/cockroach/pull/139150) -- Removed the `kv.snapshot_receiver.excise.enable` cluster setting. Excise is now enabled unconditionally. [#142651](https://github.com/cockroachdb/cockroach/pull/142651) -- The cluster setting `changefeed.new_webhook_sink_enabled`/`changefeed.new_webhook_sink.enabled` is no longer supported. The new webhook sink has been enabled by default since v23.2, and the first version webhook sink has been removed. [#141940](https://github.com/cockroachdb/cockroach/pull/141940) -- The cluster setting `changefeed.new_pubsub_sink_enabled`/`changefeed.new_pubsub_sink.enabled` is no longer supported. The new Google Cloud Pub/Sub sink has been enabled by default since v23.2, and the first version Pub/Sub sink has been removed. [#141948](https://github.com/cockroachdb/cockroach/pull/141948) -- Removed the deprecated `--storage-engine` parameter from the CLI. [#139744](https://github.com/cockroachdb/cockroach/pull/139744) -- Removed the **Paused Follower** graph from the **Replication** dashboard in the DB Console as followers are no longer paused by default from v25.1. [#141427](https://github.com/cockroachdb/cockroach/pull/141427) -- The `server.client_cert_expiration_cache.capacity` cluster setting has been removed. The `security.certificate.expiration.client` and `security.certificate.ttl.client` metrics now report the lowest value observed for a user in the last 24 hours. -- Removed the `ST_3DLength` function. \ No newline at end of file +- The default value of the `autocommit_before_ddl` session variable is now `true`. This will cause any schema change statement that is sent during a transaction to make the current transaction commit before executing the schema change in a separate transaction. Users who do not want the autocommit behavior can preserve the previous behavior by changing the default value of `autocommit_before_ddl` with: `ALTER ROLE ALL SET autocommit_before_ddl = false;`. [#139871] +- `DROP INDEX` can now only be run when `sql_safe_updates` is set to `false`. [#139456] +- Vector indexes do not support mutation while being created with `CREATE INDEX` or rebuilt with `ALTER PRIMARY KEY`. To prevent inadvertent application downtime, set the `sql_safe_updates` session setting to `false` when using `CREATE INDEX` or `ALTER PRIMARY KEY` with a vector index. [#144601] +- The variable arguments of polymorphic built-in functions (e.g., `concat`, `num_nulls`, `format`, `concat_ws`, etc.) no longer need to have the same type, matching PostgreSQL behavior. As a result, CockroachDB's type inference engine will no longer be able to infer argument types in some cases where it previously could, and there is a possibility that CockroachDB applications will encounter new errors. The new session variable `use_pre_25_2_variadic_builtins` restores the previous behavior (and limitations). [#144600] + +[#139871]: https://github.com/cockroachdb/cockroach/pull/139871 +[#139456]: https://github.com/cockroachdb/cockroach/pull/139456 +[#144601]: https://github.com/cockroachdb/cockroach/pull/144601 +[#144600]: https://github.com/cockroachdb/cockroach/pull/144600 \ No newline at end of file From 8d3bc346f3d16bbec627863afa99d988bfee132f Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 17:40:54 -0400 Subject: [PATCH 19/20] Fix link --- src/current/v25.2/vector-indexes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/v25.2/vector-indexes.md b/src/current/v25.2/vector-indexes.md index 2f8cbea4bf9..c67e8cebd12 100644 --- a/src/current/v25.2/vector-indexes.md +++ b/src/current/v25.2/vector-indexes.md @@ -147,7 +147,7 @@ For example, the following statement creates a vector index with a custom partit CREATE VECTOR INDEX ON items (category, embedding) WITH (min_partition_size=16, max_partition_size=128); ~~~ -Set the [`vector_search_beam_size` session setting]({% link {{ page.version.version }}/session-vars.md %}#vector-search-beam-size) to determine how many vector partitions will be considered during query execution. The default value is `32`, which represents the number of partitions that are explored at each level of the k-means tree. +Set the [`vector_search_beam_size` session setting]({% link {{ page.version.version }}/session-variables.md %}#vector-search-beam-size) to determine how many vector partitions will be considered during query execution. The default value is `32`, which represents the number of partitions that are explored at each level of the k-means tree. For example: From 4f2427439375e481d19d3429bdac5c4336fb6a2a Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 12 May 2025 17:53:07 -0400 Subject: [PATCH 20/20] Edits from review --- .../releases/v25.2/cluster-setting-changes.md | 5 ++--- src/current/_includes/releases/v25.2/v25.2.0.md | 11 ++++------- src/current/releases/cloud.md | 2 +- src/current/releases/index.md | 2 +- 4 files changed, 8 insertions(+), 12 deletions(-) diff --git a/src/current/_includes/releases/v25.2/cluster-setting-changes.md b/src/current/_includes/releases/v25.2/cluster-setting-changes.md index 43ff8c1468a..077af0321fa 100644 --- a/src/current/_includes/releases/v25.2/cluster-setting-changes.md +++ b/src/current/_includes/releases/v25.2/cluster-setting-changes.md @@ -5,12 +5,11 @@ Changes to [cluster settings]({% link v25.2/cluster-settings.md %}) should be re - `feature.vector_index.enabled` - Set to `TRUE` to enable vector indexes. Default is `FALSE` (not enabled). - `server.child_metrics.include_aggregate.enabled` - When `TRUE`, reports both aggregate and child Prometheus metrics, which can be helpful for quick top-level insights or backward compatibility, but should be disabled if you’re seeing inflated values in Prometheus queries due to double counting. Defaults to `TRUE`. - `ui.default_timezone` - Allows you to set the time zone for displayed timestamps in the DB Console. (Refer to [DB Console timezone configuration]({% link v25.2/ui-overview.md %}#db-console-timezone-configuration).) Replaces the deprecated [`ui.display_timezone` cluster setting]({% link v25.2/cluster-settings.md %}#setting-ui-display-timezone). If that value had been set, it will automatically be applied to the new setting `ui.default_timezone`, which takes precedence. -- `server.oidc_authentication.provider.custom_ca`- Supports a custom root CA for verifying certificates while authenticating with an OIDC provider. +- `server.oidc_authentication.provider.custom_ca` - Supports a custom root CA for verifying certificates while authenticating with an OIDC provider. - `sql.stats.automatic_full_collection.enabled` - It is now possible to automatically collect partial table statistics, but disable automatic collection of full table statistics. To do so, change this setting to `FALSE`. It defaults to `TRUE`. In addition to this cluster setting, you can use the table setting `sql_stats_automatic_full_collection_enabled`.
Settings with changed visibility
The following settings are now marked `public` after previously being `reserved`. Reserved settings are not documented and their tuning by customers is not supported. -- `sql.stats.detailed_latency_metrics.enabled` - - Percentile latencies are no longer available for **SQL Activity**. The implementation of these percentiles was error-prone and difficult to understand because it was computed differently from the other SQL statistics collected. Customers interested in viewing percentile latencies per statement fingerprint are encouraged to use the experimental per-fingerprint histograms that can be enabled with the `sql.stats.detailed_latency_metrics.enabled` cluster setting. This will enable externalized histogram metrics via the Prometheus scrape endpoint. [#139500](https://github.com/cockroachdb/cockroach/pulls/139500) +- `sql.stats.detailed_latency_metrics.enabled` - Percentile latencies are no longer available for **SQL Activity**. The implementation of these percentiles was error-prone and difficult to understand because it was computed differently from the other SQL statistics collected. Customers interested in viewing percentile latencies per statement fingerprint are encouraged to use the experimental per-fingerprint histograms that can be enabled with the `sql.stats.detailed_latency_metrics.enabled` cluster setting. This will enable externalized histogram metrics via the Prometheus scrape endpoint. [#139500](https://github.com/cockroachdb/cockroach/pulls/139500) diff --git a/src/current/_includes/releases/v25.2/v25.2.0.md b/src/current/_includes/releases/v25.2/v25.2.0.md index e119ea82442..59a2d77406b 100644 --- a/src/current/_includes/releases/v25.2/v25.2.0.md +++ b/src/current/_includes/releases/v25.2/v25.2.0.md @@ -130,8 +130,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

Major Reduction in Duplicate Messages for Changefeeds

- We’ve introduced a major improvement to changefeeds that significantly reduces the number of duplicate messages emitted during restarts and retries. This means more accurate data delivery, lower processing overhead for downstream consumers, and a smoother experience overall. This improvement is especially beneficial in systems with large tables or uneven processing speeds, where legacy checkpointing often led to unnecessary message duplication. With this update, your changefeeds are more reliable, efficient, and production-ready than ever. -

+ A major improvement to changefeeds significantly reduces the number of duplicate messages emitted during restarts and retries. This means more accurate data delivery, lower processing overhead for downstream consumers, and a smoother experience overall. This improvement is especially beneficial in systems with large tables or uneven processing speeds, where legacy checkpointing often led to unnecessary message duplication.

25.2 {% include icon-yes.html %} @@ -143,8 +142,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

Enriched Changefeed format for easier integration and richer metadata

- In 25.2 we’re introducing a preview of an enriched changefeed format that aligns with the Debezium message structure, making it significantly easier for to integrate CockroachDB into your existing CDC pipelines. This new format adds structured metadata and flexibility to the changefeed message body, allowing teams to seamlessly migrate from PostgreSQL or Debezium-based systems without re-architecting downstream services. Whether you're working with real-time analytics, event-driven systems, or audit logs, the enriched format provides clear context about each change event—including source information, schema, operation type, and timestamps. It simplifies debugging, enhances observability, and makes changefeeds more useful in complex, distributed architectures. This new metadata envelope is in preview in 25.2. -

+ An enriched changefeed format has been introduced in Preview that aligns with the Debezium message structure, making it significantly easier to integrate CockroachDB into existing CDC pipelines. This new format adds structured metadata and flexibility to the changefeed message body, allowing seamless migrations from PostgreSQL or Debezium-based systems without re-architecting downstream services. Whether you're working with real-time analytics, event-driven systems, or audit logs, the enriched format provides clear context about each change event, including source information, schema, operation type, and timestamps. It simplifies debugging, enhances observability, and makes changefeeds more useful in complex, distributed architectures.

25.2 {% include icon-yes.html %} @@ -307,7 +305,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

JSONPath support in Preview

- Preview support for JSONPath enables powerful, declarative querying and manipulation of deeply nested JSON structures—making it easier to work with complex JSON data and prototype advanced JSON-based workflows. + Preview support for JSONPath enables powerful, declarative querying and manipulation of deeply nested JSON structures. This makes it easier to work with complex JSON data and prototype advanced JSON-based workflows.

25.2 @@ -340,8 +338,7 @@ This section summarizes the most significant user-facing changes in v25.2.0 and

Manage Enterprise license keys in the Cloud Console

- You can now manage new Enterprise license keys for CockroachDB Self-Hosted in the CockroachDB Cloud Console. This feature can help you keep better track of your license keys, their expiration dates, and important notifications. -

+ You can now manage new Enterprise license keys for self-hosted CockroachDB clusters in the CockroachDB Cloud Console. This feature can help you keep better track of your license keys, their expiration dates, and important notifications.

All* {% include icon-yes.html %} diff --git a/src/current/releases/cloud.md b/src/current/releases/cloud.md index 2847071b7dc..25ee9aeb43d 100644 --- a/src/current/releases/cloud.md +++ b/src/current/releases/cloud.md @@ -20,7 +20,7 @@ CockroachDB v25.2 is now generally available (GA) for CockroachDB Cloud {{ site. For release notes, refer to [What's New in v25.2]({% link releases/v25.2.md %}). -To get started with version 25.2, refer to [Create a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/create-an-advanced-cluster.md %}) or [Upgrade a Cluster in CockroachDB Cloud]({% link cockroachcloud/upgrade-cockroach-version.md %}). +To get started with v25.2, refer to [Create a CockroachDB {{ site.data.products.advanced }} cluster]({% link cockroachcloud/create-an-advanced-cluster.md %}) or [Upgrade a Cluster in CockroachDB Cloud]({% link cockroachcloud/upgrade-cockroach-version.md %}). ## April 30, 2025 diff --git a/src/current/releases/index.md b/src/current/releases/index.md index bdfaa61b702..b5763109508 100644 --- a/src/current/releases/index.md +++ b/src/current/releases/index.md @@ -711,7 +711,7 @@ All binaries available on this page released prior to the release date of 24.3.0 To review the CCL, refer to the [CockroachDB Community License](https://www.cockroachlabs.com/cockroachdb-community-license) page. You can find the applicable Business Source License or third party licenses by reviewing these in the `licenses` folder for the applicable version of CockroachDB in the GitHub repository [cockroachdb/cockroach](https://github.com/cockroachdb/cockroach). See individual files for details. -In late 2024, we retired our Core offering to consolidate on a single CockroachDB Enterprise offering under the CockroachDB Software License. This license is available at no charge for individual users and small businesses, and offers all users, free and paid, the full breadth of CockroachDB capabilities. For details, refer to the [CockroachDB licensing update](https://www.cockroachlabs.com/enterprise-license-update/) and [Licensing FAQs]({% link {{site.versions["stable"]}}/licensing-faqs.md %}). +In late 2024, Cockroach Labs retired its Core offering to consolidate on a single CockroachDB Enterprise offering under the CockroachDB Software License. This license is available at no charge for individual users and small businesses, and offers all users, free and paid, the full breadth of CockroachDB capabilities. For details, refer to the [CockroachDB licensing update](https://www.cockroachlabs.com/enterprise-license-update/) and [Licensing FAQs]({% link {{site.versions["stable"]}}/licensing-faqs.md %}). ## Unsupported versions