Various edits

Author: rmloveland

src/current/_includes/releases/v25.4/v25.4.0-beta.2.md

@@ -13,67 +13,39 @@ Release Date: October 10, 2025
 
 - Added the `SHOW INSPECT ERRORS` command. This command can be used to view issues that are identified by running the `INSPECT` command to validate tables and indexes. [#154337][#154337]
 - Added the `sql.catalog.allow_leased_descriptors.enabled` cluster setting, which is false by default. When set to true, queries that access the `pg_catalog` or `information_schema` can use cached leased descriptors to populate the data in those tables, with the tradeoff that some of the data could be stale. [#154491][#154491]
-- We now support index acceleration for a subset of jsonb_path_exists filters.
-  
-  Given the `jsonb_path_exists(json_obj, json_path_expression)`, we only support
-  inverted index for json_path_expression that matches one of the following
-  patterns:
-  
+- We now support index acceleration for a subset of jsonb_path_exists filters. Given the `jsonb_path_exists(json_obj, json_path_expression)`, we only support inverted index for json_path_expression that matches one of the following patterns:
   - The json_path_expression must NOT be in STRICT mode.
   - keychain mode: $.[key|wildcard].[key|wildcard]...
   	- For this mode, we will generate a prefix span for the inverted expression.
   - filter with end value mode, with equality check: $.[key|wildcard]? (@.[key|wildcard].[key|wildcard]... == [string|number|null|boolean])
       - For this mode, since the end value is fixed, we will generate a single value span.
-  
-  Specifically, we don't support the following edge case:
-  
-  - $
-  - $[*]
-  - $.a.b.c == 12 or $.a.b.c > 12 or $.a.b.c < 12 (operation expression)
-  - $.a.b ? (@.a > 10) (filter, with inequality check)
-  
-  Note that the cases we support is to use `jsonb_path_exists` in filters,
-  as in, when they are used in the WHERE clause. [#154631][#154631]
-- The optimizer can now use table statistics
-  that merge the latest full statistic with all newer partial statistics,
-  including those over arbitrary constraints over a single span. [#154755][#154755]
+  - Specifically, we don't support the following edge case:
+      - $
+      - $[*]
+      - $.a.b.c == 12 or $.a.b.c > 12 or $.a.b.c < 12 (operation expression)
+      - $.a.b ? (@.a > 10) (filter, with inequality check)
+  - Note that the cases we support is to use `jsonb_path_exists` in filters, as in, when they are used in the WHERE clause. [#154631][#154631]
+- The optimizer can now use table statistics that merge the latest full statistic with all newer partial statistics, including those over arbitrary constraints over a single span. [#154755][#154755]
 
 <h3 id="v25-4-0-beta-2-operational-changes">Operational changes</h3>
 
-- Two new changefeed metrics for tracking
-  the max skew between a changefeed's slowest and fastest span/table
-  have been added. The metrics are gauge metrics with the names
-  `changefeed.progress_skew.{span,table}`. [#154166][#154166]
+- Two new changefeed metrics for tracking the max skew between a changefeed's slowest and fastest span/table have been added. The metrics are gauge metrics with the names `changefeed.progress_skew.{span,table}`. [#154166][#154166]
 - The metrics `sql.select.started.count`, `sql.insert.started.count`, `sql.update.started.count`, and `sql.delete.started.count` are now emitted with labels under the common metric name `sql.started.count`, using a `query_type` label to distinguish each operation. [#154388][#154388]
 - Added the cluster setting `storage.unhealthy_write_duration` (defaults to 20s), which is used to indicate to the allocator that a store's disk is unhealthy. The cluster setting `kv.allocator.disk_unhealthy_io_overload_score` controls the overload score assigned to a store with an unhealthy disk, where a higher score results in preventing lease or replica transfers to the store, or shedding of leases by the store. The default value of that setting is 0, so the allocator behavior is unaffected. [#154459][#154459]
 - Added cluster setting `sql.schema.approx_max_object_count` (default: 20,000) to prevent creation of new schema objects when the limit is exceeded. The check uses cached table statistics for performance and is approximate - it may not be immediately accurate until table statistics are updated by the background statistics refreshing job. Clusters that have been running stably with a larger object count should raise the limit or disable the limit by setting the value to 0. In future releases, the default value for this setting will be raised as more CockroachDB features support larger object counts. [#154576][#154576]
 
 <h3 id="v25-4-0-beta-2-bug-fixes">Bug fixes</h3>
 
-- Vector index backfill will now properly track job
-  progress in SHOW JOBS output. [#154261][#154261]
-- A bug has been fixed that caused panics when
-  executing `COPY` into a table with hidden columns and expression
-  indexes. The panic only occurred when the
-  `expect_and_ignore_not_visible_columns_in_copy` setting was enabled.
-  This bug has been present since
-  `expect_and_ignore_not_visible_columns_in_copy` was introduced in
-  v22.1.0. [#154289][#154289]
+- Vector index backfill will now properly track job progress in SHOW JOBS output. [#154261][#154261]
+- A bug has been fixed that caused panics when executing `COPY` into a table with hidden columns and expression indexes. The panic only occurred when the `expect_and_ignore_not_visible_columns_in_copy` setting was enabled. This bug has been present since `expect_and_ignore_not_visible_columns_in_copy` was introduced in v22.1.0. [#154289][#154289]
 - **Idle latency** on the **Transaction Details** page in the DB Console is now reported more accurately. Previously, transactions that used prepared statements (e.g., with placeholders) overcounted idle time, while those that included observer statements (common in the SQL CLI) undercounted it. [#154385][#154385]
 - Fixed a bug where `RESTORE` of a database with a `SECONDARY REGION` did not apply the lease preferences for that region. [#154659][#154659]
-- A bug where a changefeed could perform
-  many unnecessary job progress saves during an initial scan has
-  been fixed. [#154709][#154709]
-- A bug where a changefeed targeting only a subset
-  of a table's column families could become stuck has been fixed. [#154915][#154915]
+- A bug where a changefeed could perform many unnecessary job progress saves during an initial scan has been fixed. [#154709][#154709]
+- A bug where a changefeed targeting only a subset of a table's column families could become stuck has been fixed. [#154915][#154915]
 
 <h3 id="v25-4-0-beta-2-performance-improvements">Performance improvements</h3>
 
-- The cost of generic query plans
-  is now calculated based on worst-case selectivities for placeholder
-  equalities (e.g., x = $1). This reduces the chance of suboptimal generic
-  query plans being chosen when `plan_cache_mode=auto`. [#154899][#154899]
-
+- The cost of generic query plans is now calculated based on worst-case selectivities for placeholder equalities (e.g., x = $1). This reduces the chance of suboptimal generic query plans being chosen when `plan_cache_mode=auto`. [#154899][#154899]
 
 [#154337]: https://github.com/cockroachdb/cockroach/pull/154337
 [#154491]: https://github.com/cockroachdb/cockroach/pull/154491