From f0792bf40cfba44dc5ec08dd8003d12a6a2f68f1 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Fri, 7 Feb 2025 13:48:51 -0500 Subject: [PATCH 01/10] Initial script output without 25.1 branch change --- src/current/_data/releases.yml | 28 ++++++++++ .../_includes/releases/v25.1/v25.1.0-rc.1.md | 55 +++++++++++++++++++ 2 files changed, 83 insertions(+) create mode 100644 src/current/_includes/releases/v25.1/v25.1.0-rc.1.md diff --git a/src/current/_data/releases.yml b/src/current/_data/releases.yml index 6e39e7e24a0..3fec29f39c7 100644 --- a/src/current/_data/releases.yml +++ b/src/current/_data/releases.yml @@ -8200,3 +8200,31 @@ CockroachDB Cloud clusters. To request to upgrade a CockroachDB self-hosted cluster to this version, [contact support](https://support.cockroachlabs.com/hc/requests/new). + + +- release_name: v25.1.0-rc.1 + major_version: v25.1 + release_date: '2025-02-10' + release_type: Testing + go_version: go1.22.8 + sha: 839543761f65547a48b78c10af993545590bded5 + 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.1.0-beta.3 diff --git a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md new file mode 100644 index 00000000000..4659b9e090e --- /dev/null +++ b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md @@ -0,0 +1,55 @@ +## v25.1.0-rc.1 + +Release Date: February 10, 2025 + +{% include releases/new-release-downloads-docker-image.md release=include.release %} + +

Backward-incompatible changes

+ +- 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. This change is being made because CockroachDB does not have full support for multiple schema changes in a transaction, as described here: https://www.cockroachlabs.com/docs/stable/online-schema-changes#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; ``` [#140156][#140156] + +

SQL language changes

+ +- 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`. [#139898][#139898] +- The `optimizer_prefer_bounded_cardinality` session setting has been added which instructs the optimizer to prefer query plans where every expression has a guaranteed upper-bound on the number of rows it will process. This may help the optimizer produce better query plans in some cases. This setting is disabled by default. [#140245][#140245] +- The `optimizer_min_row_count` session setting has been added which sets a lower bound on row count estimates for relational expressions during query planning. A value of zero, which is the default, indicates no lower bound. Note that if this is set to a value greater than zero, a row count of zero can still be estimated for expressions with a cardinality of zero, e.g., for a contradictory filter. Setting this to a value higher than 0, such as 1, may yield better query plans in some cases, such as when statistics are frequently stale and inaccurate. [#140245][#140245] +- Fixed a bug existing only in pre-release versions of v25.1 which could cause unexpected errors during planning for `VALUES` expressions containing function calls with multiple overloads. [#140306][#140306] +- The default setting for `plan_cache_mode` has been reverted to `force_custom_plan`. Please disregard the previous release node about it being set to `auto`. [#140405][#140405] + +

Bug fixes

+ +- Fixed a bug that could cause SHOW TABLES and other introspection operations to encounter a "batch timestamp must be after replica GC threshold" error. [#140078][#140078] +- Fixed a bug existing only in pre-release versions of v25.1. The bug could cause creation of a PL/pgSQL routine with a CTE to fail with an error like the following: `unexpected root expression: with`. [#140145][#140145] +- Fix a rare bug in which a query might fail with error "could not find computed column expression for column in table" while dropping a virtual computed column from the table. This bug was introduced in v23.2.4. [#139834][#139834] +- Configuring replication controls on a partition name of an index that is not unique across all indexes will correctly impact only that partition. [#140293][#140293] +- Data distribution page in advanced debug will no longer crash if there are null values for `raw_sql_config` in `crdb_internal.zones`. [#140609][#140609] + +

Miscellaneous

+ +

Changes without release note annotation

+ +- [#140252][#140252] [2ea91e321][2ea91e321] +- [#140089][#140089] [62c075413][62c075413] release-25.1: Revert "sql/stats: generation count was incorrectly incremented on each look up" +- [#140089][#140089] [76944423e][76944423e] release-25.1: Revert "sql/stats: generation count was incorrectly incremented on each look up" + +

Doc updates

+ +{% comment %}Docs team: Please add these manually.{% endcomment %} + + + +[#139834]: https://github.com/cockroachdb/cockroach/pull/139834 +[#139898]: https://github.com/cockroachdb/cockroach/pull/139898 +[#140078]: https://github.com/cockroachdb/cockroach/pull/140078 +[#140089]: https://github.com/cockroachdb/cockroach/pull/140089 +[#140145]: https://github.com/cockroachdb/cockroach/pull/140145 +[#140156]: https://github.com/cockroachdb/cockroach/pull/140156 +[#140245]: https://github.com/cockroachdb/cockroach/pull/140245 +[#140252]: https://github.com/cockroachdb/cockroach/pull/140252 +[#140293]: https://github.com/cockroachdb/cockroach/pull/140293 +[#140306]: https://github.com/cockroachdb/cockroach/pull/140306 +[#140405]: https://github.com/cockroachdb/cockroach/pull/140405 +[#140609]: https://github.com/cockroachdb/cockroach/pull/140609 +[2ea91e321]: https://github.com/cockroachdb/cockroach/commit/2ea91e321 +[62c075413]: https://github.com/cockroachdb/cockroach/commit/62c075413 +[76944423e]: https://github.com/cockroachdb/cockroach/commit/76944423e From 40130b664a73ca0f7ebcf3be7df780d84a8e4393 Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Fri, 7 Feb 2025 14:11:45 -0500 Subject: [PATCH 02/10] Edits --- .../releases/v25.1/v25.1.0-alpha.1.md | 1 + .../_includes/releases/v25.1/v25.1.0-rc.1.md | 42 ++++++++----------- 2 files changed, 19 insertions(+), 24 deletions(-) diff --git a/src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md b/src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md index 9a1c7af4a42..5844208cd89 100644 --- a/src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md +++ b/src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md @@ -112,6 +112,7 @@ Release Date: December 19, 2024 - Performance for some PL/pgSQL loops is now significantly improved, by as much as 3–4 times. This is due to applying tail-call optimization in more cases to the recursive sub-routines that implement loops. [#135145][#135145] - Improved the internal caching logic for role membership information. This reduces the latency impact of commands such as `DROP ROLE`, `CREATE ROLE`, and `GRANT role TO user`, which cause the role membership cache to be invalidated. [#135852][#135852] - The session variable `plan_cache_mode` now defaults to `auto`, enabling generic query plans for some queries. [#135668][#135668] + - This change is reverted in v25.1-rc.1, so this note can be disregarded whe running the latest testing release and v25.1 production releases, unless otherwise noted. - GRPC streams are now pooled across unary intra-cluster RPCs, allowing for reuse of gRPC resources to reduce the cost of remote key-value layer access. This pooling can be disabled using the `rpc.batch_stream_pool.enabled` cluster setting. [#136648][#136648] - This information was updated in the v25.1.0-beta.2 release notes. diff --git a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md index 4659b9e090e..ac11f16ebb4 100644 --- a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md +++ b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md @@ -6,37 +6,31 @@ Release Date: February 10, 2025

Backward-incompatible changes

-- 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. This change is being made because CockroachDB does not have full support for multiple schema changes in a transaction, as described here: https://www.cockroachlabs.com/docs/stable/online-schema-changes#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; ``` [#140156][#140156] +- 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. -

SQL language changes

- -- 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`. [#139898][#139898] -- The `optimizer_prefer_bounded_cardinality` session setting has been added which instructs the optimizer to prefer query plans where every expression has a guaranteed upper-bound on the number of rows it will process. This may help the optimizer produce better query plans in some cases. This setting is disabled by default. [#140245][#140245] -- The `optimizer_min_row_count` session setting has been added which sets a lower bound on row count estimates for relational expressions during query planning. A value of zero, which is the default, indicates no lower bound. Note that if this is set to a value greater than zero, a row count of zero can still be estimated for expressions with a cardinality of zero, e.g., for a contradictory filter. Setting this to a value higher than 0, such as 1, may yield better query plans in some cases, such as when statistics are frequently stale and inaccurate. [#140245][#140245] -- Fixed a bug existing only in pre-release versions of v25.1 which could cause unexpected errors during planning for `VALUES` expressions containing function calls with multiple overloads. [#140306][#140306] -- The default setting for `plan_cache_mode` has been reverted to `force_custom_plan`. Please disregard the previous release node about it being set to `auto`. [#140405][#140405] - -

Bug fixes

+ 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). -- Fixed a bug that could cause SHOW TABLES and other introspection operations to encounter a "batch timestamp must be after replica GC threshold" error. [#140078][#140078] -- Fixed a bug existing only in pre-release versions of v25.1. The bug could cause creation of a PL/pgSQL routine with a CTE to fail with an error like the following: `unexpected root expression: with`. [#140145][#140145] -- Fix a rare bug in which a query might fail with error "could not find computed column expression for column in table" while dropping a virtual computed column from the table. This bug was introduced in v23.2.4. [#139834][#139834] -- Configuring replication controls on a partition name of an index that is not unique across all indexes will correctly impact only that partition. [#140293][#140293] -- Data distribution page in advanced debug will no longer crash if there are null values for `raw_sql_config` in `crdb_internal.zones`. [#140609][#140609] + 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` -

Miscellaneous

+ ``` ALTER ROLE ALL SET autocommit_before_ddl = false; ``` + + [#140156][#140156] -

Changes without release note annotation

- -- [#140252][#140252] [2ea91e321][2ea91e321] -- [#140089][#140089] [62c075413][62c075413] release-25.1: Revert "sql/stats: generation count was incorrectly incremented on each look up" -- [#140089][#140089] [76944423e][76944423e] release-25.1: Revert "sql/stats: generation count was incorrectly incremented on each look up" - -

Doc updates

+

SQL language changes

-{% comment %}Docs team: Please add these manually.{% endcomment %} +- 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`. The previous behavior can be reenabled by setting the cluster setting `sql.stats.non_indexed_json_histograms.enabled` to `true`. [#139898][#139898] +- Added the session setting `optimizer_prefer_bounded_cardinality` which instructs the optimizer to prefer query plans where every expression has a guaranteed upper-bound on the number of rows it will process. This may help the optimizer produce better query plans in some cases. This setting is disabled by default. [#140245][#140245] +- Added the session setting `optimizer_min_row_count` which sets a lower bound on row-count estimates for relational expressions during query planning. A value of zero, which is the default, indicates no lower bound. Note that if this is set to a value greater than zero, a row count of zero can still be estimated for expressions with a cardinality of zero, e.g., for a contradictory filter. Setting this to a value higher than 0, such as 1, may yield better query plans in some cases, such as when statistics are frequently stale and inaccurate. [#140245][#140245] +- Fixed a bug existing only in testing releases of v25.1 which could cause unexpected errors during planning for `VALUES` expressions containing function calls with multiple overloads. [#140306][#140306] +- The default setting for `plan_cache_mode` has been reverted to `force_custom_plan`, after being changed to `auto` in a [prior testing release]({% link releases/v25.1.md %}#v25-1-0-alpha-1). You can disregard the [previous release note]({% link releases/v25.1.md %}#v25-1-0-alpha-1-performance-improvements). [#140405][#140405] +

Bug fixes

+- Fixed a bug that could cause `SHOW TABLES` and other introspection operations to encounter a "batch timestamp must be after replica GC threshold" error. [#140078][#140078] +- Fixed a bug existing only in testing releases of v25.1 that could cause the creation of a PL/pgSQL routine with a CTE to fail with an error similar to: `unexpected root expression: with`. [#140145][#140145] +- Fixed a rare bug in which a query might fail with error "could not find computed column expression for column in table" while dropping a virtual computed column from the table. This bug was introduced in v23.2.4. [#139834][#139834] +- Configuring replication controls on a partition name of an index that is not unique across all indexes will now correctly impact only that partition. [#140293][#140293] +- The Data Distribution page in Advanced Debug will no longer crash if there are null values for `raw_sql_config` in `crdb_internal.zones`. [#140609][#140609] [#139834]: https://github.com/cockroachdb/cockroach/pull/139834 [#139898]: https://github.com/cockroachdb/cockroach/pull/139898 From 46e1f2ac500cd495625dbd3c4d3e93e7d9945d4d Mon Sep 17 00:00:00 2001 From: Mike Lewis <76072290+mikeCRL@users.noreply.github.com> Date: Fri, 7 Feb 2025 15:19:12 -0500 Subject: [PATCH 03/10] Update src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md Co-authored-by: Florence Morris --- src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md b/src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md index 5844208cd89..7b56990601b 100644 --- a/src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md +++ b/src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md @@ -112,7 +112,7 @@ Release Date: December 19, 2024 - Performance for some PL/pgSQL loops is now significantly improved, by as much as 3–4 times. This is due to applying tail-call optimization in more cases to the recursive sub-routines that implement loops. [#135145][#135145] - Improved the internal caching logic for role membership information. This reduces the latency impact of commands such as `DROP ROLE`, `CREATE ROLE`, and `GRANT role TO user`, which cause the role membership cache to be invalidated. [#135852][#135852] - The session variable `plan_cache_mode` now defaults to `auto`, enabling generic query plans for some queries. [#135668][#135668] - - This change is reverted in v25.1-rc.1, so this note can be disregarded whe running the latest testing release and v25.1 production releases, unless otherwise noted. + - This change is reverted in v25.1.0-rc.1, so this note can be disregarded when running the latest testing release and v25.1 production releases, unless otherwise noted. - GRPC streams are now pooled across unary intra-cluster RPCs, allowing for reuse of gRPC resources to reduce the cost of remote key-value layer access. This pooling can be disabled using the `rpc.batch_stream_pool.enabled` cluster setting. [#136648][#136648] - This information was updated in the v25.1.0-beta.2 release notes. From ba38251448f74b3686385fa48501385ec7c83281 Mon Sep 17 00:00:00 2001 From: Mike Lewis <76072290+mikeCRL@users.noreply.github.com> Date: Fri, 7 Feb 2025 15:19:25 -0500 Subject: [PATCH 04/10] Update src/current/_includes/releases/v25.1/v25.1.0-rc.1.md Co-authored-by: Florence Morris --- src/current/_includes/releases/v25.1/v25.1.0-rc.1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md index ac11f16ebb4..e6e14827c78 100644 --- a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md +++ b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md @@ -10,7 +10,7 @@ Release Date: February 10, 2025 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` + 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; ``` From dae0aa640a2427bc994ad33b5d1ef579d3262ded Mon Sep 17 00:00:00 2001 From: Mike Lewis <76072290+mikeCRL@users.noreply.github.com> Date: Fri, 7 Feb 2025 15:19:44 -0500 Subject: [PATCH 05/10] Update src/current/_includes/releases/v25.1/v25.1.0-rc.1.md Co-authored-by: Florence Morris --- src/current/_includes/releases/v25.1/v25.1.0-rc.1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md index e6e14827c78..203b89d1df5 100644 --- a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md +++ b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md @@ -18,7 +18,7 @@ Release Date: February 10, 2025

SQL language changes

-- 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`. The previous behavior can be reenabled by setting the cluster setting `sql.stats.non_indexed_json_histograms.enabled` to `true`. [#139898][#139898] +- 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`. The previous behavior can be re-enabled by setting the cluster setting `sql.stats.non_indexed_json_histograms.enabled` to `true`. [#139898][#139898] - Added the session setting `optimizer_prefer_bounded_cardinality` which instructs the optimizer to prefer query plans where every expression has a guaranteed upper-bound on the number of rows it will process. This may help the optimizer produce better query plans in some cases. This setting is disabled by default. [#140245][#140245] - Added the session setting `optimizer_min_row_count` which sets a lower bound on row-count estimates for relational expressions during query planning. A value of zero, which is the default, indicates no lower bound. Note that if this is set to a value greater than zero, a row count of zero can still be estimated for expressions with a cardinality of zero, e.g., for a contradictory filter. Setting this to a value higher than 0, such as 1, may yield better query plans in some cases, such as when statistics are frequently stale and inaccurate. [#140245][#140245] - Fixed a bug existing only in testing releases of v25.1 which could cause unexpected errors during planning for `VALUES` expressions containing function calls with multiple overloads. [#140306][#140306] From 03939e4f1106365008f73674e93dac9a0d1e2020 Mon Sep 17 00:00:00 2001 From: Mike Lewis <76072290+mikeCRL@users.noreply.github.com> Date: Fri, 7 Feb 2025 15:19:54 -0500 Subject: [PATCH 06/10] Update src/current/_includes/releases/v25.1/v25.1.0-rc.1.md Co-authored-by: Florence Morris --- src/current/_includes/releases/v25.1/v25.1.0-rc.1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md index 203b89d1df5..bed9578fd45 100644 --- a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md +++ b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md @@ -26,7 +26,7 @@ Release Date: February 10, 2025

Bug fixes

-- Fixed a bug that could cause `SHOW TABLES` and other introspection operations to encounter a "batch timestamp must be after replica GC threshold" error. [#140078][#140078] +- Fixed a bug that could cause `SHOW TABLES` and other introspection operations to encounter a `batch timestamp ... must be after replica GC threshold` error. [#140078][#140078] - Fixed a bug existing only in testing releases of v25.1 that could cause the creation of a PL/pgSQL routine with a CTE to fail with an error similar to: `unexpected root expression: with`. [#140145][#140145] - Fixed a rare bug in which a query might fail with error "could not find computed column expression for column in table" while dropping a virtual computed column from the table. This bug was introduced in v23.2.4. [#139834][#139834] - Configuring replication controls on a partition name of an index that is not unique across all indexes will now correctly impact only that partition. [#140293][#140293] From de8fde42c31911a0a98e97ae2851797200a30416 Mon Sep 17 00:00:00 2001 From: Mike Lewis <76072290+mikeCRL@users.noreply.github.com> Date: Fri, 7 Feb 2025 15:26:15 -0500 Subject: [PATCH 07/10] Apply remaining suggestions from code review Co-authored-by: Florence Morris --- src/current/_includes/releases/v25.1/v25.1.0-rc.1.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md index bed9578fd45..6b7cb1c7df1 100644 --- a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md +++ b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md @@ -21,16 +21,16 @@ Release Date: February 10, 2025 - 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`. The previous behavior can be re-enabled by setting the cluster setting `sql.stats.non_indexed_json_histograms.enabled` to `true`. [#139898][#139898] - Added the session setting `optimizer_prefer_bounded_cardinality` which instructs the optimizer to prefer query plans where every expression has a guaranteed upper-bound on the number of rows it will process. This may help the optimizer produce better query plans in some cases. This setting is disabled by default. [#140245][#140245] - Added the session setting `optimizer_min_row_count` which sets a lower bound on row-count estimates for relational expressions during query planning. A value of zero, which is the default, indicates no lower bound. Note that if this is set to a value greater than zero, a row count of zero can still be estimated for expressions with a cardinality of zero, e.g., for a contradictory filter. Setting this to a value higher than 0, such as 1, may yield better query plans in some cases, such as when statistics are frequently stale and inaccurate. [#140245][#140245] -- Fixed a bug existing only in testing releases of v25.1 which could cause unexpected errors during planning for `VALUES` expressions containing function calls with multiple overloads. [#140306][#140306] +- Fixed a bug existing only in testing releases of v25.1 that could cause unexpected errors during planning for `VALUES` expressions containing function calls with multiple overloads. [#140306][#140306] - The default setting for `plan_cache_mode` has been reverted to `force_custom_plan`, after being changed to `auto` in a [prior testing release]({% link releases/v25.1.md %}#v25-1-0-alpha-1). You can disregard the [previous release note]({% link releases/v25.1.md %}#v25-1-0-alpha-1-performance-improvements). [#140405][#140405]

Bug fixes

- Fixed a bug that could cause `SHOW TABLES` and other introspection operations to encounter a `batch timestamp ... must be after replica GC threshold` error. [#140078][#140078] - Fixed a bug existing only in testing releases of v25.1 that could cause the creation of a PL/pgSQL routine with a CTE to fail with an error similar to: `unexpected root expression: with`. [#140145][#140145] -- Fixed a rare bug in which a query might fail with error "could not find computed column expression for column in table" while dropping a virtual computed column from the table. This bug was introduced in v23.2.4. [#139834][#139834] +- Fixed a rare bug in which a query might fail with error `could not find computed column expression for column ... in table` while dropping a virtual computed column from the table. This bug was introduced in v23.2.4. [#139834][#139834] - Configuring replication controls on a partition name of an index that is not unique across all indexes will now correctly impact only that partition. [#140293][#140293] -- The Data Distribution page in Advanced Debug will no longer crash if there are null values for `raw_sql_config` in `crdb_internal.zones`. [#140609][#140609] +- The Data Distribution page in Advanced Debug will no longer crash if there are `NULL` values for `raw_sql_config` in `crdb_internal.zones`. [#140609][#140609] [#139834]: https://github.com/cockroachdb/cockroach/pull/139834 [#139898]: https://github.com/cockroachdb/cockroach/pull/139898 From 278bf1656ea9fc59d51d6e42cb1bac600c503b69 Mon Sep 17 00:00:00 2001 From: Mike Lewis <76072290+mikeCRL@users.noreply.github.com> Date: Fri, 7 Feb 2025 15:55:34 -0500 Subject: [PATCH 08/10] Update src/current/_includes/releases/v25.1/v25.1.0-rc.1.md --- src/current/_includes/releases/v25.1/v25.1.0-rc.1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md index 6b7cb1c7df1..125ade072bc 100644 --- a/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md +++ b/src/current/_includes/releases/v25.1/v25.1.0-rc.1.md @@ -10,7 +10,7 @@ Release Date: February 10, 2025 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 + 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; ``` From f0cb1839a645c96e873ea3f39eaaeca12bd56b3c Mon Sep 17 00:00:00 2001 From: mikeCRL Date: Mon, 10 Feb 2025 12:20:15 -0500 Subject: [PATCH 09/10] Update version-specific remote includes to use release-25.1 branch --- 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 45c9397872a..278e4c377bd 100644 --- a/src/current/_data/versions.csv +++ b/src/current/_data/versions.csv @@ -16,4 +16,4 @@ v23.2,2024-02-05,2025-02-05,2025-08-05,23.2.6,23.2.7,2024-07-08,2025-07-08,2026- v24.1,2024-05-20,2025-05-20,2025-11-20,24.1.5,24.1.6,2024-10-21,2025-10-21,2026-10-21,v23.2,release-24.1 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 v24.3,2024-11-18,2025-11-18,2026-05-18,N/A,N/A,N/A,N/A,N/A,v24.2,release-24.3 -v25.1,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,v24.3,release-24.3 +v25.1,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,v24.3,release-25.1 From ccc27975f7c193d960b806fc2b66e7bbb9b1ef99 Mon Sep 17 00:00:00 2001 From: Mike Lewis <76072290+mikeCRL@users.noreply.github.com> Date: Mon, 10 Feb 2025 15:56:48 -0500 Subject: [PATCH 10/10] Revert versions.csv branch name change --- 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 278e4c377bd..45c9397872a 100644 --- a/src/current/_data/versions.csv +++ b/src/current/_data/versions.csv @@ -16,4 +16,4 @@ v23.2,2024-02-05,2025-02-05,2025-08-05,23.2.6,23.2.7,2024-07-08,2025-07-08,2026- v24.1,2024-05-20,2025-05-20,2025-11-20,24.1.5,24.1.6,2024-10-21,2025-10-21,2026-10-21,v23.2,release-24.1 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 v24.3,2024-11-18,2025-11-18,2026-05-18,N/A,N/A,N/A,N/A,N/A,v24.2,release-24.3 -v25.1,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,v24.3,release-25.1 +v25.1,N/A,N/A,N/A,N/A,N/A,N/A,N/A,N/A,v24.3,release-24.3