Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v25.1.0-rc.1. release notes #19358

Merged
merged 13 commits into from
Feb 10, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions src/current/_data/releases.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8172,3 +8172,30 @@
docker_arm_limited_access: false
source: true
previous_release: v24.2.9

- 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
1 change: 1 addition & 0 deletions src/current/_includes/releases/v25.1/v25.1.0-alpha.1.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.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 <a href="#v25-1-0-beta-2-performance-improvements">v25.1.0-beta.2 release notes</a>.

Expand Down
49 changes: 49 additions & 0 deletions src/current/_includes/releases/v25.1/v25.1.0-rc.1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
## v25.1.0-rc.1

Release Date: February 10, 2025

{% include releases/new-release-downloads-docker-image.md release=include.release %}

<h3 id="v25-1-0-rc-1-backward-incompatible-changes">Backward-incompatible changes</h3>

- 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]({% 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; ```

[#140156][#140156]

<h3 id="v25-1-0-rc-1-sql-language-changes">SQL language changes</h3>

- 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 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]

<h3 id="v25-1-0-rc-1-bug-fixes">Bug fixes</h3>

- 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
[#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
Loading