You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a {{ site.data.products.cloud }} organization with billing configured lapses in payment, non-payment reminders are sent the **Billing contact info** designated in the {{ site.data.products.cloud }} Console under **Billing** > **Settings**. By default this billing contact is set to the original Organization Admin of the {{ site.data.products.cloud }} organization.
2
+
3
+
After sending multiple payment failure reminders with no acknowledgement or change in billing, all clusters in the organization are deleted including data. Deleted clusters cannot be restored.
{% include releases/new-release-downloads-docker-image.md release=include.release %}
6
+
7
+
<h3id="v24-1-24-sql-language-changes">SQL language changes</h3>
8
+
9
+
- When `sql_safe_updates` is enabled, the `ALTER TABLE ... LOCALITY` statement will be blocked when trying to convert an existing table to `REGIONAL BY ROW`, unless a region column has been added to the table. This protects against undesired behavior that caused `UPDATE` or `DELETE` statements to fail against the table while the locality change was in progress. [#152603][#152603]
- Updated TTL job replanning to be less sensitive by focusing specifically on detecting when nodes become unavailable rather than reacting to all plan differences. The cluster setting `sql.ttl.replan_flow_threshold` may have been set to `0` to work around the TTL replanner being too sensitive; this fix will alleviate that and any instance that had set `replan_flow_threshold` to `0` can be reset back to the default. [#151490][#151490]
14
+
15
+
<h3id="v24-1-24-bug-fixes">Bug fixes</h3>
16
+
17
+
- Fixed a bug where `debug.zip` files collected from clusters with `disallow_full_table_scans` enabled were missing system table data. [#151222][#151222]
18
+
- Fixed a bug where updating column default expressions would incorrectly remove sequence ownerships for the affected column. [#152312][#152312]
19
+
- Fixed a bug where views could not reference the `crdb_region` column from their underlying tables in expressions. [#152744][#152744]
- Lookup joins can now be used on tables with virtual columns even if the type of the search argument is not identical to the column type referenced in the virtual column. [#152893][#152893]
{% include releases/new-release-downloads-docker-image.md release=include.release %}
6
+
7
+
<h3id="v24-3-20-sql-language-changes">SQL language changes</h3>
8
+
9
+
- When `sql_safe_updates` is enabled, the `ALTER TABLE ... LOCALITY` statement will be blocked when trying to convert an existing table to `REGIONAL BY ROW`, unless a region column has been added to the table. This protects against undesired behavior that caused `UPDATE` or `DELETE` statements to fail against the table while the locality change was in progress. [#152602][#152602]
10
+
11
+
<h3id="v24-3-20-bug-fixes">Bug fixes</h3>
12
+
13
+
- Fixed a bug where invalid default expressions could cause backfilling schema changes to retry forever. [#147015][#147015]
14
+
- Fixed a bug that could cause excessive memory allocations when compacting timeseries keys. [#151813][#151813]
15
+
- Fixed a bug where updating column default expressions would incorrectly remove sequence ownerships for the affected column. [#152313][#152313]
16
+
- Fixed a bug that allowed foreign-key violations to result from some combinations of concurrent `READ COMMITTED` and `SERIALIZABLE` transactions. If both `SERIALIZABLE` and weaker-isolation transactions will concurrently modify rows involved in foreign-key relationships, the `SERIALIZABLE` transactions must have the following session variables set in order to prevent any possible foreign-key violations:
- Lookup joins can now be used on tables with virtual columns even if the type of the search argument is not identical to the column type referenced in the virtual column. [#152630][#152630]
26
+
27
+
<h3id="v24-3-20-miscellaneous">Miscellaneous</h3>
28
+
29
+
- Tunes S3 client retry behavior to be more reliable in the
{% include releases/new-release-downloads-docker-image.md release=include.release %}
6
+
7
+
<h3id="v25-2-6-sql-language-changes">SQL language changes</h3>
8
+
9
+
- Added a new session variable, `disable_optimizer_rules`, which allows users to provide a comma-separated list of optimizer rules to disable during query optimization. This allows users to avoid rules that are known to create a suboptimal query plan for specific queries. [#152349][#152349]
10
+
- When `sql_safe_updates` is enabled, the `ALTER TABLE ... LOCALITY` statement will be blocked when trying to convert an existing table to `REGIONAL BY ROW`, unless a region column has been added to the table. This protects against undesired behavior that caused `UPDATE` or `DELETE` statements to fail against the table while the locality change was in progress. [#152600][#152600]
- Updated TTL job replanning to be less sensitive by focusing specifically on detecting when nodes become unavailable rather than reacting to all plan differences. The cluster setting `sql.ttl.replan_flow_threshold` may have been set to `0` to work around the TTL replanner being too sensitive; this fix will alleviate that and any instance that had set `replan_flow_threshold` to `0` can be reset back to the default. [#151485][#151485]
15
+
16
+
<h3id="v25-2-6-bug-fixes">Bug fixes</h3>
17
+
18
+
- Fixed a bug where `debug.zip` files collected from clusters with `disallow_full_table_scans` enabled were missing system table data. [#151224][#151224]
19
+
- Addressed a bug on `schema_locked` tables when a column is dropped, and `schema_locked` is toggled for the user. [#151528][#151528]
20
+
- Fixed a bug that could cause excessive memory allocations when compacting timeseries keys. [#151814][#151814]
21
+
- Fixed a bug where `DROP USER` succeeded even though a role owned default privileges, which could leave invalid privilege entries in the system. [#151879][#151879]
22
+
- Previously, CockroachDB could hit an error `ERROR: span with results after resume span...` when evaluating some queries with `ORDER BY ... DESC` in an edge case. This bug was present since v22.1 and is now fixed. [#152184][#152184]
23
+
- Fixed a bug where `SHOW TABLES` would show inaccurate row counts if the most recent statistics collection was partial. [#152186][#152186]
24
+
- Fixed a bug where updating column default expressions would incorrectly remove sequence ownerships for the affected column. [#152314][#152314]
25
+
- Fixed a bug that allowed foreign-key violations to result from some combinations of concurrent `READ COMMITTED` and `SERIALIZABLE` transactions. If both `SERIALIZABLE` and weaker-isolation transactions will concurrently modify rows involved in foreign-key relationships, the `SERIALIZABLE` transactions must have the following session variables set in order to prevent any possible foreign-key violations:
- Added an automatic repair for dangling or invalid entries in the `system.comments` table. [#152471][#152471]
30
+
- Added the `use_soft_limit_for_distribute_scan` session variable (default: `false`), which controls whether CockroachDB uses the soft row count estimate when deciding whether an execution plan should be distributed. In v25.1, the physical planning heuristics were changed such that large constrained table scans, estimated to scan at least 10,000 rows (controlled via `distribute_scan_row_count_threshold`), would force plan distribution when `distsql=auto`. However, if the scan had a "soft limit" CockroachDB would still use the full estimate (for example, `10,000` in `estimated row count: 100–10,000`), sometimes unnecessarily distributing queries and increasing latency. The `use_soft_limit_for_distribute_scan` session variable addresses this by allowing the planner to use the soft limit when deciding whether a scan is "large". [#152559][#152559]
31
+
- Fixed a bug where views could not reference the `crdb_region` column from their underlying tables in expressions. [#152679][#152679]
- Lookup joins can now be used on tables with virtual columns even if the type of the search argument is not identical to the column type referenced in the virtual column. [#152631][#152631]
36
+
37
+
<h3id="v25-2-6-miscellaneous">Miscellaneous</h3>
38
+
39
+
- Tunes S3 client retry behavior to be more reliable in the
0 commit comments