Release Notes for v25.2-v25.2.0-alpha.3

src/current/_data/releases.yml

@@ -8644,3 +8644,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.2.0-alpha.3
+  major_version: v25.2
+  release_date: '2025-04-07'
+  release_type: Testing
+  go_version: go1.23.7
+  sha: 8c5593566153523828f2a2c329f4bc1a0001f0ae
+  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-alpha.2

src/current/_includes/releases/v25.2/v25.2.0-alpha.3.md

@@ -0,0 +1,87 @@
+## v25.2.0-alpha.3
+
+Release Date: April 7, 2025
+
+{% include releases/new-release-downloads-docker-image.md release=include.release %}
+
+<h3 id="v25-2-0-alpha-3-sql-language-changes">SQL language changes</h3>
+
+- `last` is now supported for array indexing in JSONPath queries. For example, `SELECT jsonb_path_query('[1, 2, 3, 4]', '$[1 to last]');`.
+ [#143658][#143658]
+- String comparisons are now supported in JSONPath queries. For example, `SELECT jsonb_path_query('{}', '"a" < "b"');`.
+ [#143240][#143240]
+- Added the `ST_3DLength` function, which returns the 3D or 2D length of `LINESTRING` and `MULTILINESTRING` spatial types.
+ [#139450][#139450]
+- Updated edge cases in the `width_bucket()` function to return `count + 1` for a positive infinity operand, and `0` for a negative infinity operand, instead of an error.
+ [#142932][#142932]
+- Unary arithmetic operators are now supported in JSONPath queries. For example, `SELECT jsonb_path_query('[1, 2, 3]', '-$');`.
+ [#143613][#143613]
+- Implemented various `power()` and `^` edge cases to match PostgreSQL behaviour. Some expressions that previously returned `NaN` now return specific numbers; some expressions that previously returned `Infinity` or `NaN` now return errors; and some expressions with infinite exponents now return different results.
+ [#142932][#142932]
+- Null comparisons are now supported in JSONPath queries. For example, `SELECT jsonb_path_query('{}', 'null != 1');`.
+ [#143240][#143240]
+- Wildcard key accessors are now supported in JSONPath queries. For example, `SELECT jsonb_path_query('{"a": 1, "b": true}', '$.*');`.
+ [#143588][#143588]
+- `like_regex` predicate evaluation is now supported in JSONPath queries. For example, `SELECT jsonb_path_query('{}', '"hello" like_regex "^he.*$"');`.
+ [#143240][#143240]
+- Added the `EXPERIMENTAL COPY` option to `RESTORE`, which runs online `RESTORE`, but waits to publish the tables until all data is downloaded.
+ [#143674][#143674]
+
+<h3 id="v25-2-0-alpha-3-operational-changes">Operational changes</h3>
+
+- 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.
+ [#143384][#143384]
+- Previously, the user provided in the source URI in the logical data replication (LDR) stream required the `REPLICATIONSOURCE` privilege at the system level. With this change, the user only needs this privilege on the source tables (i.e., a table-level privilege).
+ [#143456][#143456]
+
+<h3 id="v25-2-0-alpha-3-db-console-changes">DB Console changes</h3>
+
+- The lock and latch wait time components of a query's cumulative contention time are now tracked separately and surfaced as annotations in `EXPLAIN ANALYZE` output.
+ [#113649][#113649]
+- The metric that measures cumulative contention time now includes time spent waiting to acquire latches, in addition to time spent acquiring locks. This metric is displayed in both the DB Console and the `EXPLAIN ANALYZE` output.
+ [#113649][#113649]
+
+<h3 id="v25-2-0-alpha-3-bug-fixes">Bug fixes</h3>
+
+- Fixed a bug where index backfills unnecessarily merged new data written to an index, which could lead to extra contention.
+ [#142768][#142768]
+- Column IDs are now validated when starting an `immediate` mode logical replication stream. [#143773][#143773]
+- Fixed a bug where a GC threshold error (which appears as "batch timestamp must be after replica GC threshold ...") could cause a schema change that backfills data to fail. Now, the error will cause the backfill to be retried at a higher timestamp to avoid the error.
+ [#143451][#143451]
+- Fixed a bug where index backfill progress before a `PAUSE`/`RESUME` would not get tracked.
+ [#142602][#142602]
+- Fixed a bug that could cause a function reference to be left behind if a procedure referred to another procedure that depended on a a table, and that table was dropped with `CASCADE`.
+ [#143538][#143538]
+- Fixed a potential deadlock that could occur during client certificate updates while metrics were being collected. This issue affected the reliability of certificate expiration reporting.
+ [#143663][#143663]
+- Previously, the fields `maximum memory usage` and `max sql temp disk usage` in the `EXPLAIN ANALYZE` output could be under-reported for distributed plans when memory-intensive operations were fully performed on the remote nodes. This is now fixed. The bug existed in v22.1 and later.
+ [#143777][#143777]
+- The `ALTER VIRTUAL CLUSTER SET REPLICATION READ VIRTUAL CLUSTER` syntax is now supported for adding a reader virtual cluster for an existing physical cluster replication (PCR) standby cluster.
+ [#143752][#143752]
+
+<h3 id="v25-2-0-alpha-3-performance-improvements">Performance improvements</h3>
+
+- Schema changes that require data to be backfilled no longer hold a protected timestamp for the entire duration of the backfill, which means there is less overhead caused by MVCC garbage collection after the backfill completes.
+ [#143451][#143451]
+- Fixed a bug that caused the optimizer to over-estimate the cost of inverted index scans in some cases. Now, plans with inverted index scans should be selected in more cases where they are optimal.
+ [#120079][#120079]
+
+[#143588]: https://github.com/cockroachdb/cockroach/pull/143588
+[#143384]: https://github.com/cockroachdb/cockroach/pull/143384
+[#143451]: https://github.com/cockroachdb/cockroach/pull/143451
+[#120079]: https://github.com/cockroachdb/cockroach/pull/120079
+[#143613]: https://github.com/cockroachdb/cockroach/pull/143613
+[#142768]: https://github.com/cockroachdb/cockroach/pull/142768
+[#143773]: https://github.com/cockroachdb/cockroach/pull/143773
+[#143538]: https://github.com/cockroachdb/cockroach/pull/143538
+[#143752]: https://github.com/cockroachdb/cockroach/pull/143752
+[#143674]: https://github.com/cockroachdb/cockroach/pull/143674
+[#143240]: https://github.com/cockroachdb/cockroach/pull/143240
+[#142602]: https://github.com/cockroachdb/cockroach/pull/142602
+[#143663]: https://github.com/cockroachdb/cockroach/pull/143663
+[#143777]: https://github.com/cockroachdb/cockroach/pull/143777
+[#143658]: https://github.com/cockroachdb/cockroach/pull/143658
+[#139450]: https://github.com/cockroachdb/cockroach/pull/139450
+[#142932]: https://github.com/cockroachdb/cockroach/pull/142932
+[#143456]: https://github.com/cockroachdb/cockroach/pull/143456
+[#113649]: https://github.com/cockroachdb/cockroach/pull/113649