What's New in v24.1 - CockroachDB

CockroachDB v24.1 is a required . This page contains a complete list of features and changes in v24.1.

For a summary of the most significant changes in v24.1, refer to Feature highlights.
Before , review the backward-incompatible changes, including key cluster setting changes and deprecations; as well as newly identified known limtiations.
For details about the support window for this release type, review the .
For details about all supported releases, the release schedule, and licenses, refer to .
After downloading a supported CockroachDB binary, learn how to or .

Get future release notes emailed to you:

v24.1.31

Release Date: June 26, 2026

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.31.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.31.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.31.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.31.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.31.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.31.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.31.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.31.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.31.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.31.windows-6.2-amd64.zip (SHA256)

Docker image

Multi-platform images include support for both Intel and ARM. Multi-platform images do not take up additional space on your Docker host. Within the multi-platform image, both Intel and ARM images are generally available for production use. To download the Docker image:

docker pull cockroachdb/cockroach:v24.1.31

Security updates

Security: Fixed an issue where a tenant-scoped client certificate could bypass tenant-scope checks and gain cluster-wide RPC access if its subject distinguished name (DN) matched the configured root or node DN.

v24.1.30

Release Date: June 11, 2026

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.30.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.30.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.30.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.30.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.30.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.30.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.30.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.30.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.30.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.30.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.30

Bug fixes

Fixed a bug where the view owner’s privileges on underlying tables were not checked when selecting from a view. A view would continue to work even after the owner lost access to the underlying tables. To enforce privilege checks on underlying tables, set the sql.auth.skip_underlying_view_privilege_checks.enabled cluster setting to false. This setting defaults to true to prevent backward-incompatible behavior.

Build changes

Replaces bors with Trunk merge queue for better performance and reliability. Configuration-only change with no runtime impact - maintains same safety checks while improving CI workflow.

v24.1.29

Release Date: May 12, 2026

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.29.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.29.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.29.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.29.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.29.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.29.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.29.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.29.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.29.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.29.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.29

Bug fixes

Fixed a bug that would allow a race condition in foreign key cascades under READ COMMITTED and REPEATABLE READ isolation levels.
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:
- SET enable_implicit_fk_locking_for_serializable = on;
- SET enable_shared_locking_for_serializable = on;
- SET enable_durable_locking_for_serializable = on;

v24.1.28

Release Date: April 22, 2026

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.28.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.28.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.28.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.28.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.28.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.28.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.28.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.28.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.28.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.28.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.28

Bug fixes

Fixed a bug where concurrent updates to a table using multiple column families during a partial index creation could result in data loss, incorrect NULL values, or validation failures in the resulting index.

v24.1.27

Release Date: April 8, 2026

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.27.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.27.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.27.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.27.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.27.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.27.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.27.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.27.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.27.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.27.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.27

Bug fixes

Fixed a bug where generating a debug zip could trigger an out-of-memory (OOM) condition on a node if malformed log entries were present in logs using json or json-compact formatting. This bug was introduced in v24.1.

v24.1.26

Release Date: February 19, 2026

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.26.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.26.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.26.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.26.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.26.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.26.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.26.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.26.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.26.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.26.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.26

Bug fixes

Fixed a rare race condition between range splits and MVCC garbage collection where a GCRequest could target keys outside its declared span. In rare cases, this could result in data on the post-split right-hand side (RHS) being incorrectly garbage collected, potentially leading to lost writes. The system now detects and rejects such malformed GC requests.
Fixed a bug where generating a debug zip could trigger an out-of-memory (OOM) condition on a node if malformed log entries were present in logs using json or json-compact formatting. Debug zip generation now safely handles malformed log lines and prevents excessive memory consumption.

v24.1.25

Release Date: October 17, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.25.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.25.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.25.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.25.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.25.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.25.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.25.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.25.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.25.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.25.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.25

Bug fixes

Fixed a bug where an INSERT statement could fail with a type checking error while adding a BIT(n) column.
Fixed a bug that caused panics when executing COPY into a table with hidden columns and expression indexes. The panic only occurred when the session setting expect_and_ignore_not_visible_columns_in_copy was enabled. This bug was introduced with expect_and_ignore_not_visible_columns_in_copy in v22.1.0.
Fixed a bug where the presence of duplicate temporary tables in a backup caused the restore to fail with an error containing the text restoring table desc and namespace entries: table already exists.

v24.1.24

Release Date: September 22, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.24.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.24.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.24.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.24.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.24.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.24.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.24.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.24.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.24.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.24.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.24

SQL language changes

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.

Operational changes

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.

Bug fixes

Fixed a bug where debug.zip files collected from clusters with disallow_full_table_scans enabled were missing system table data.
Fixed a bug where updating column default expressions would incorrectly remove sequence ownerships for the affected column.
Fixed a bug where views could not reference the crdb_region column from their underlying tables in expressions.

Performance improvements

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.

v24.1.23

Release Date: August 22, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.23.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.23.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.23.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.23.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.23.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.23.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.23.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.23.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.23.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.23.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.23

General changes

Backporting detailed error logging logic gated behind a cluster setting. The cluster setting enables detailed error logging for messages exceeding Kafka v2 size limit.
Changefeeds emitting to Kafka sinks that were created in CockroachDB v24.2.1+, or v23.2.10+ and v24.1.4+ with the changefeed.new_kafka_sink.enabled cluster setting enabled now include the message key, size, and MVCC timestamp in “message too large” error logs.

Bug fixes

Fixed an issue where the mvcc_timestamp field was incorrectly returning zero values when used with CDC queries. The timestamp is now emitted correctly.
Fixed a bug that could cause some errors returned by attempts to upload backup data to external storage providers to be undetected, potentially causing incomplete backups.

Build changes

Upgrade Go to consume security fixes

Miscellaneous

Restore will now re-attempt AdminSplit KV requests instead of immediately failing and pausing the job.

v24.1.22

Release Date: August 1, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.22.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.22.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.22.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.22.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.22.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.22.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.22.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.22.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.22.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.22.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.22

Bug fixes

Fixed a bug that could cause some errors returned by attempts to upload backup data to external storage providers to be undetected, potentially causing incomplete backups.

v24.1.21

Release Date: July 28, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.21.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.21.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.21.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.21.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.21.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.21.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.21.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.21.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.21.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.21.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.21

Bug fixes

Fixed a data race in the cloudstorage sink.
Fixed a bug where libpq clients using the async API could hang with large result sets (Python: psycopg; Ruby: ActiveRecord, ruby-pg).

v24.1.20

Release Date: June 25, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.20.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.20.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.20.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.20.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.20.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.20.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.20.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.20.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.20.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.20.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.20

Bug fixes

Fixed a bug that could potentially cause a changefeed to complete erroneously when one of its watched tables encounters a schema change.
Fixed a bug that caused the SQL Activity > Statement Fingerprint page to fail to load details for statements run with application names containing a # character.
Fixed a bug that could cause the cockroach process to segfault when collecting runtime execution traces (typically collected via the Advanced Debug page in the Console).
Fixed a bug that could cause stable expressions to be folded in cached query plans. The bug could cause stable expressions like current_setting to return the wrong result if used in a prepared statement. The bug was introduced in v23.2.22, v24.1.14, v24.3.9, v25.1.2, and the v25.2 alpha.
Fixed a bug where prepared statements on schema changes could fail with runtime errors.
Fixed a bug where ALTER TABLE was modifying identity attributes on columns not backed by a sequence.

Performance improvements

TTL jobs now respond to cluster topology changes by restarting and rebalancing across available nodes.

v24.1.19

Release Date: May 28, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.19.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.19.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.19.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.19.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.19.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.19.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.19.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.19.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.19.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.19.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.19

Operational changes

Changed the default value of the cluster setting admission.l0_file_count_overload_threshold to 4000.

DB Console changes

Schema insights that recommend replacing an index were previously a two-statement command consisting of a CREATE INDEX and a DROP INDEX statement. When these two DDL statements were run as a single batched command, it was possible for one statement to succeed and one to fail. This is because DDL statements do not have the same atomicity guarantees as other SQL statements in CockroachDB. Index-replacement insights are now a single CREATE INDEX statement followed by a comment with additional DDL statements to be run manually: an ALTER INDEX... NOT VISIBLE statement, which makes the old index invisible to the optimizer, followed by a DROP INDEX statement that should only be run after making the old index invisible and verifying that workload performance is satisfactory.

Bug fixes

Fixed a bug where CockroachDB could encounter a cannot specify timestamp older than... error during table statistics collection in some cases (e.g., when the cluster is overloaded). The bug was present since v19.1.
Fixed a bug in the DB Console where tables with page size dropdowns failed to update when a new page size option was selected. Tables now update correctly.
Fixed the following bugs in the Schedules page of the DB Console:
- Fixed a bug where the Schedules page displayed only a subset of a cluster’s schedules. The Schedules page now correctly displays all schedules.
- Fixed a bug where manually updating the show or status parameters in the URL (e.g., http://127.0.0.1:8080/#/schedules?status=ACTIVE&show=50 ) caused the Schedules page to fail to load.
Fixed a bug in the SQL Activity Statements page where filtering by Statement Type returned no results. The filter now works as expected.
Improved the performance of SHOW CREATE TABLE on multi-region databases with large numbers of objects.
Fixed a bug that could lead to schema changes hanging after a cluster recovered from availability issues.
Previously, on a table with multiple column families, CockroachDB could encounter a Non-nullable column "‹×›:‹×›" with no value error in rare cases during table statistics collection. The bug was present since v19.2 and is now fixed.
Fixed a bug where orphaned leases were not properly cleaned up.
Fixed an internal assertion failure that could occur during operations like ALTER TYPE or ALTER DATABASE... ADD REGION when temporary tables were present.
Fixed a bug that could cause queries that perform work in parallel to ignore the requested quality-of-service level. Affected operations include lookup joins, DistSQL execution, and foreign-key checks.
Fixed a bug that prevented TRUNCATE from succeeding if any indexes on the table had back-reference dependencies, such as from a view or function referencing the index. \
Fixed a rare corruption bug that impacts import and materialized views.

v24.1.18

Release Date: April 30, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.18.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.18.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.18.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.18.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.18.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.18.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.18.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.18.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.18.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.18.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.18

SQL language changes

EXPLAIN ANALYZE statements now display the number of transaction retries and time spent retrying, if non-zero, in the plan output.
Added the WITH IGNORE_FOREIGN_KEYS option to SHOW CREATE TABLE which omits foreign key constraints from the output schema. This option is also allowed in SHOW CREATE VIEW, but has no effect. It cannot be combined with the WITH REDACT option.

Bug fixes

Fixed a rare corruption bug that impacts import and materialized views.
Fixed a bug that caused changefeeds to fail on startup when scanning a single key.
Fixed a bug in the client certificate expiration metrics security.certificate.expiration.client and security.certificate.ttl.client.
Fixed a bug in v24.1.14, v24.3.7, v24.3.8, and v25.1 that could cause a nil-pointer error when a column’s default expression contained a volatile expression (like nextval ) as a UDF argument.
MVCC garbage collection is now fully subject to IO admission control. Previously, it was possible for MVCC GC to cause store overload (such as LSM inversion) when a large amount of data would become eligible for garbage collection. Should any issues arise from subjecting MVCC GC to admission control, the kv.mvcc_gc.queue_kv_admission_control.enabled cluster setting can be set to false to restore the previous behavior.
Fixed a bug that could cause a stack overflow during execution of a prepared statement that invoked a PL/pgSQL routine with a loop. The bug existed in versions v23.2.22, v24.1.15, v24.3.9, v25.1.2, v25.1.3, and pre-release versions of v25.2 prior to v25.2.0-alpha.3.
Fixed a bug where CockroachDB would encounter an internal error when decoding the gists of plans with CALL statements. The bug had been present since v23.2.
Fixed a bug where calling a stored procedure could drop the procedure if it had OUT parameters that were not used by the calling routine. This bug had existed since PL/pgSQL CALL statements were introduced in v24.1.
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.

v24.1.17

Release Date: April 28, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.17.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.17.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.17.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.17.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.17.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.17.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.17.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.17.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.17.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.17.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.17

Bug fixes

Fixed a rare corruption bug that impacts import and materialized views.

v24.1.16

Release Date: April 9, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.16.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.16.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.16.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.16.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.16.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.16.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.16.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.16.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.16.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.16.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.16

Bug fixes

Fixed a bug that could cause a stack overflow during execution of a prepared statement that invoked a PL/pgSQL routine with a loop. The bug existed in versions v23.2.22, v24.1.15, v24.3.9, v25.1.2, v25.1.3, and pre-release versions of v25.2 prior to v25.2.0-alpha.3.

v24.1.15

Release Date: April 3, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.15.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.15.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.15.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.15.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.15.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.15.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.15.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.15.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.15.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.15.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.15

Operational changes

Added the sql.statement_timeout.count metric to track the number of SQL statements that fail due to exceeding the statement timeout.
Added the sql.transaction_timeout.count metric to track the number of SQL statements that fail due to exceeding the transaction timeout.
The node decommission CLI command now waits until the target node is fully drained before marking it as decommissioned. Previously, the command would start draining but not wait, leaving the node in an unstable state where it could still accept client requests while being unable to communicate with the cluster, causing those requests to hang or fail with unexpected errors.

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.
Fixed a bug that could cause gateway nodes to panic when performing an UPSERT on a table with a BOOL primary key column and a partial index using the primary key column as the predicate expression.
Fixed a bug where CREATE SEQUENCE without concurrent DDL operations could hit a retry error due to incorrect schema modification.
Fixed a bug where CockroachDB could incorrectly evaluate casts to some OID types (e.g., REGCLASS ). This issue had been present since at least v22.1.
Fixed a bug that could cause nil pointer dereference errors when executing statements with user-defined functions (UDFs) or certain built-in functions like obj_description.
Fixed a bug where nodes drained during decommissioning could interrupt active SQL connections unexpectedly, even when drain was expected to wait for them to complete.
Fixed a bug where the fraction completed and internal checkpoints during an index backfill operation would stop being written if any periodic fraction/checkpoint write failed. Progress is now additionally logged to aid debugging. This bug affected schema changes such as creating an index or adding a non-nullable column.
Fixed a bug that could prevent SHOW CREATE TABLE from working if a database was offline (e.g., due to a RESTORE ).
Fixed a bug where tuple labels were sometimes disregarded, causing unexpected behavior, such as when converting a tuple to JSON with to_jsonb. This bug existed since v22.1.0 and became more likely to cause issues after changes in v24.1.7.
Fixed a bug where the declarative schema changer allowed CREATE SEQUENCE operations to proceed even while a DROP SCHEMA or DROP DATABASE was in progress. Such operations now retry if the parent object has a schema change in progress.
Fixed a bug in v24.1.14, v24.3.7, v24.3.8, and v25.1 that could cause a nil-pointer error when a column’s default expression contained a volatile expression (like nextval ) as a UDF argument.

Miscellaneous

Configuring the sql.ttl.default_delete_rate_limit cluster setting now displays a notice clarifying that the TTL rate limit is per leaseholder per table, with a link to the documentation.

v24.1.14

Release Date: March 6, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.14.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.14.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.14.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.14.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.14.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.14.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.14.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.14.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.14.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.14.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.14

SQL language changes

Since v23.2, table statistics histograms have been collected for non-indexed JSONB columns. Histograms are no longer collected for these columns if the sql.stats.non_indexed_json_histograms.enabled cluster setting is set to false. This reduces memory usage during table statistics collection for both automatic and manual collection via ANALYZE and CREATE STATISTICS.
Added support for a new index hint, AVOID_FULL_SCAN, which will prevent the optimizer from planning a full scan for the specified table if any other plan is possible. The hint can be used in the same way as other existing index hints. For example, SELECT * FROM table_name@{AVOID_FULL_SCAN};. This hint is similar to NO_FULL_SCAN, but will not error if a full scan cannot be avoided. Note that normally a full scan of a partial index would not be considered a “full scan” for the purposes of the NO_FULL_SCAN and AVOID_FULL_SCAN hints, but if the user has explicitly forced the partial index via FORCE_INDEX=index_name, we do consider it a full scan.
Added the optimizer_prefer_bounded_cardinality session setting, 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.
Added the optimizer_min_row_count session setting, which sets a lower bound on row count estimates for relational expressions during query planning. A value of 0, which is the default, indicates no lower bound. Note that if this is set to a value greater than 0, 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.
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.
Added the optimizer_check_input_min_row_count session setting to control the minimum row count estimate for buffer scans of foreign key and uniqueness checks. It defaults to 0.

Operational changes

The changefeed.max_behind_nanos metric now supports scoping with metric labels.

Command-line changes

Improved the performance of the debug zip query that collects transaction_contention_events data, reducing the chances of “memory budget exceeded” or “query execution canceled due to statement timeout” errors.

Bug fixes

Fixed a bug that, under rare circumstances, could cause draining a node to fail with the error message “some sessions did not respond to cancellation within 1s”.
Fixed a bug that prevented the CREATE statement for a routine from being shown in a statement bundle. This happened when the routine was created on a schema other than public. The bug had existed since v23.1.
Fixed a memory leak that could previously occur when evaluating some memory-intensive queries via the vectorized engine in CockroachDB. The leak had been present since v20.2.
Fixed a bug that could cause SHOW TABLES and other introspection operations to encounter a “batch timestamp must be after replica GC threshold” error.
Removed duplicate columns in the Parquet output from changefeeds using CDC queries.
Fixed a rare bug in which a query might fail with the 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.
Fixed a bug that would cause an internal error when the result of a RECORD -returning user-defined function (UDF) was wrapped by another expression (such as COALESCE ) within a VALUES clause.
The Data Distribution report on the Advanced Debug page will no longer crash if there are null values for raw_sql_config in crdb_internal.zones.
Upgraded the Sarama Kafka client library to pick up a fix for a race condition bug that could occur when Kafka throttling was enabled.

v24.1.13

Release Date: February 19, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.13.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.13.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.13.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.13.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.13.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.13.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.13.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.13.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.13.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.13.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.13

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.

This fix is present in v24.1.11 and v24.1.13, but was not released in v24.1.12.

v24.1.12

Release Date: February 6, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.12.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.12.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.12.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.12.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.12.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.12.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.12.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.12.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.12.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.12.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.12

General changes

The protected timestamp records of running changefeeds are now updated when the set of targets changes, such as when system tables are added to the protected tables list.

Backward-incompatible changes

In v24.1.11, a bug was fixed that could cause SHOW TABLES and other introspection operations to encounter a "batch timestamp... must be after replica GC threshold" error. This fix is not present in v24.1.12, but has been released in v24.1.13.

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 if the sql.stats.non_indexed_json_histograms.enabled cluster setting is set to false. This reduces memory usage during table statistics collection, for both automatic and manual collection via ANALYZE and CREATE STATISTICS.
Added support for a new index hint, AVOID_FULL_SCAN, which will prevent the optimizer from planning a full scan for the specified table if any other plan is possible. The hint can be used in the same way as other existing index hints. For example, SELECT * FROM table_name@{AVOID_FULL_SCAN};. This hint is similar to NO_FULL_SCAN, but will not error if a full scan cannot be avoided. Note that normally a full scan of a partial index would not be considered a “full scan” for the purposes of the NO_FULL_SCAN and AVOID_FULL_SCAN hints, but if the user has explicitly forced the partial index via FORCE_INDEX=index_name, CockroachDB does consider it a full scan.
Added the optimizer_prefer_bounded_cardinality session setting, 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.
Added the optimizer_min_row_count session setting, 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.

Operational changes

Added new metrics that expose the TTL for various certificates.
Introduced the metric sql.schema_changer.object_count that keeps track of the count of objects in the cluster.

Bug fixes

ALTER BACKUP SCHEDULE no longer fails on schedules with a collection URI that contains a space.
Previously, SHOW CREATE TABLE was showing incorrect data with regards to inverted indexes. It now shows the correct data that can be repeatedly entered back into CockroachDB to recreate the same table.
Fixed a bug where querying the pg_catalog.pg_constraint table while the schema changer was dropping a constraint could result in a query error.
Fixed a timing issue between ALTER VIEW.. RENAME and DROP VIEW that caused repeated failures in the DROP VIEW job.
Queries that perform a cast from the string representation of an array containing GEOMETRY or GEOGRAPHY types to a SQL array type will now succeed.
security.certificate.* metrics will now be updated if a node loads new certificates while running.
When the session variable allow_role_memberships_to_change_during_transaction is set, it is now possible to create and drop users quickly even when there are contending transactions on the system.users and system.role_options system tables.
Fixed a bug where the error batch timestamp... must be after replica GC threshold could occur during a schema change backfill operation, and cause the schema change job to retry infinitely. Now this error is treated as permanent, and will cause the job to enter the failed state.
CockroachDB could previously hit a bounded memory leak when collecting table statistics on a table that had both very wide (10KiB or more) and relatively small (under 400B) BYTES -like values within the same row. This has been present since before v19.2. Additionally, in v24.1.0, a bug was introduced that made this leak also apply to STRING -like values.

v24.1.11

Release Date: January 31, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.11.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.11.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.11.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.11.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.11.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.11.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.11.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.11.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.11.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.11.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.11

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.

This fix is present in v24.1.11 and v24.1.13, but was not released in v24.1.12.

v24.1.10

Release Date: January 9, 2025

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.10.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.10.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.10.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.10.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.10.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.10.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.10.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.10.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.10.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.10.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.10

Security updates

The cluster setting server.jwt_authentication.issuers now takes the issuer’s configuration value apart from the URI.
- This can be set to one of the following values:
  1. A string that Go can parse as a valid issuer URL, e.g., 'https://accounts.google.com'.
  2. A string that can be parsed as valid JSON array of issuer URLs, e.g., ['example.com/adfs','https://accounts.google.com'].
  3. A string that can be parsed as valid JSON and deserialized into a map of issuer URLs to corresponding JWKS URIs. In the third case, CockroachDB will override the JWKS URI present in the issuer’s well-known endpoint, e.g., '{ "issuer_jwks_map": { "https://accounts.google.com": "https://www.googleapis.com/oauth2/v3/certs", "example.com/adfs": "https://example.com/adfs/discovery/keys" }}'. When issuer_jwks_map is set, CockroachDB directly uses the JWKS URI to get the key set. In all other cases where JWKSAutoFetchEnabled is set, it obtains the JWKS URI first from the issuer’s well-known endpoint and then uses this endpoint.

General changes

To improve the granularity of changefeed pipeline metrics, the changefeed metrics changefeed.admit_latency and changefeed.commit_latency have histogram buckets from 5ms to 60m (previously 500ms to 5m ). The following changefeed metrics have histogram buckets from 5ms to 10m (previously 500ms to 5m ):
- changefeed.parallel_io_queue_nanos
- changefeed.parallel_io_result_queue_nanos
- changefeed.sink_batch_hist_nanos
- changefeed.flush_hist_nanos
- changefeed.kafka_throttling_hist_nanos
Added support for multiple seed brokers in the new Kafka sink.
Added a new metric ( distsender.rangefeed.catchup_ranges_waiting_client_side ) that counts how many rangefeeds are waiting on the client-side limiter to start performing catchup scans.
Added changefeed support for the mvcc_timestamp option with the avro format. If both options are specified, the Avro schema includes an mvcc_timestamp metadata field and emits the row’s MVCC timestamp with the row data.
Added a no-op AWS_USE_PATH_STYLE parameter for forward compatibility with v24.3.

SQL language changes

Added the legacy_varchar_typing session setting, which reverts the changes of that caused the change in typing behavior described in. Specifically, it makes type-checking and overload resolution ignore the newly added “unpreferred” overloads. This setting defaults to on.

Operational changes

Removed the sql.auth.resolve_membership_single_scan.enabled cluster setting. This was added out of precaution in case it was necessary to revert back to the old behavior for looking up role memberships, but this escape hatch has never been needed in practice since this was added in v23.1.
Telemetry delivery is now considered successful even in cases where CockroachDB experiences a network timeout. This will prevent throttling in cases outside an operator’s control.
When a schema change job is completed, rolls back, or encounters a failure, the time taken since the job began is now logged in a structured log in the SQL_SCHEMA log channel.

Bug fixes

Fixed a bug where ALTER COLUMN SET NOT NULL was not enforced consistently when the table was created in the same transaction.
Fixed a bug where CREATE RELATION / TYPE could leave dangling namespace entries if the schema was concurrently being dropped.
The idle_in_session_timeout setting now excludes the time spent waiting for schema changer jobs to complete, preventing unintended session termination during schema change operations.
Fixed a bug that caused the optimizer to use stale table statistics after altering an ENUM type used in the table.
Table statistics collection in CockroachDB could previously run into no bytes in account to release errors in some edge cases (when the SQL memory budget, configured via --max-sql-memory flag, was close to being exhausted). The bug had been present since v21.2 and is now fixed.
CockroachDB now better respects the statement_timeout limit on queries involving the top K sort and merge join operations.
Fixed an issue where license enforcement was not consistently disabled for single-node clusters started with cockroach start-single-node. The fix ensures proper behavior on cluster restarts.
Fixed a bug that caused queries against tables with user-defined types to sometimes fail with errors after restoring those tables.
Fixed a bug that caused an incorrect filesystem to be logged as part of the store information.
Fixed a bug that had existed since v24.1 that would cause a set-returning UDF with OUT parameters to return a single row.
Fixed a bug that could cause an internal error if a table with an implicit ( rowid ) primary key was locked from within a subquery, e.g.: SELECT * FROM (SELECT * FROM foo WHERE x = 2) FOR UPDATE;. The error could occur either under READ COMMITTED isolation, or with optimizer_use_lock_op_for_serializable enabled.
Fixed an issue where adding an existing column with the IF NOT EXISTS option could exit too early, skipping necessary handling of the abstract syntax tree (AST). This could lead to failure of the ALTER statement.
Fixed an issue where a schema change could incorrectly cause a changefeed to fail with an assertion error like received boundary timestamp... of type... before reaching existing boundary of type....
Internal scans are now exempt from the sql.defaults.disallow_full_table_scans.enabled setting, allowing index creation even when the cluster setting is active.
Using more than one DECLARE statement in the definition of a user-defined function (UDF) now correctly declares additional variables.
Fixed an issue where corrupted table statistics could cause the cockroach process to crash.
Fixed a bug that could cause the password for the root user to be deleted while upgrading to v24.1. This bug only affected clusters that were initially created with v22.2 or earlier. The same bug could also cause the defaultdb and postgres databases to be recreated during the upgrade to v24.1 if they had been previously deleted.
CLOSE CURSOR statements are now allowed in read-only transactions, similar to PostgreSQL. The bug had been present since at least v23.1.

Performance improvements

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.

v24.1.9

Release Date: December 26, 2024

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.9.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.9.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.9.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.9.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.9.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.9.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.9.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.9.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.9.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.9.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.9

SQL language changes

Added the legacy_varchar_typing session setting. When set to on, type-checking comparisons involving VARCHAR columns behave as they did in all previous versions. When set to off, type-checking of these comparisons is more strict and queries that previously succeeded may now error with the message unsupported comparison operator. These errors can be fixed by adding explicit type casts. The legacy_varchar_typing session setting is on by default.

v24.1.8

Release Date: December 12, 2024

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.8.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.8.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.8.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.8.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.8.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.8.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.8.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.8.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.8.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.8.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.8

Security updates

All cluster settings that accept strings are now fully redacted when transmitted as part of our diagnostics telemetry. The transmitted payload includes a record of modified cluster settings and their values when they are not strings. If you previously applied the mitigations in , you can safely set the value of cluster setting server.redact_sensitive_settings.enabled to false and turn on diagnostic reporting via the diagnostics.reporting.enabled cluster setting without leaking sensitive cluster settings values.

General changes

COCKROACH_SKIP_ENABLING_DIAGNOSTIC_REPORTING is no longer mentioned in the cockroach demo command.
Added system.users to the list of system tables that changefeeds protect with protected timestamps (PTS). This table is required for change data capture queries.
Added changefeed support for the mvcc_timestamp option with the avro format. If both options are specified, the avro schema includes an mvcc_timestamp metadata field and emits the row’s MVCC timestamp with the row data.

Operational changes

To prevent unnecessary queuing in admission control CPU queues, the goschedstats.always_use_short_sample_period.enabled setting should be set to true for any production cluster.
A new cluster setting ui.database_locality_metadata.enabled, when set to true, disables loading database and table region information in the DB Console Database and Table pages. This information can cause significant CPU load on large clusters with many ranges. The Database and Table pages in v24.3 onwards do not have this problem. If you require this data, use the SHOW RANGES FROM {DATABASE|TABLE} SQL statement to compute this information on-demand.
The row-level TTL job now will periodically log progress by showing the number of table spans that have been processed so far.

Bug fixes

Fixed a bug where CockroachDB could encounter an internal error interface conversion: coldata.Column is in an edge case. The bug was present in v22.2.13+, v23.1.9+, and v23.2+.
Fixed an unhandled error that could occur when using REVOKE... ON SEQUENCE... FROM user on an object that is not a sequence.
Fixed a bug that caused incorrect NOT NULL constraint violation errors on UPSERT and INSERT... ON CONFLICT... DO UPDATE statements when those statements updated an existing row and a subset of columns that did not include a NOT NULL column of the table. This bug had been present since at least v20.1.0.
Addressed a panic that could occur inside CREATE TABLE AS if sequence builtin expressions had invalid function overloads.
String constants can now be compared against collated strings.
Previously, when executing queries with index / lookup joins where ordering needed to be maintained, CockroachDB’s behavior could lead to increased query latency, potentially by several orders of magnitude. This bug was introduced in v22.2, and is now fixed.
Fixed a bug where DISCARD ALL statements were counted under the sql.ddl.count metric. Now these statements will be counted under the sql.misc.count metric.
Fixed a bug where DROP CASCADE would occasionally panic with an un-dropped backref message on partitioned tables.
Reduced the duration of partitions in the gossip network when a node crashes. This eliminates false positives in the ranges.unavailable metric.
As a non-admin user who runs DROP ROLE IF EXISTS on a user that does not exist, you no longer get an error message.
Fixed a bug that caused quotes around the name of a routine to be dropped when the routine was called within another routine. This could prevent the correct routine name from being resolved if the nested routine name was case-sensitive. The bug has existed since v24.1, when nested routines were introduced.
Fixed a bug that could cause incorrect query results when the optimizer planned a lookup join on an index containing a column of type CHAR(N), VARCHAR(N), BIT(N), VARBIT(N), or DECIMAL(M, N), and the query held that column constant to a single value (for example, with an equality filter).
Fixed an unhandled error that would occur if DROP SCHEMA was executed on the public schema of the system database, or on an internal schema, such as pg_catalog or information_schema.
Fixed a bug that caused incorrect evaluation of some binary expressions involving CHAR(N) values and untyped string literals with trailing whitespace characters. For example, the expression 'f'::CHAR = 'f ' now correctly evaluates to true.
CREATE SCHEMA now returns the correct error if a the schema name is missing.

Performance improvements

Unnecessary block loads of SSTable files are now avoided in some rare cases after a replica rebalance.

v24.1.7

Release Date: November 18, 2024

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.7.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.7.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.7.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.7.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.7.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.7.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.7.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.7.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.7.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.7.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.7

Security updates

You can now authenticate to the DB Console by passing a JWT as the bearer token.

General changes

Changed the license cockroach is distributed under to the new CockroachDB Software License.
Attempting to install a second Enterprise Trial license on the same cluster will now fail.
The cluster setting diagnostics.reporting.enabled is now ignored if the cluster has an Enterprise Trial or Enterprise Free license or if the license cannot be loaded.
The new metrics changefeed.sink_errors and changefeed.internal_retry_message_count allow you to observe the rate of errors and internal retries for a sink, respectively.
Added a timer for inner sink client flushes.

DB Console changes

Some charts on the Overview and Replication metrics dashboard pages have more terse legends to facilitate easier browsing.
The DB Console now shows a warning if the cluster is throttled or will be throttled soon due to an expired Enterprise Free or Enterprise Trial license or missing telemetry data. Clusters with an Enterprise license are not throttled.
The Range Count column on the Databases page is no longer shown due to performance issues. This data is still available via the SHOW RANGES command.

Bug fixes

Fixed a bug where timers were not correctly registered with the metric system.
Fixed a bug where the command-line interface would not correctly escape JSON values that had double quotes inside a string when using the --format=sql flag.
Fixed an error that could occur if a SET command used an aggregate function as the value.
Added automated clean-up and validation for dropped roles inside of default privileges.
Fixed a bug that could cause RESTORE to hang after encountering transient errors from the storage layer.
Fixed a rare bug that could prevent a backup from being restored and could cause the error rewriting descriptor ids: missing rewrite for <id> in SequenceOwner.... This bug could occur only if a DROP COLUMN operation dropped a sequence while the backup was running.
Fixed a bug that caused incorrect evaluation of a CASE, COALESCE, or IF expression with a branch that produced fixed-width string-like types, such as CHAR.
Fixed a bug that could cause the BPCHAR type to incorrectly impose a length limit of 1.
Fixed a bug introduced before v23.1 that could cause incorrect results when a join evaluates columns with equivalent but non-identical types, such as OID and REGCLASS, for equality. The issue arises when the join performs an index lookup on an index that includes a computed column referencing one of the equivalent columns.
Fixed a bug introduced before v23.1 that could cause a composite sensitive expression to compare differently if comparing equivalent but non-identical input values, such as 2.0::DECIMAL and 2.00::DECIMAL. The issue arises when the join performs an index lookup on a table with a computed index column where the computed column expression is composite sensitive.
Fixed a bug where a span statistics request on a mixed-version cluster could result in a null pointer exception.
Updated the franz-go library to fix a potential deadlock when a changefeed restarts.
Fixed a bug where a changefeed could fail to update protected timestamp records after a retryable error.
Fixed a bug where a changefeed that used change data capture queries could fail after a system table was garbage collected.
Fixed a rare bug introduced in v22.2 where an update of a primary key column could fail to update the primary index if it is also the only column in a separate column family.
Fixed a bug where the proretset column of the pg_catalog.pg_proc table was incorrectly set to false for builtin functions that return a set.
Fixed a bug that could cause incorrect evaluation of scalar expressions with NULL values.
Fixed a rare bug in the query optimizer that could cause a node to crash if a query contained a filter in the form col IN (elem0, elem1,..., elemN) when N is very large, in the order of millions, and when col exists in a hash-sharded index or when a table with an indexed computed column depends on col.
Fixed a bug where an ALTER DEFAULT PRIVILEGES FOR target_role... command could result in an erroneous privilege error when run by a user with the admin role.
Fixed a bug where a REASSIGN OWNED BY command would fail to transfer ownership of the public schema, even when the schema was owned by the target role.
Fixed a panic when resolving the types of an AS OF SYSTEM TIME expression.

Performance improvements

Reduced the write-amplification impact of rebalances by splitting snapshot sorted string table (SST) files into smaller ones before ingesting them into Pebble.
Performance has been improved during periodic polling of table history when schema_locked is not used.

v24.1.6

Release Date: October 17, 2024

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.6.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.6.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.6.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.6.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.6.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.6.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.6.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.6.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.6.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.6.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.6

Enterprise edition changes

Updated the cluster setting with all the that support the setting.
Added two network metrics, changefeed.network.bytes_in and changefeed.network.bytes_out. These metrics track the number of bytes sent by individual to the following sinks:
- . If , the metric will have a kafka label.
- . If child metrics are enabled, the metric will have a webhook label.
- . If child metrics are enabled, the metric will have a pubsub label.
- . If child metrics are enabled, the metric will have a sql label.
Added a changefeed.total_ranges metric that can be used to monitor the number of ranges that are watched by aggregators. It shares the same polling interval as changefeed.lagging_ranges, which is controlled by the existing lagging_ranges_polling_interval option.
Disambiguated and logs for the two buffers used by the KV feed. The following metrics now have a suffix indicating which buffer they correspond to: changefeed.buffer_entries.*, changefeed.buffer_entries_mem.*, changefeed.buffer_pushback_nanos.*. The old versions are kept for backward compatibility, though using the new format is recommended.
Added timers around key parts of the pipeline to help debug feeds experiencing issues. The changefeed.stage.{stage}.latency metrics now emit latency histograms for each stage. The metric respects the changefeed scope label for debugging specific feeds.

General changes

Beginning with v24.1.6, CockroachDB v24.1 is in .

Operational changes

Added a ranges.decommissioning representing the number of ranges that have a replica on a .
You can now configure the log format for the by setting the stderr.format field in the .

DB Console changes

The will now show a notification alerting customers without an Enterprise license to upcoming license changes with a link to more information.

Bug fixes

Fixed a bug in which SHOW CLUSTER SETTING FOR VIRTUAL CLUSTER would erroneously return NULL for some settings.
Addressed a bug in the pre-condition for repairing descriptor corruption, which could lead to upgrade finalization being stuck.
Fixed a potential memory leak in using a . The memory leak could occur if both and changefeed.cloudstorage.async_flush.enabled were true, and the changefeed received an error while attempting to write to the cloud storage sink.
Fixed a bug in which some or queries using NOWAIT could still block on locked rows when using the optimizer_use_lock_op_for_serializable under isolation. This bug was introduced with in v23.2.0.
Fixed a bug that caused the to plan unnecessary post-query uniqueness checks during , , and statements on tables with , , . These unnecessary checks added overhead to execution of these statements, and caused the statements to error when executed under isolation.
Previously, if a connection was attempting a while the same schema objects were being dropped, it was possible for the connection to be incorrectly dropped. This is now fixed.
Fixed a bug that could result in the inability to garbage collect an range tombstone within a .
Fixed a bug that could cause errors with the message internal error: Non-nullable column... when executing statements under isolation that involved tables with virtual columns.
Fixed a bug that could cause incorrect results for queries containing a correlated subquery with a or operator referencing an outer column. This issue would occur if the correlated subquery was in the input of a or operator that had a filter equating the outer-column reference to a non-outer column in the grouping operator’s input, while the grouping column set did not include the replacement column but functionally determined it. This bug was introduced in v23.1.
The AWS endpoint and cloud custom HTTP client configuration are now considered when is used for cloud storage. Previously, these were only considered when using explicit credentials.
Fixed a bug where jobs created in sessions with non-zero session timezone offsets could hang before starting or report incorrect creation times when viewed in and the DB Console.
Fixed a bug that could prevent a from being able to resume after being paused for a prolonged period of time.
Fixed a bug where backup schedules could advance a protected timestamp too early, which caused incremental backups to fail.

Performance improvements

The now plans limited, scans in more cases when the new session setting is set to on.

Contributors

This release includes 85 merged PRs by 39 authors.

v24.1.5

Release Date: September 25, 2024

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.5.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.5.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.5.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.5.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.5.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.5.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.5.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.5.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.5.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.5.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.5

General changes

Upgraded the grpc version to v1.56.3.

Enterprise edition changes

Introduced the new changefeed.protect_timestamp.lag, which controls when a protected timestamp is updated. The will only be updated if the set changefeed.protect_timestamp.lag value has passed between the last protected timestamp and the .
, SHOW CHANGEFEED JOBS, and no longer expose user-sensitive information like client_key.
Added two network metrics, changefeed.network.bytes_in and changefeed.network.bytes_out. These metrics track the number of bytes sent by individual to the following sinks:
- . If are enabled, the metric will have a kafka label.
- . If are enabled, the metric will have a webhook label.
- . If are enabled, the metric will have a pubsub label.
- . If are enabled, the metric will have a sql label.

SQL language changes

The session setting can now be used to force to use query plans that are once, and reused in future executions without re-optimization, as long as it does not become stale due to or a collection of new . The setting takes effect during EXECUTE commands. includes a plan type field. If a generic query plan is optimized for the current execution, the plan type will be generic, re-optimized. If a generic query plan is reused for the current execution without performing optimization, the plan type will be generic, reused. Otherwise, the plan type will be custom.
The session setting can now be used to instruct the system to automatically determine whether to use custom or generic query plans for the execution of a . Custom query plans are optimized on every execution, while generic plans are once and reused on future executions as-is. Generic query plans are beneficial in cases where query optimization contributes significant overhead to the total cost of executing a query.

Operational changes

There are now structured that report connection breakage during node shutdown. Previously, the logs existed, but were unstructured. The logs appear in the . There are two new events:
- The node_shutdown_connection_timeout event is logged after the timeout defined by the cluster setting transpires, if there are still open SQL connections.
- The node_shutdown_transaction_timeout event is logged after the timeout defined by the cluster setting transpires, if there are still open transactions on those SQL connections.
Added a new configuration parameter server.cidr_mapping_url, which maps IPv4 CIDR blocks to arbitrary tag names.
Modified the metrics sql.bytesin and sql.bytesout to work as aggregate metrics if are enabled.
Added three new network-tracking metrics. rpc.connection.connected is the number of rRPC TCP level connections established to remote nodes. rpc.client.bytes.egress is the number of TCP bytes sent via gRPC on connections CockroachDB initiates. rpc.client.bytes.ingress is the number of TCP bytes received via gRPC on connections CockroachDB initiated.
This commit adds two metrics: changefeed.network.bytes_in and changefeed.network.bytes_out. These metrics track the number of bytes sent by the individual to different .

DB Console changes

The user experience for charges in the now has hover behavior that focuses on individual lines and shows values under the mouse pointer.
Users with the privilege can download statement bundles from the .
Users with the privilege can now request, view, and cancel statement bundles in the .
The will show a notification alerting customers without an Enterprise license to upcoming license changes with a link to more information.

Bug fixes

Previously, and legacy were incorrectly allowed to be run concurrently, which could lead to failing or hung schema change jobs.
Fixed a bug that caused errors like ERROR: column 'crdb_internal_idx_expr' does not exist when accessing a table with an where the expression evaluates to an ENUM type, for example, CREATE INDEX ON t ((col::an_enum)).
Fixed a bug where NaN or Inf could not be used as the default value for a parameter in statements.
Fixed a bug in which queries using and a could return incorrect results under isolation. This bug was present when support for SKIP LOCKED under READ COMMITTED isolation was introduced in v24.1.0.
Fixed a bug in which some queries using could still block on locked rows when using under isolation. This bug was present when optimizer_use_lock_op_for_serializable was introduced in v24.1.0.
Function input parameters for can no longer be of the VOID type, which matches the behavior of PostgreSQL.
Fixed a bug in the public preview of that could prevent a node from starting if it crashed during a failover.
could fail with: could not insert session...: unexpected value, if an ambiguous result error was encountered when inserting into the sqlliveness table.
Internally issued queries that are not initiated within a no longer respect a . This includes: background , queries issued by the that perform introspection, and the .
Fixed a rare bug in that could cause it to fail with an error like timed out: value differs between local setting and KV.
Fixed a bug where the did not prevent a table from being referenced by a .
Fixed a bug where the would aggressively prevent all statements from working.
Fixed a slow-building memory leak when using .
Fixed a potential memory leak in using a . The memory leak could occur if both the cluster settings and are set to true and the changefeed received an error while attempting to write to the cloud storage sink.
Fixed a bug that prevented buffered file sinks from being included when iterating over all file sinks. This led to problems such as the debug zip command not being able to fetch logs for a cluster where buffering was enabled.

v24.1.4

Release Date: August 29, 2024

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.4.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.4.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.4.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.4.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.4.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.4.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.4.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.4.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.4.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.4.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.4

Security updates

URLs in the following SQL statements are now sanitized of any secrets before being written to .

Enterprise edition changes

Added a new Kafka that uses the franz-go library and CockroachDB’s batching_sink implementation. The new Kafka sink can be enabled with the changefeed.new_kafka_sink_enabled , which is disabled by default.
The new Kafka sink, enabled with , as well as the Google Cloud Pub/Sub sink, now display notices indicating the topics that a changefeed will emit to.

SQL language changes

Added a new sql.auth.grant_option_for_owner.enabled to prevent the from being given to the owner of an object by default. The cluster setting defaults to true, retaining the existing behavior; when it is set to false, the GRANT OPTION is not implicitly given to an object’s owner. The owner will still have all privileges on an object except the ability to grant privileges to other users.

Command-line changes

A --locality-file flag is now available on the and commands. This allows specifying node (typically a region value) as a file, rather than by using the .

DB Console changes

The in the DB Console now show a loading state while loading information for databases and tables, including size and range counts.
On the in the DB Console, table names will no longer appear with quotes around the schema and table name.

Bug fixes

Fixed a bug introduced in v23.2.0 in which CockroachDB would hit an internal error when evaluating into tables where the source was a clause with a single row and at least one Boolean expression.
Fixed a bug in which the statement was disallowed when the default_transaction_read_only was set to on.
In the , events now display correctly even when no are included in the ALTER ROLE statement.
Fixed a formatting issue with the sql_sequence_cached_node value of the . This could lead to an error connecting to CockroachDB if this value was set as the default for serial_normalization via the cluster setting .
Fixed a bug where that were referenced by could fail with an error.
Fixed a bug that caused a memory leak when executing SQL statements with , for example, SELECT /* comment */ 1;. Memory owned by a SQL session would continue to grow as these types of statements were executed. The memory would only be released when closing the . This bug had been present since v23.1.
Fixed a bug where could hang if the lease rangefeed stopped receiving updates.
Fixed small memory leaks that would occur during creation.
Fixed a memory leak that could occur when specifying a non-existent name in the connection string.
Fixed a bug where would not correctly short-circuit if the given index already existed.
Fixed a bug in syntax validation, in which the DESCENDING clause was not allowed for non-terminal columns of an . Only the last column of an inverted index should be prevented from being DESCENDING. This is now properly checked.
Fixed a bug where an could store a column in the primary index if that column had a mixed-case name.
Setting or dropping a default value on a is now blocked, even for NULL defaults. Previously, setting or dropping a default value on a computed column was a no-op.
Fixed a bug that could cause spurious user permission errors when multiple databases shared a common schema with a routine referencing a table. The bug had existed since v22.2 when were introduced.
Fixed a bug where would return an error while fetching unstructured/malformed logs.
Fixed a bug where a hash-sharded could not be created if it referred to columns that had a backslash in the name.
Fixed a bug in which the output of for various CREATE statements was not redacted. This bug had existed since was introduced in v23.1 and affects the following statements:
- EXPLAIN (OPT, REDACT) CREATE TABLE
- EXPLAIN (OPT, REDACT) CREATE VIEW
- EXPLAIN (OPT, REDACT) CREATE FUNCTION

v24.1.3

Release Date: August 1, 2024

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.3.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.3.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.3.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.3.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.3.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.3.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.3.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.3.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.3.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.3.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.3

SQL language changes

statements are now supported when executed via Cloud Console .
Added the . The default value is true, which maintains consistency with CockroachDB’s previous behavior: users granted a privilege with can in turn grant that privilege to others. When sql.auth.grant_option_inheritance.enabled is set to false, the GRANT OPTION is not inherited through role membership, thereby preventing descendant roles from granting the privilege to others. However, the privilege itself continues to be inherited through role membership.

Operational changes

crdb_internal.cluster_execution_insights.txt and crdb_internal.cluster_txn_execution_insights.txt have been removed from the . These files contained cluster-wide insights for statements and transactions. Users can still rely on the insights in crdb_internal.node_execution_insights.txt and crdb_internal.node_txn_execution_insights.txt.
For the , TCL sampled_query events will now be sampled at the rate specified by the setting , which is already used to limit the rate of sampling DML statements.

Bug fixes

Fixed a bug where collection of for very long-running could use excessive space in the job_info system table and cause some interactions with the jobs system to become slow.
Fixed a bug where a change to a could cause queries against tables using that type to fail with an error: histogram.go:694: span must be fully contained in the bucket. The change to the user-defined type could come directly from an statement, or indirectly from an or statement (which implicitly change the type). This bug has existed since UDTs were introduced in v20.2.
Fixed a bug in which constant patterns containing certain sequences of backslashes did not become constrained scans. This bug has been present since v21.1.13 when support for building constrained scans from LIKE patterns containing backslashes was added.
Fixed the statistics estimation code in the so it does not use the empty histograms produced if has been disabled during stats collection due to excessive memory utilization. Now the optimizer will rely on distinct counts instead of the empty histograms and should produce better plans as a result. This bug has existed since CockroachDB v22.1.
Fixed a bug where statements with could hit undefined column errors on .
Fixed a bug where CockroachDB would hit an internal error when evaluating into tables where the source is a with a single row and at least one boolean expression. The bug was introduced in v23.2.0.
Fixed a bug in where the command fails when a custom SQL port is used and the flag is provided.
Fixed a bug where a that shared a name with a would not be resolved, even if the UDF had higher precedence according to the variable.
Fixed a bug that caused to incorrectly respect a statement timeout.
Fixed a bug where could fail if any tables under the given database have .
Fixed a PostgreSQL incompatibility bug when inputting public as user name for such as has_database_privilege and has_schema_privilege.
Fixed a bug when a database with a .
Fixed a bug where the page crashed if the range information was not available.
Fixed a bug where CockroachDB could incorrectly evaluate an filter if it was applied to non- NULL tuples that had NULL elements, such as (1, NULL) or (NULL, NULL). This bug has existed since v20.2.
The sql_sequence_cached_node value of the was not correctly formatted. This could lead to errors while connecting to CockroachDB if the default value of serial_normalization was set to serial_normalization. The formatting bug was fixed, which also fixes the errors when connecting.

Performance improvements

Starting a cockroach process will no longer flush buffered to configured unless the process is running under systemd, where cockroach runs with the NOTIFY_SOCKET environment variable.
that cause a data backfill, such as adding a non-nullable column or changing the primary key, will now split and scatter the temporary indexes used to perform the change. This reduces the chance of causing a that can slow down foreground traffic.

Contributors

This release includes 122 merged PRs by 39 authors.

v24.1.2

Release Date: July 2, 2024

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.2.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.2.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.2.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.2.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.2.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.2.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.2.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.2.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.2.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.2.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.2

Enterprise edition changes

Added error messages for unsupported Apache Pulsar sink parameters, e.g. topic_prefix is not yet supported.
Fixed a bug that was present since v22.2 where with long-running might incorrectly restore checkpoint job progress and drop events during due to transient errors or node restarts. The bug was most likely to occur in clusters with the following contributing factors:
- The changefeed.shutdown_checkpoint.enabled was enabled.
- The cluster settings changefeed.frontier_checkpoint_frequency and low changefeed.frontier_highwater_lag_checkpoint_threshold were set low, which resulted in the initial scan taking many multiples of the configured frequency to complete.
- There were multiple target tables with significant differences in row counts in one changefeed.
- The changefeed target tables were large with many ranges.
- The initial scan took a long time to complete (an hour or longer).

Operational changes

Improved over volumes that dynamically change their size over the life of the cockroach process.
The default values for the following were updated from 100000 to 7500. These settings control the maximum number of (distinct combinations of statements and ) CockroachDB can store in memory, with stats being flushed on a 10m by default. You can increase these settings if your workload produces more unique fingerprints than this amount within the flush interval, and you notice that SQL stats are missing.

DB Console changes

The favicon now renders properly for , along with other image files.

Bug fixes

now includes . It had omitted those types ever since composite types were added in v23.1.
Fixed a crash introduced in v24.1.0-beta.2 that could occur when planning collection on a table with a using a when the sql.stats.virtual_computed_columns.enabled (introduced in v24.1.0-alpha.1) was set to true.
Fixed handling in the when columns are included in the STORING() clause of a statement. CockroachDB now checks if the column is virtual up-front, and properly detects when a column is already handled by an existing when the column name has UTF-8 characters.
Fixed a bug where a change to a could cause queries against tables using that type to fail with an error message like: "histogram.go:694: span must be fully contained in the bucket". The change to the user-defined type could come directly from an statement, or indirectly from an or statement (which implicitly changes the crdb_internal_region type). This bug had existed since UDTs were introduced in v20.2.
Fixed a bug where had the same ID for different SQL statements.
Fixed an issue where with a default value of an empty would not succeed.
will now fail with a well-formed error message and code 42601 if a statement tries to add a on an expression.
Fixed a bug where the would be created with the wrong owner. Previously the would own the public schema. Now, the database owner is also the owner of the public schema. The owner can be altered after the schema is created.
Fixed a bug in v24.1, v23.2, and v23.1 where using the changefeed.aggregator.flush_jitter with the option set to 0 could cause panics.
The log message "expiration of liveness record... is not greater than expiration of the previous lease... after liveness heartbeat" is no longer generated.
Fixed a bug introduced in v23.2.0 in which CockroachDB would hit an internal error when evaluating into tables where the source was a VALUES clause with a single row and at least one boolean expression.

Performance improvements

Improved the efficiency of error handling in the to reduce the CPU overhead of statement timeout handling and reduce the potential for more statement timeouts.
Some checks when scanning the crdb_internal.system_jobs internal table now happen once before the scan, instead of once for each row. This improves performance for queries that read from crdb_internal.system_jobs.

Miscellaneous

A optimization to reduce duplicates during aggregator restarts has been disabled due to poor performance.

Contributors

This release includes 78 merged PRs by 35 authors.

v24.1.1

Release Date: June 14, 2024

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.1.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.1.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.1.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.1.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.1.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.1.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.1.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.1.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.1.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.1.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.1

Enterprise edition changes

Fixed a bug introduced in v22.2 where a with a long-running might incorrectly restore checkpoint job progress and drop events during a due to transient errors or node restarts. The bug was most likely to occur in clusters with the following contributing factors:
- The changefeed.shutdown_checkpoint.enabled was enabled (in clusters running v23.2 and later).
- The cluster settings changefeed.frontier_checkpoint_frequency and low changefeed.frontier_highwater_lag_checkpoint_threshold were set low, which resulted in the initial scan taking many multiples of the configured frequency to complete.
- There were multiple target tables with significant differences in row counts in one changefeed.
- The changefeed target tables were large with many ranges.
- The initial scan took a long time to complete (an hour or longer).
History retention jobs created upon completion of no longer erroneously indicate that they failed when they expire.

SQL language changes

The can now plan constrained scans over partial indexes in more cases, particularly on partial indexes with predicates referencing .
The storage parameter ttl_delete_rate_limit, which determines the rate limit for deleting expired rows, is now set to 100 by default.
CockroachDB no longer limits precision when converting to JSON.
The optimizer_push_offset_into_index_join has been added. When enabled, the will attempt to push offset expressions into index join expressions to produce more efficient query plans. The setting is enabled by default on v24.1 and later, and disabled on v23.2.
The default value of the sql.defaults.results_buffer.size has been changed from 16KiB to 512KiB. This reduces the chance that clients using transactions will encounter errors that cannot automatically be retried within CockroachDB.

Operational changes

The default values for the sql.metrics.max_mem_stmt_fingerprints and sql.metrics.max_mem_txn_fingerprints have been changed from 100000 to 5000, thus lowering the default limits for in-memory statement and transaction fingerprints.
The new sql.pgwire.pipeline.count shows the number of wire protocol commands that have been received by the server, but have not yet begun processing. This metric will only grow if clients are using the “pipeline mode” of the PostgreSQL wire protocol.
The client_authentication_ok and client_session_end messages are now logged to the SESSIONS unconditionally. Previously, these would be logged only if the server.auth_log.sql_sessions.enabled was set to true. All other SESSIONS log messages are logged only if server.auth_log.sql_sessions.enabled or server.auth_log.sql_connections.enabled are set to true. To prevent logging of client_authentication_ok or client_session_end messages, you can optionally disable the SESSIONS log channel.

DB Console changes

Fixed a bug where the would falsely report high lag for multi-node clusters and on cutover.
Fixed a bug that caused entries sorted by % of Runtime to be sorted incorrectly.
The “Admission Delay Rate”, “Admission Work Rate”, and “Requests Waiting For Flow Tokens” time-series charts have been removed from the DB Console. These charts can be difficult to interpret and provide little value for overload investigations.
The now includes descriptions for all metrics.
Metrics on the have been reordered to improve their categorization. The metrics are now roughly in the following order: 1. Metrics to help determine which resource is constrained (IO, CPU); 2. Metrics to narrow down which queues are seeing requests waiting; 3. More advanced metrics about system health (goroutine scheduler, L0 sublevels, etc.).
New metrics cr.store.storage.l0-sublevels and cr.node.go.scheduler_latency-p99.9 on the provide better visibility into overloaded resources.
There are now four separate graphs for Admission Queue Delay: 1. Foreground (regular) CPU work; 2. Store (IO) work; 3. Background (elastic) CPU work; 4. Replication Admission Control (store overload on replicas).

Bug fixes

Fixed a bug that would occur when is followed by DROP SCHEMA CASCADE... in the same transaction. Previously, the ALTER TYPE schema change would get queued up to run at commit time, but by that point, the type may have already been removed, so the commit could fail.
Tables are now automatically repaired when the errors invalid inbound foreign key... origin table ID should be... or invalid outbound foreign key... reference table ID should be... occur.
Fixed a bug where a failed could not be retried without manual intervention.
Fixed a bug introduced in alpha versions of v23.1 where calling a routine could result in an unexpected function... does not exist error. The bug is triggered when the routine is called twice using the exact same SQL query, and either: (a) the routine has polymorphic arguments, or: (b) between the two calls, the routine is replaced by a routine with the same name and different parameters.
Fixed a rare bug where a lease transfer could lead to a side-transport update saw closed timestamp regression panic. The bug could occur when a node was overloaded and .
Fixed a crash introduced in v24.1.0-beta.2 that could occur when planning statistics collection on a table with a using a when the newly-introduced sql.stats.virtual_computed_columns.enabled is set to true. (The setting was introduced in v24.1.0-alpha.1, and defaults to true.)
Fixed a bug where an statement could hang if the table had any indexes that were referred to by or using the FORCE INDEX clause.
Fixed a bug introduced in v24.1.0 where the max_decimal_digits argument of the st_geojson was ignored and the default was used instead.
Scattering a range with a replication factor of 1 now no longer erroneously up-replicates the range to two replicas. Leases will also no longer thrash between nodes when perturbed with a replication factor of 1.
Fixed a bug where, if the ttl_row_stats_poll_interval storage parameter was non-zero for a table with enabled, the queries issued to update row statistics could block the job from completing. Now, if the job completes, these statistics queries are cancelled. This means that the jobs.row_level_ttl.total_rows and jobs.row_level_ttl.total_expired_rows metrics will report 0 if the job finishes before the row stats queries complete.
Fixed a bug where a or command could leave references behind inside types, which could prevent subsequent commands from working.
Fixed a bug where the results_buffer_size could not be configured by using the “options” query parameter in the connection string, but only as a top-level query parameter. Now, results_buffer_size can be configured in either part of the connection string. This variable still cannot be changed with the command after the session begins.
Fixed a bug introduced in v20.2 where a change to a could cause queries against tables using that type to fail with an error message like histogram.go:694: span must be fully contained in the bucket. The change to the user-defined type could come directly from an statement, or indirectly from an or statement (which implicitly change the crdb_internal_region type).

Performance improvements

Improved the efficiency of error handling in the in order to reduce the CPU overhead of statement timeout handling and reduce the potential for more statement timeouts.
Due to its poor performance, a optimization that aimed to reduce duplicates during aggregator restarts due to its bad performance has been disabled.

Contributors

This release includes 173 merged PRs by 42 authors.

v24.1.0

Release Date: May 20, 2024 With the release of CockroachDB v24.1, we’ve added new capabilities to help you migrate, build, and operate more efficiently. Refer to our summary of the most significant user-facing changes under Feature Highlights.

Downloads

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.0.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.0.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.0.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.0.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.0.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.0.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.0.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.0.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.0.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.0.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v24.1.0

Feature highlights

This section summarizes the most significant user-facing changes in v24.1.0 and other features recently made available to CockroachDB users across versions. For a complete list of features and changes in v24.1, including bug fixes and performance improvements, refer to the release notes for previous v24.1 testing releases. You can also search the docs for sections labeled .

Feature categories
Additional information

In CockroachDB Self-Hosted, all available features are free to use unless their description specifies that an Enterprise license is required. For more information, refer to the .

Performance

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
WAL (Write-Ahead Logging) Failover When a CockroachDB node is configured to run with multiple stores, you can mitigate some effects of disk stalls by configuring the node to to another store’s data directory. This feature is in preview.	24.1
Autocommit DDL In 24.1 we have added the `autocommit_before_ddl`. When set to true, any schema change statement that is sent during an explicit transaction will cause the transaction to commit before executing the schema change. This setting can be used to improve compatibility with some tools that do not work well due to our limitations with schema changes in explicit transactions. It also can be used to use schema changes under `READ COMMITTED` more easily, without needing to teach the schema changer about `READ COMMITTED`.	24.1
Statistics for virtual computed columns CockroachDB now collects statistics for , making it possible to optimize query plans for tables that have these columns. Customers will see better query performance for queries that involve virtual computed columns. For more information, you can also view a video demo.	24.1
Write Amplification Improvements A number of improvements are now on by default, leading to a reduction in . Of particular note, a vast majority of range snapshots previously ingested into L0 are now ingested directly into L6 in the , reducing write and read amplification with positive effects to node stability and SQL performance.	24.1
Increased SLA for multi-region Dedicated clusters CockroachDB Dedicated multi-region clusters now offer a five-nines (99.999%) availability target.	All^*

Change Data Capture

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
Improved performance for changefeeds at scale is a subsystem that improves the performance of with scale. In v24.1, Mux rangefeeds are enabled by default.	24.1
Emit changefeed messages to an Azure Event Hub Changefeeds can emit messages to an , which is compatible with Apache Kafka. You can use the Kafka changefeed and sink configuration options.	24.1
Google Cloud Pub/Sub sink for changefeeds is now generally available The changefeed is GA.	24.1
Filter changefeed messages based on cluster, SQL session, or row-level TTL jobs Use the `disable_changefeed_replication` session variable to prevent changefeeds from emitting messages for any changes during that session. Also in v24.1, you can enable the `ignore_disable_changefeed_replication` option to ignore the storage parameter or cluster setting that disables changefeed replication. These can be useful to manage multiple changefeed use cases on the same table.	24.1
Set Kafka quotas per changefeed For , implement a resource usage limit per changefeed by setting a client ID and quota in your Kafka server’s configuration.	24.1

Recovery

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
Physical Cluster Replication is now generally available is an asynchonous replication feature that allows your cluster to recover from full-cluster failure with a low RPO and RTO. In 24.1, it is a GA feature, requiring an Enterprise license, and only available for self-hosted CockroachDB deployments. For more information, refer to the and a blog post about Physical Cluster Replication.	24.1

Security

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
Private connectivity in CockroachDB Dedicated with Google Cloud Private Service Connect using Private Service Connect is now available in preview for CockroachDB Dedicated clusters on GCP. For more information, refer to and a video about how to set it up.	All^*
Support for matching against SUBJECT When using certificate based authentication, CockroachDB now supports mapping of SQL user roles to used for TLS authentication. Subject mapping is useful if: - You run your own Certificate Authority (CA) infrastructure. - You need to use your existing CA infrastructure to manage SQL user authentication. - You need to use the same CA for multiple CockroachDB clusters.	24.1

Migrations

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
is GA. MOLT Fetch automatically imports data from a PostgreSQL, MySQL, or CockroachDB source to a target CockroachDB database. If the fetch process encounters an error, data import can be continued from the point where it was interrupted. MOLT Fetch can be configured to replicate ongoing changes on the source database to CockroachDB following the initial data load.	All^*

SQL

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
Stored Procedures and UDF Improvements Support for PL/pgSQL, user-defined functions, and stored procedures is now expanded: - parameters can be specified. - PL/pgSQL can be used together with conditions. - UDFs can . - Stored procedures can using a . - is possible using COMMIT, ROLLBACK, and SET TRANSACTION statements. For more information, you can also view a video demo.	24.1
Read Committed Isolation in GA Read Committed isolation is now GA. Under `READ COMMITTED` isolation, DDL operations can be auto-committed, and `RETRY_SERIALIZABLE` errors are absent. This offers a simpler migration path for applications and removes the need for client-side retry handling, which is necessary under `SERIALIZABLE` isolation. For more information, you can also view a video about using Read Committed isolation and the blog post Isolation levels without the anomaly table.	24.1
SELECT FOR SHARE updates A shared lock that is acquired explicitly using or implicitly by a read-committed transaction, can now be re-acquired with higher strength by either using a `SELECT FOR UPDATE` statement or by writing to the key.	24.1
SHOW DEFAULT SESSION VARIABLES FOR ROLE Previously, a database administrator could discover which session variables were set for a role only by switching into to that user or querying a system table. The new command shows the database administrator the default values for session variables applied to a given user.	24.1

Operations

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
New Regions for CockroachDB Dedicated Cockroach Cloud is now available in additional Azure regions. This expansion enhances our global reach and offers more options for deploying resilient, distributed databases with low latency and high availability. With these , you can now select a geographical location that best fits your needs, reducing data latency and ensuring compliance with regional data residency regulations. Deploying in a region close to your service or customers means improved performance and a better user experience.	All^*
Organize Cloud clusters using Folders help users organize and manage access for Clusters by projects, teams or business units. This feature is now in public preview and available to all Cloud organizations. For additional details, refer to the	All^*
CockroachDB Cloud Terraform provider IAM enhancements The CockroachDB Cloud Terraform provider has new resources for User Role Grant and Service Accounts, and a new data source for Folders. These new features improve customers’ ability to manage secure access to data, API, and infrastructure on CockroachDB Cloud.	All^*

Observability

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
CockroachDB Dedicated supports a Prometheus-compatibile metric scrape endpoint. The for CockroachDB Dedicated is generally available.	All^*
Export CockroachDB Dedicated metrics to Azure Monitor CockroachDB Dedicated supports in limited access. Contact your Cockroach Labs account team for access.	All^*
Export CockroachDB Dedicated logs to Azure Monitor CockroachDB Dedicated supports in limited access. Contact your Cockroach Labs account team for access.	All^*

Feature detail key
*	Features marked “All*” were recently made available in the CockroachDB Cloud platform. They are available for all supported versions of CockroachDB, under the deployment methods specified in their row under Availability.
**	Features marked “All**” were recently made available via migration tools maintained outside of the CockroachDB binary. They are available to use with all supported versions of CockroachDB, under the deployment methods specified in their row under Availability.
	Feature is available for this deployment method of CockroachDB as specified in the icon’s column: CockroachDB Self-Hosted, CockroachDB Dedicated, or CockroachDB Serverless.
	Feature is not available for this deployment method of CockroachDB as specified in the icon’s column: CockroachDB Self-Hosted, CockroachDB Dedicated, or CockroachDB Serverless.

Backward-incompatible changes

Before , be sure to review the following backward-incompatible changes, as well as key cluster setting changes, and adjust your deployment as necessary.

queries can no longer use a timestamp followed by a question mark to signify a future-time value. This was an undocumented syntax.
The isolation level now requires the cluster to have a valid enterprise license. Otherwise, transactions which are configured to run as READ COMMITTED will be upgraded to , as described in the next note.
The sql.txn.read_committed_isolation.enabled is now true by default. As a result for enterprise users, transactions are not automatically upgraded to , and will run as READ COMMITTED by default. On v23.2, refer to the graph in the DB Console to check whether any transaction is being upgraded from a weaker isolation level to SERIALIZABLE, and could therefore run differently on v24.1.

Features that require upgrade finalization

During a major-version upgrade, certain features and performance improvements may not be available until the upgrade is finalized.

Splits no longer hold latches for time proportional to the range size while computing MVCC statistics. Instead, MVCC statistics are pre-computed before the critical section of the split. As a side effect, the resulting statistics are no longer 100% accurate because they may correctly distribute writes concurrent with the split. To mitigate against this potential inaccuracy, and to prevent the statistics from drifting after successive splits, the existing stored statistics are re-computed and corrected if needed during the non-critical section of the split.

Key Cluster Setting Changes

The following changes should be reviewed prior to upgrading. Default cluster settings will be used unless you have manually set a value for a setting. This can be confirmed by checking the system.settings table (select * from system.settings) to view the non-default settings.

sql.txn.read_committed_isolation.enabled is now true by default. When set to true, transactions use the READ COMMITTED isolation level if specified by BEGIN / SET commands.
- If the cluster setting is false, as was the default in v23.2, such READ COMMITTED transactions will instead run as SERIALIZABLE.
- To check whether any transactions are being upgraded to SERIALIZABLE, see the graph in the DB Console.”
The changefeed.balance_range_distribution.enabled is now deprecated. Instead, use the new cluster setting changefeed.default_range_distribution_strategy. changefeed.default_range_distribution_strategy='balanced_simple' has the same effect as setting changefeed.balance_range_distribution.enabled=true. It does not require initial_scan='only', which was required by the old setting.
Added the security.client_cert.subject_required.enabled which enforces a mandatory requirement for the client certificate’s role subject to be set. The subject can be defined through either the subject role option or by specifying the root-cert-distinguished-name and node-cert-distinguished-name properties. This setting applies to both RPC access and login via authCert.
The sql.contention.record_serialization_conflicts.enabled is now on by default. As a result, any that contains conflicting transaction information will be recorded by the contention registry, improving the ability to troubleshoot. For more information, refer to the documentation.
The new storage.sstable.compression_algorithm configures the compression algorithm used when compressing sstable blocks. Supported values are: “snappy” and “zstd” [snappy = 1, zstd = 2 ]. Changing the default of snappy to zstd can result in substantial performance improvement, however, the effects this change may be highly dependent on the workload and data, so experimentation is recommended before enabling zstd in production environments.
The new setting storage.wal_failover.unhealthy_op_threshold allows you to set the latency threshold at which a WAL (Write-Ahead Logging) write is considered unhealthy. When exceeded, the node will attempt to write WAL entries to a secondary store’s volume. For more information, refer to
The new server.max_open_transactions_per_gateway , when set to a non-negative value, allows only admin users to execute a query if the number of open transactions on the current gateway node is already at the configured limit.
The new server.redact_sensitive_settings.enabled ( false by default), when set to true, redacts the values of the following settings in the output of SHOW commands or other introspection interfaces. In the future, newly-added sensitive cluster settings will be redacted as well. Users with the MODIFYCLUSTERSETTING can always view the unredacted settings.
The new boolean changefeed option , when set to true, prevents the changefeed from filtering events even if CDC filtering is configured via the disable_changefeed_replication , sql.ttl.changefeed_replication.disabled , or the ttl_disable_changefeed_replication .
The provisioned-rate field, if specified, should no longer accept a disk-name or an optional bandwidth field. To use the disk bandwidth constraint the store-spec must contain provisioned-rate=bandwidth=<bandwidth-bytes/s>, otherwise the cluster setting kvadmission.store.provisioned_bandwidth will be used. When set to a non-zero value, this is used as the provisioned bandwidth (in bytes/s), for each store. It can be overridden on a per-store basis using the —store flag. Note that setting the provisioned bandwidth to a positive value may enable disk bandwidth based admission control, since admission.disk_bandwidth_tokens.elastic.enabled defaults to true.
Removed in v24.1:
- sql.show_ranges_deprecated_behavior.enabled
- sql.trace.session_eventlog.enabled
- changefeed.balance_range_distribution.enabled

Deprecations

changefeed.balance_range_distribution.enable is now deprecated. Instead, use the new changefeed.default_range_distribution_strategy. changefeed.default_range_distribution_strategy='balanced_simple' has the same effect as setting changefeed.balance_range_distribution.enable=true. It does not require initial_scan='only', which was required by the old setting.
The cockroach connect command has been removed. This command was in CockroachDB v23.2.

Known limitations

For information about new and unresolved limitations in CockroachDB v24.1, with suggested workarounds where applicable, refer to .

Additional resources

Resource	Topic	Description
Cockroach University	Introduction to Distributed SQL and CockroachDB	This course introduces the core concepts behind distributed SQL databases and describes how CockroachDB fits into this landscape. You will learn what differentiates CockroachDB from both legacy SQL and NoSQL databases and how CockroachDB ensures consistent transactions without sacrificing scale and resiliency. You’ll learn about CockroachDB’s seamless horizontal scalability, distributed transactions with strict ACID guarantees, and high availability and resilience.
Cockroach University	Practical First Steps with CockroachDB	This course will give you the tools you need to get started with CockroachDB. During the course, you will learn how to spin up a cluster, use the Admin UI to monitor cluster activity, and use SQL shell to solve a set of hands-on exercises.
Cockroach University	Enterprise Application Development with CockroachDB	This course is the first in a series designed to equip you with best practices for mastering application-level (client-side) transaction management in CockroachDB. We’ll dive deep on common differences between CockroachDB and legacy SQL databases and help you sidestep challenges you might encounter when migrating to CockroachDB from Oracle, PostgreSQL, and MySQL.
Cockroach University	Building a Highly Resilient Multi-region Database using CockroachDB	This course is part of a series introducing solutions to running low-latency, highly resilient applications for data-intensive workloads on CockroachDB. In this course we focus on surviving large-scale infrastructure failures like losing an entire cloud region without losing data during recovery. We’ll show you how to use CockroachDB survival goals in a multi-region cluster to implement a highly resilient database that survives node or network failures across multiple regions with zero data loss.
Docs		This page summarizes the steps of migrating a database to CockroachDB, which include testing and updating your schema to work with CockroachDB, moving your data into CockroachDB, and testing and updating your application.
Docs		This page provides a starting point for understanding the architecture and design choices that enable CockroachDB’s scalability and consistency capabilities.
Docs		The page summarizes the standard SQL features CockroachDB supports as well as common extensions to the standard.
Docs		This page summarizes CockroachDB’s data streaming capabilities. Change data capture (CDC) provides efficient, distributed, row-level changefeeds into a configurable sink for downstream processing such as reporting, caching, or full-text indexing.
Docs		This page describes the backup job workflow with a high-level overview, diagrams, and more details on each phase of the job.

v24.1.0-rc.2

Release Date: May 16, 2024

Downloads

CockroachDB v24.1.0-rc.2 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments.

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.0-rc.2.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-rc.2.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.0-rc.2.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-rc.2.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.0-rc.2.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-rc.2.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.0-rc.2.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-rc.2.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.0-rc.2.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.0-rc.2.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach-unstable:v24.1.0-rc.2

Bug fixes

Fixed a bug that was present since v22.2 where with long-running might incorrectly restore checkpoint job progress and drop events during due to transient errors or node restarts. The bug was most likely to occur in clusters with the following contributing factors:
- The changefeed.shutdown_checkpoint.enabled was enabled (in clusters running v23.2 and later).
- The cluster settings changefeed.frontier_checkpoint_frequency and low changefeed.frontier_highwater_lag_checkpoint_threshold were set low, which resulted in the initial scan taking many multiples of the configured frequency to complete.
- There were multiple target tables with significant differences in row counts in one changefeed.
- The changefeed target tables were large with many ranges.
- The initial scan took a long time to complete (an hour or longer).
Fixed a crash introduced in v24.1.0-beta.2 that could occur when planning on a table with a using a user-defined type and the sql.stats.virtual_computed_columns.enabled is set to true. sql.stats.virtual_computed_columns.enabled was introduced in v24.1.0-alpha.1 as true by default and introduced in v23.2.5 as false by default.

Contributors

This release includes 3 merged PRs by 3 authors.

v24.1.0-rc.1

Release Date: May 8, 2024

Downloads

CockroachDB v24.1.0-rc.1 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments.

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.0-rc.1.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-rc.1.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.0-rc.1.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-rc.1.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.0-rc.1.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-rc.1.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.0-rc.1.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-rc.1.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.0-rc.1.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.0-rc.1.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach-unstable:v24.1.0-rc.1

SQL language changes

Added a new optimizer_use_improved_multi_column_selectivity_estimate, which if enabled, causes the to use an improved selectivity estimate for multi-column predicates. This setting will default to true on v24.2 and later, and false on earlier versions.

Operational changes

Added two new : range.snapshots.upreplication.rcvd-bytes counts the number of recovery snapshot bytes received, and range.snapshots.upreplication.sent-bytes counts the number of Raft recovery snapshot bytes sent. Also updated range.snapshots.recovery.rcvd-bytes and range.snapshots.recovery.sent-bytes to only include Raft snapshots. A new line was added to the graph.

DB Console changes

Added a Replication Lag graph to the dashboard to measure replication lag between primary and standby clusters using .

Bug fixes

Fixed a bug that caused the and pages in the DB Console to display an incorrect value for Table Stats Last Updated.
Fixed a bug in the DB Console’s tool where store-level metrics were displayed only for the first store ID associated with the node. Now data is displayed for all stores present on a node, and a single time series is shown for each store, rather than an aggregated value for all of the node’s stores. This allows finer-grained monitoring of store-level metrics.
Fixed a bug introduced in v22.2 that could cause the internal error attempting to append refresh spans after the tracked timestamp has moved forward in some edge cases.
Fixed a bug where a TYPEDESC SCHEMA CHANGE job could retry forever if the descriptor it targeted was already dropped.
Fixed a bug where, if the legacy schema changer was enabled, the command would incorrectly require the user to have the CREATE on the parent database rather than only on the parent schema.
Fixed a bug where a would fail if it reported an out-of-bound progress fraction. The error is now logged and no longer causes the job to fail.

Performance improvements

Added a new optimizer_use_improved_zigzag_join_costing. When enabled and when the enable_zigzag_join is also enabled, the cost of zigzag joins is updated such that a zigzag join will be chosen over a scan only if it produces fewer rows than a scan.
Improved the selectivity estimation of multi-column filters when the multi-column distinct count is high. This prevents the from choosing a bad query plan due to over-estimating the selectivity of a multi-column predicate.
Improved the efficiency of error handling in the , to reduce the CPU overhead of statement timeout handling and reduce the potential for more statement timeouts.
Disabled a poorly-performing optimization that was intended to reduce duplicates during aggregator restarts.

Contributors

This release includes 57 merged PRs by 24 authors.

v24.1.0-beta.3

Release Date: April 30, 2024

Downloads

CockroachDB v24.1.0-beta.3 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments.

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Full CockroachDB executable

SQL-only command-line client executable

Windows (Experimental)

CockroachDB executable for Windows is experimental and not suitable for production deployments. Windows 8 or higher is required.

Docker image

docker pull cockroachdb/cockroach-unstable:v24.1.0-beta.3

SQL language changes

Updated the responses to display the object_type and object_name, which has replaced the relation_name column.
Added granted privileges to the command.
Introduced three new for controlling table statistics forecasting:
- is the minimum number of observed statistics required to produce a forecast.
- is the minimum R² (goodness of fit) measurement required from all predictive models to use a forecast.
- is the most a prediction can decrease, expressed as the minimum ratio of the prediction to the lowest prior observation.

Bug fixes

Fixed a bug that could lead to descriptors having privileges to roles that no longer exist. Added an automated clean up for inside descriptors.
Fixed a bug where combined with ( server.identity_map.configuration ) did not work since v23.1. For the feature to work correctly, the client must specify a valid db user in the .
Fixed a bug where the could drop a clause when there was an clause, and the ordering was partially provided by an input operator. For example, this bug could occur with an ordering such as ORDER BY a, b when the scanned index was only ordered on column a. The impact of this bug was that more rows may have been returned than specified by the LIMIT clause. This bug is only present when not using the . That is, when running with SET vectorize = off;. This bug has existed since CockroachDB v22.1.
Previously, CockroachDB could run into an internal error when evaluating routines with nested blocks. The bug is only present in 24.1.0-beta versions. This bug is now fixed.
Fixed a bug where and queries with a subquery were sometimes inappropriately using implicit locking within the subquery. This bug has existed since implicit FOR UPDATE locking was introduced in v20.1.
and a column with the same name no longer results in a "column already exists error".
Fixed a bug that could cause an internal error of the form invalid datum type given:..., expected... when a RECORD -returning , used as a data source, was supplied a column definition list with mismatched types. This bug has existed since v23.1.
Fixed a bug that could result in an internal error when attempting to create a routine using the (unsupported) %ROWTYPE syntax for a variable declaration. Now, an expected syntax error is returned instead.
Fixed a bug that could result in an assertion error during evaluation of routines that invoke procedures while using DEFAULT arguments. The bug was present in v24.1.0-beta releases and is now fixed.
Previously, privileges granted for were displaying in SHOW SYSTEM GRANTS with no associated object name. Now these privileges are no longer displayed. Instead, the statement SHOW GRANTS ON EXTERNAL CONNECTION should be used to view external connection privileges with their associated object name.
Statistics forecasts of zero rows can cause suboptimal . Forecasting will now avoid predicting zero rows for most downward-trending statistics.
Fixed a bug introduced in v23.2 that could cause a variable assignment to not be executed if the variable was never referenced after the assignment.

Performance improvements

More efficient are now generated for queries with text similarity filters, for example, text_col % 'foobar'. These plans are generated if the optimizer_use_trigram_similarity_optimization is enabled. It is disabled by default.
The now costs distinct-on operators more accurately. It may produce more efficient query plans in some cases.
Improved the speed for optimization of some statements using GROUP BY or DISTINCT or ON CONFLICT by skipping the rule SplitGroupByScanIntoUnionScans when it is not needed.

Contributors

This release includes 56 merged PRs by 25 authors.

v24.1.0-beta.2

Release Date: April 24, 2024

Downloads

CockroachDB v24.1.0-beta.2 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments.

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.0-beta.2.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-beta.2.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.0-beta.2.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-beta.2.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.0-beta.2.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-beta.2.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.0-beta.2.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-beta.2.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.0-beta.2.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.0-beta.2.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach-unstable:v24.1.0-beta.2

Security updates

Added the security.client_cert.subject_required.enabled that enforces a mandatory requirement for the client certificate’s role subject to be set. The subject can be defined through either the subject role option or by specifying the root-cert-distinguished-name and node-cert-distinguished-name properties. This setting applies to both RPC access and login via authCert.

Bug fixes

Fixed a bug where table statistics were sometimes not collected on tables that have virtual of a user-defined type when the sql.stats.virtual_computed_columns.enabled cluster setting is enabled. The setting was introduced in v23.2.4 and is disabled by default. Only clusters running v23.2.4 with the non-default setting are affected.

Contributors

This release includes 52 merged PRs by 28 authors.

v24.1.0-beta.1

Release Date: April 17, 2024

Downloads

CockroachDB v24.1.0-beta.1 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments.

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.0-beta.1.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-beta.1.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.0-beta.1.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-beta.1.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.0-beta.1.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-beta.1.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.0-beta.1.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-beta.1.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.0-beta.1.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.0-beta.1.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach-unstable:v24.1.0-beta.1

SQL language changes

no longer displays some internal retry counter columns ( last_run, next_run, num_runs ) and now only shows the statement, trace_id, and execution_errors columns when inspecting a specific job ID or IDs.
now shortens long job descriptions to 100 characters to make the table easier to read while the full description and statement can be inspected using SHOW JOB or SHOW JOBS on specific job IDs.
Extended to include dependencies between UDFs.
With set to true, statements now return an error if they do not contain either a WHERE clause or a LIMIT clause. Also, UPDATE and DELETE statements without WHERE clauses but with LIMIT clauses now bypass sql_safe_updates, which better matches MySQL behavior.
Added support for CALL statements. It is now possible to call a stored procedure from a PL/pgSQL routine.
DEFAULT expressions for input parameters of and stored procedures are now supported.

Command-line changes

The flag now accepts the special value path=* to apply the specified keys to all stores.

DB Console changes

The Commit Latency chart in the now aggregates by max instead of by sum for multi-node . This more accurately reflects the amount of time for events to be acknowledged by the downstream sink.
Introduced a license expiration message in the in the top-right corner of the primary header. This message indicates the remaining days before license expiration for clusters with an Enterprise or trial license.
The page no longer includes two columns related to a deprecated internal implementation detail (last execution time and execution count).
The timeseries graphs shown on the statement details page in the DB Console will now render properly, after fixing a bug related to setting the time range of the charts.
in the DB Console will now function properly for indexes on tables or columns whose names contain quotation marks or whitespace. For example: CREATE INDEX ON "my table" ("my col");.

Bug fixes

Sequence options for NO MINVALUE and NO MAXVALUE now match PostgreSQL behavior. Sequence MINVALUE and MAXVALUE automatically adjust to new types bounds mirroring behavior of PostgreSQL.
CockroachDB could previously “leak” reported memory usage as accounted by the internal memory accounting system, the limit for which is configured with the --max-sql-memory flag, on long-running sessions that issue many (hundreds of thousands or more) transactions. This, in turn, could result in "root: memory budget exceeded" errors for other queries. This bug was present in versions v23.1.17 and v23.2.3 and is now fixed.
CockroachDB could previously incorrectly evaluate IN expressions that had INT2 or INT4 type on the left side and values outside of the range of the left side on the right side. The bug has been present since at least v21.1 and is now fixed.
Fixed a slow memory leak in the deprecated , which can accumulate when restarting or canceling many deprecated Pub/Sub changefeeds. The bug had been present since the deprecated Pub/Sub changefeed was introduced in a testing release of v22.1.

Contributors

This release includes 134 merged PRs by 36 authors.

v24.1.0-alpha.5

Release Date: April 1, 2024

Downloads

CockroachDB v24.1.0-alpha.5 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments.

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.0-alpha.5.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.5.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.0-alpha.5.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.5.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.0-alpha.5.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.5.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.0-alpha.5.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.5.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.0-alpha.5.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.0-alpha.5.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach-unstable:v24.1.0-alpha.5

Enterprise edition changes

now default to evenly distributing their work across all replicas, including followers, regardless of leaseholder placement. On upgrade to v24.1, running changefeed jobs will be restarted automatically as part of the upgrade process and will default to distributing work across replicas. To disable this behavior, set the changefeed.random_replica_selection.enabled to false. If disabled, changefeed planning reverts to its previous behavior for distributing work.
When is enabled, the output of the SHOW VIRTUAL CLUSTER... WITH REPLICATION STATUS command now displays replication lag.
When is enabled, the output of the SHOW VIRTUAL CLUSTER WITH REPLICATION STATUS to 1 command has changed:
- The output no longer displays replication_job_id or service_mode return fields.
- The data_state field has been renamed to status.
- The fields that are displayed are now ordered as follows: retained_time, replicated_time, replication_lag, cutover_time, status.
You can now run from an , without enabled, to a standby cluster with cluster virtualization enabled.

SQL language changes

You can now specify a condition for the EXIT and CONTINUE.
A can now invoke another stored procedure using a .
You can now use a statement within a to configure the transaction isolation level, timestamp, or priority, or to set the transaction to read-only. A SET TRANSACTION statement must immediately follow a COMMIT or ROLLBACK, with no other statements or block boundaries between them.
The new optimizer_use_virtual_computed_column_stats, when enabled, configures the to use on virtual computed columns.
An can now drop the IDENTITY constraint and related sequence using the following SQL statement:
ALTER TABLE {table_name} ALTER COLUMN {column_name} DROP IDENTITY [IF EXISTS];
IF EXISTS is optional, and skips the command if the column is not an identity column.
A shared lock that is acquired explicitly using or implicitly by a , can now be re-acquired with higher strength by either using a statement or by writing to the key.
now support OUT and INOUT parameter classes.
The EXIT and CONTINUE statements can now use labels to specify which loop or block is the target.

Operational changes

You can now enable asynchronous buffering of file-group using the buffering either by default or to an individual file-group. The buffering configuration option is incompatible with the buffered-writes configuration option. To try the buffering option, you must set buffered-writes: false. Cockroach Labs recommends setting max-staleness to 1s and flush-trigger-size to 256KiB.
A minimum concurrency is now enforced per store so that nodes with many stores do not spread workers too thin. This helps to avoid high scheduler latency across replicas on a store when load is imbalanced.
The new kv.split.estimated_stats and kv.split.total_bytes_estimates track the number of splits that produce statistic estimates and the total bytes of estimates produced.
The new storage.sstable.compression_algorithm configures the compression algorithm used when compressing sstable blocks.
The new kv.dist_sender.proxy.enabled, which is enabled by default, causes proxy requests to be routed through a follower replica when the leaseholder is unavailable.
The new startup flag --wal-failover allows you to explicitly set the path for WAL failover of a single-store node.
Cluster virtualization is now enabled using either of the new startup flags --virtualized or --virtualized-empty instead of the --config-profile flag.
The following metrics, which track the SQL statistics subsystem’s task to flush in-memory statistics to persisted storage, are now more consistent with other metrics used in the subsystem.
- sql.stats.flushes.successful: Number of times SQL statistics have been flushed successfully to persistent storage.
- sql.stats.flushes.failed: Number of attempted SQL statistics flushes that failed with errors.
- sql.stats.flush.latency: The latency of attempted SQL statistics flushes to persistent storage, including both successes and failures.
The following new track the number and outcome of proxy requests when kv.dist_sender.proxy.enabled is set to true:
- distsender.rpc.proxy.sent
- distsender.rpc.proxy.err
- distsender.rpc.proxy.forward.sent
- distsender.rpc.proxy.forward.err Cockroach Labs recommends monitoring and alerting on distsender.rpc.proxy.sent, because it indicates a possible network partition.
The provisioned-rate field of a node’s store specification can no longer be used to add constraints for the disk name or bandwidth. By default, bandwidth is constrained according to the kv.store.admission.provisioned_bandwidth. To override this setting for a specific node, the storage specification must contain provisioned-rate=bandwidth={bandwidth-bytes/s}.
Removal of the kv.rangefeed.scheduler.enabled, which was announced in , has been reverted, and the cluster setting is reinstated.

DB Console changes

In generated statement fingerprints in the DB Console , lists with only literals or placeholders or similar subexpressions are shortened to their first item followed by ” more ”.

Bug fixes

Fixed a bug introduced in v23.2 that could cause a routine to return incorrect results when the routine included:
1. At least one parameter.
2. An IF statement with one leak-proof branch and one branch with side effects.
Fixed a rare bug where a BACKUP command issued shortly after an could exclude data from an unrelated table from the backup.
Fixed a behavior where a memory exhaustion error during a schema change was treated as a permanent failure and reverted. Such schema changes are now retried instead of reverted.
Fixed a bug where the attname for a dropped column was not correctly padded with 8 . characters to be compatible with PostgreSQL.

Performance improvements

Splits no longer hold latches for time proportional to the range size while computing MVCC statistics. Instead, MVCC statistics are pre-computed before the critical section of the split. As a side effect, the resulting statistics are no longer 100% accurate because they may correctly distribute writes concurrent with the split. To mitigate against this potential inaccuracy, and to prevent the statistics from drifting after successive splits, the existing stored statistics are re-computed and corrected if needed during the non-critical section of the split.
The now generates more efficient query plans for some queries with OFFSET clauses.

Contributors

This release includes 157 merged PRs by 44 authors. We would like to thank the following contributors from the CockroachDB community:

Andrew Delph

v24.1.0-alpha.4

Release Date: March 25, 2024

Downloads

CockroachDB v24.1.0-alpha.4 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments.

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.0-alpha.4.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.4.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.0-alpha.4.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.4.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.0-alpha.4.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.4.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.0-alpha.4.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.4.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.0-alpha.4.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.0-alpha.4.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach-unstable:v24.1.0-alpha.4

Security updates

When , file-permissions are now applied literally, such that file-permissions: 644 will result in files with permissions matching 644 (instead of the previous behavior’s 640 ). Previously, CockroachDB’s umask (which is always at least 007 ) was being applied after the file-permissions field was used to create files, meaning the resulting permissions did not match those specified in the log configuration.

General changes

The following were added for observability of per-store disk events:
- storage.disk.read.count
- storage.disk.read.bytes
- storage.disk.read.time
- storage.disk.write.count
- storage.disk.write.bytes
- storage.disk.write.time
- storage.disk.io.time
- storage.disk.weightedio.time
- storage.disk.iopsinprogress The metrics match the definitions of the sys.host.disk.* system metrics.

Enterprise edition changes

server.controller.default_target_cluster can now be set to any virtual cluster name by default, including a virtual cluster yet to be created or have service started.
The isolation level now requires the cluster to have a valid enterprise license.
The new boolean changefeed option , when set to true, prevents the changefeed from filtering events even if CDC filtering is configured via the disable_changefeed_replication , sql.ttl.changefeed_replication.disabled , or the ttl_disable_changefeed_replication .

SQL language changes

Added support for the COMMIT and ROLLBACK statements.
now support enhanced sequence management through the and commands. This update facilitates the fine-tuning of identity column sequences.
It is now possible to use the STRICT option with and in order to enforce that a SQL statement within a routine returns exactly one row.
Added a plpgsql_use_strict_into, which causes PL/pgSQL and to require exactly one row from the SQL statement, similar to Oracle behavior.
Added a new failure_count INT NOT NULL column to crdb_internal.node_statement_statistics. It represents the number of recorded statement execution failures for the given statement, as a new component of the overall statistics.
The FORCE_INVERTED_INDEX hint causes the to prefer a query plan scan over any inverted index of the hinted table. An error is emitted if no such query plan can be generated.
The REPAIRCLUSTERMETADATA privilege has been aliased to REPAIRCLUSTER. Both names can be used interchangeably.

Operational changes

The new option environment variable will configure a multi-store CockroachDB node to fail over a store’s write-ahead log (WAL) to another store’s data directory. Failing over the write-ahead log may allow some operations against a store to continue completing, even if the underlying storage is temporarily unavailable. This feature is in .
The new storage.wal_failover.unhealthy_op_threshold allows configuring the latency threshold at which a WAL write is considered unhealthy.
Two new metrics track the status of the SQL Activity Update job, which pre-aggregates top K information within the SQL statistics subsytem and writes the results to system.statement_activity and system.transaction_activity:
- sql.stats.activity.updates.successful: Number of successful updates made by the SQL activity updater job.
- sql.stats.activity.update.latency: The latency of updates made by the SQL activity updater job. Includes failed update attempts.
Added a new counter metric, sql.stats.flush.done_signals.ignored, that tracks the number of times the SQL activity update job has ignored the signal that indicates that a flush has completed. This metric may indicate that the SQL activity update job is taking longer than expected to complete.
Added a new counter metric, sql.stats.activity.updates.failed, to measure the number of update attempts made by the SQL activity update job that failed with errors.
Added a new counter metric, sql.stats.flush.fingerprint.count, that tracks the number of unique statement and transaction fingerprints included in the SQL stats flush.
The /_status/stores endpoint now includes node_id, dir, and wal_failover_path fields to show the store’s node ID, data directory, and path to the configured WAL failover secondary, if configured.

Command-line changes

The new --go-gc-percent flag of the command controls the garbage collection target percentage of the Go runtime, mirroring the existing GOGC environment variable. A garbage collection is triggered when the ratio of freshly allocated data to live data remaining after the previous collection reaches this percentage. If left unspecified and if a Go soft memory limit is configured (i.e., not explicitly disabled via --max-go-memory or GOMEMLIMIT ), the garbage collection target percentage defaults to 300%. Setting the flag to a negative value disables the target percentage garbage collection heuristic, and only the soft memory limit heuristic triggers garbage collection. To monitor the impact of this change in the DB Console, look for an increase in Memory usage in the and an increase in Go total memory usage in the . This does not increase the risk of an out-of-memory exception (OOM), because the Go memory limit (controlled by the --max-go-memory flag or the GOMEMLIMIT environment variable) prevents Go from consuming too much memory.

DB Console changes

The now includes lease queue metrics.
The DB Console SQL Activity page has replaced the Failed? boolean column with a Failure Count column that shows the number of failed executions for the given statement fingerprint. In the SQL Activity table, the same statement fingeprint no longer appears in separate rows for failed executions and successful executions. Instead, they are combined into a single statement fingerprint.
The DB Console now displays an alert message when a license has expired or will expire in fewer than 15 days.

Bug fixes

Fixed a bug with that could lead to dangling function references in other schemas accessing any functions.
Fixed a bug where a of a backup that itself contained a table created by the RESTORE of a table with an in-progress would fail to restore all rows.
Fixed a bug where without any configured sequence options did not display the default values for identity attributes in information_schema.
Fixed a bug where a statement could fail if sequences existed and they did not support a privilege (e.g., BACKUP ).
Fixed a bug where an statement would generate event log entries for schema changes that were not executed.

Contributors

This release includes 153 merged PRs by 179 authors.

v24.1.0-alpha.3

Release Date: March 18, 2024

Downloads

CockroachDB v24.1.0-alpha.3 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments.

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.0-alpha.3.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.3.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.0-alpha.3.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.3.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.0-alpha.3.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.3.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.0-alpha.3.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.3.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.0-alpha.3.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.0-alpha.3.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach-unstable:v24.1.0-alpha.3

Enterprise edition changes

now accepts a --version=2 parameter. Version 2 keys activate a new encryption implementation with improved performance. This is expected to become the default in CockroachDB v24.2.

SQL language changes

Mutation statements such as and as well as locking statements such as are not allowed in read-only transactions or transactions. This fixes an oversight where CockroachDB was allowing mutation statements and locking statements in implicit single-statement transactions using AS OF SYSTEM TIME.
Added support for RETURN statements with no expression for routines with OUT parameters and routines with a VOID return type.

can now change columns to an identity column by using the syntax in one of the following:

ALTER TABLE t ALTER COLUMN c ADD GENERATED ALWAYS AS IDENTITY [( <opt_sequence_option_list> )]
ALTER TABLE t ALTER COLUMN c ADD GENERATED BY DEFAULT AS IDENTITY[( <opt_sequence_option_list> )]

Identity columns can have their identity type altered by using the syntax in one of the following statements:

ALTER TABLE t ALTER COLUMN c SET GENERATED ALWAYS
ALTER TABLE t ALTER COLUMN c SET GENERATED BY DEFAULT

Added support for the NULL statement.
is now behind the .
blocks can now be nested in a block that has an exception handler.

DB Console changes

Resolved an issue where clusters with multiple stores per node may list inaccurate region/node information in the page.
VIEW type tables will no longer display in the DB Console pages. Previously these would be listed with no information, only displaying errors.
Fixed an intermittent page crash in the tab.
Fixed a bug where the Rows written value was incorrectly showing the Rows read value on the page.

Bug fixes

Fixed a bug that occurred when using to drop and re-add a with the same name.
Fixed a bug in which it was possible to during an transaction.
Fixed a bug that caused a slow memory leak that could accumulate when opening many new connections. The bug was present in v22.2.9+ and v23.1+ versions.

Contributors

This release includes 90 merged PRs by 35 authors. We would like to thank the following contributors from the CockroachDB community:

Andrew Delph

v24.1.0-alpha.2

Release Date: March 11, 2024

Downloads

CockroachDB v24.1.0-alpha.2 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments.

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.0-alpha.2.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.2.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.0-alpha.2.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.2.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.0-alpha.2.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.2.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.0-alpha.2.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.2.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.0-alpha.2.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.0-alpha.2.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach-unstable:v24.1.0-alpha.2

Security updates

session cookie is now marked HttpOnly to prevent it from being read by any JavaScript code.
cookies are now marked Secure for the browser when the cluster is running in secure mode.

General changes

will now detect faulty or stalled and use other replicas instead, which can prevent them getting stuck in certain cases (e.g., with ). This behavior can be disabled via the kv.dist_sender.circuit_breaker.enabled.

Enterprise edition changes

Added a new . This role option can be set to a subject distinguished name in RFC 2253 or RFC 4514 format. If set, then during client certificate authentication, certs that do not match the configured distinguished name will be rejected.
support a new scheme azure-event-hub:// for Kafka data streaming to Azure event hubs. The sinkURL must include mandatory parameters shared_access_key_name and shared_access_key. By default and as required, the options tls_enabled=true, sasl_handshake=true, sasl_enabled=true, and sasl_mechanism=PLAIN are applied, as they are the only supported options. Other parameters such as topic_name and topic_prefix are also supported. An example URI is: azure-event-hub://myeventhubs.servicebus.windows.net:9093?shared_access_key_name=abc&shared_access_key=123.

SQL language changes

Added an option for node-level caching. All the sessions on the node can share the same cache, which can be concurrently accessed. The serial_normalization can now be set to the value sql_sequence_cached_node. If this value is set, the sql.defaults.serial_sequences_cache_size can be used to control the number of values to cache in a node, with a default of 256. The PER NODE CACHE sequence option (syntax is [ [ PER NODE ] CACHE # ] ) is now fully implemented and will allow nodes to cache sequence numbers. A cache size of 1 means there is no cache, and cache sizes of less than 1 are not valid.

Bug fixes

Fixed a bug that prevented the use of routines with complex variable names that require double quotes. This bug had existed since v23.2.
Fixed a bug that could cause creation of a syntactically invalid routine to return the wrong error. This bug had existed since v23.2.
Fixed a bug that could result in a syntax error if a routine was created with an escaped string constant in the routine body. This bug had existed since v23.2.
Fixed a bug where running a that targets a table with a user-defined type column and with the set to any value other than wrapped would cause a node panic due to a nil dereference.
Fixed a bug where running on certain backups would open a very large number of connections to the backup storage provider.
Previously, a user with the VIEWACTIVITYREDACTED could see constants inside of queries that originated from other in the output. This information is now properly redacted.
Previously, the and commands incorrectly required the user to have the VIEWACTIVITY or VIEWACTIVITYREDACTED . This is now fixed, as a user should always be able to view their own queries, even without this privilege.

Contributors

This release includes 1939 merged PRs by 109 authors.

v24.1.0-alpha.1

Release Date: March 7, 2024

Downloads

CockroachDB v24.1.0-alpha.1 is a testing release. Testing releases are intended for testing and experimentation only, and are not qualified for production environments and not eligible for support or uptime SLA commitments.

Experimental downloads are not qualified for production use and not eligible for support or uptime SLA commitments, whether they are for testing releases or production releases.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v24.1.0-alpha.1.linux-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.1.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v24.1.0-alpha.1.linux-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.1.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v24.1.0-alpha.1.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.1.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v24.1.0-alpha.1.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v24.1.0-alpha.1.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v24.1.0-alpha.1.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v24.1.0-alpha.1.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach-unstable:v24.1.0-alpha.1

Backward-incompatible changes

queries can no longer use a timestamp followed by a question mark to signify a future-time value. This was an undocumented syntax.

Enterprise edition changes

no longer removes a when modifying changefeed properties.
changefeed.balance_range_distribution.enable is now deprecated. Instead, use the new changefeed.default_range_distribution_strategy. changefeed.default_range_distribution_strategy='balanced_simple' has the same effect as setting changefeed.balance_range_distribution.enable=true. It does not require initial_scan='only', which was required by the old setting.
CDC queries now correctly handle the function.
The new syntax ALTER VIRTUAL CLUSTER virtual-cluster START REPLICATION OF virtual-cluster ON physical-cluster can now be used to reconfigure virtual clusters previously serving as sources for to become standbys to a promoted standby. This reverses the direction of replication while maximizing data reuse.
s now load range information that is used to avoid a spike in metadata lookups when backups begin.
Clusters created to run no longer automatically disable the and cluster settings. Users who started using physical cluster replication on v23.1 or v23.2 may wish to manually reset these settings.
Physical cluster replication is now always enabled, and the physical_replication.enabled cluster setting has been removed.

SQL language changes

can now be used to set the next scheduled execution of the backup schedule to the current time.
Fixed the update job to avoid conflicts on update, reduced the amount of data cached to just what the overview page requires, and fixed the correctess of the top queries.
Previously, user-defined composite types were not populated in two pg_catalog tables: pg_class (whose row entries pertain to the type) and pg_attribute (whose row entries pertain to the “columns” of the type). This PostgreSQL-incompatible behavior is now fixed by populating the tables with user-defined composite types. In addition, the typrelid column in the pg_type table has the proper oid for composite types.
The newly added jsonb_array_to_string_array no longer removes NULL objects. It now includes them in the resulting array.
Changed the display for RU estimates shown in from integer to float. This will prevent small estimates from being rounded to zero, which makes the estimate less confusing for cheap queries.
The information_schema._pg_char_octet_length is now supported, which improves compatibility with PostgreSQL.
The pg_encoding_max_length is now supported, which improves compatibility with PostgreSQL.
The information_schema._pg_datetime_precision is now supported, which improves compatibility with PostgreSQL.
The information_schema._pg_interval_type is now supported, which improves compatibility with PostgreSQL.
information_schema.user_defined_types is now populated with information about , and information_schema.attributes is now populated with information about the attributes of .
The will no longer generate a constrained scan that only uses filters from a constraint. This prevents cases where a constrained scan actually scans the entire table because the constraints aren’t selective.
Reads rolled back by savepoints are now refreshable, matching the PostgreSQL behavior and avoiding potential serializability violations.
Implemented the postgis ST_TileEnvelope .
Added support for a third argument in the array_position . If provided, it gives the index from which to begin searching in the array.
Added the bit_count for and types.
Added a pg_backend_pid column to crdb_internal.node_sessions and crdb_internal.cluster_sessions. This value corresponds to the numerical ID returned from pg_backend_pid.
Column type changes now require an explicit cast when automatic casting is not possible. This aligns with PostgreSQL’s behavior. Previously, certain type conversions, such as to , were allowed without an explicit cast.
Added a new , optimizer_merge_joins_enabled that, when true, instructs the to explore query plans with merge joins. The setting defaults to true.
CockroachDB now supports parsing queries like that only produce the row count and do not output any columns.
Added the metaphone , which converts a string to its Metaphone code.
The new EXPIRATION WINDOW option for allows the user to override the default producer job expiration window of 24 hours. For example, ALTER VIRTUAL CLUSTER appTenant SET REPLICATION EXPIRATION WINDOW ='100ms'. The producer job expiration window determines how long the producer job stays alive without a heartbeat from the consumer job.
The clause is now allowed with SELECT... FOR SHARE.
Added configurable for total TCP keep alive probes ( server.sql_tcp_keep_alive.count ) and TCP probe intervals ( server.sql_tcp_keep_alive.interval ) for SQL connections. Removed the COCKROACH_SQL_TCP_KEEP_ALIVE environment variable subsuming it.
Removed the sql.trace.session_eventlog.enabled cluster setting and the associated event log tracing. The information in these traces is still available in the by enabling --vmodule=conn_executor=2 with .
The array_agg can now support arrays as the input. Note that CockroachDB does not yet fully support nested arrays, and array_agg does not support nested arrays as inputs.
An execution statistic that measures “client time” is now included in plan.txt files of . Client time tracks how long the query execution was blocked on the client receiving the PGWire protocol messages. Note that when obtained via , client time does not make sense because in this variant the output rows are discarded and not communicated to the client.
Added the trace_id column to the response of the command.
Added support for the ENCODING option of COPY, as long as the encoding of 'utf8' is specified.
Added the SHOW VARIABLES FOR ROLE command, which allows the database administrator to easily view the default values for applied to a given user.
The sql.txn.read_committed_isolation.enabled is now true by default. This means that any syntax and settings that configure the isolation level will now cause the transaction to use that isolation level, rather than automatically upgrading the transaction to SERIALIZABLE.
Added a new , sql.stats.virtual_computed_columns.enabled, which when set enables collection of table statistics on .
Added the autocommit_before_ddl . When set to true, any schema change statement that is sent during an explicit transaction will cause the transaction to commit before executing the schema change.
is now enabled by default in the declarative schema changer.
now supports nested blocks, with the following limitations: variable shadowing is disallowed, and exception handlers cannot be used in a routine with nested blocks.
The sql.index_recommendation.drop_unused_duration is now public.
It is now possible to hint to the that it should plan a straight join by using the syntax ... INNER STRAIGHT JOIN.... If the hint is provided, the optimizer will now fix the join order as given in the query, even if it estimates that a different plan using join reordering would have a lower cost.
Add column goroutine_id to the response of the SHOW SESSIONS command.
Introduced a new , close_cursors_at_commit, which causes a cursor to remain open even after its calling transaction commits. Note that transaction rollback still closes any cursor created in that transaction.
Added the server.max_open_transactions_per_gateway . When set to a non-negative value, non- admin users cannot execute a query if the number of transactions open on the current gateway node is already at the configured limit.
Added the setseed . It sets the seed for the random generator used by the random built-in function.
OUT and INOUT parameter classes are now supported in .
Out-of-process SQL servers will now start exporting a new sql.aggregated_livebytes . This metric gets updated once every 60 seconds by default, and its update interval can be configured via the tenant_global_metrics_exporter_interval .
Added support for index hints with and statements. This allows INSERT... ON CONFLICT and UPSERT queries to use index hints in the same way they are already supported for and statements.
Added a new table storage parameter that can be used to disable changefeed replication for on a per-table basis.

Operational changes

The internal versions that are reported during have been renamed for clarity. For example, 23.2-8 is now named 23.2-upgrading-to-24.1-step-008.
Introduced a new cluster setting, server.jwt_authentication.jwks_auto_fetch.enabled, enabling automatic fetching of from an issuer’s remote endpoint. This prevents an administrator’s need to update the JWKS specified in server.jwt_authentication.jwks - whether manually or by custom script - when the identity provider’s keys rotate. That direct specification of JWKS remains the default, as the new cluster setting defaults to false.
Updated the error message logged in the case of stalled disks to use the appropriate term “disk stall”, matching the term used in metrics and dashboards. This was previously “file write stall”.
Introduced the changefeed.emitted_batch_sizes histogram metric that measures the batch sizes used when emitting data to . This metric supports .
Introduced metrics log_fluent_sink_conn_attempts, log_fluent_sink_write_attempts, and log_fluent_sink_write_errors to enable more precise tracking of connection and write operations when .
The sql.contention.record_serialization_conflicts.enabled is now on by default. This means any that are returned containing conflicting transaction information will be recorded by the contention registry.
Removed the kv.rangefeed.scheduler.enabled because the scheduler is now unconditionally enabled.
Removed the kv.rangefeed.catchup_scan_concurrency . Catchup scans are throttled via on a per-node basis.
Removed the cluster setting because the functionality is enabled by default.
The gossip status now includes information about the server’s high water timestamps for every other node it knows about in the gossip cluster.
Removed the cockroach_rangefeed_rpc_initial_window_size environment variable. The rangefeed connection now uses the same window size as other RPC connections.
for changes are now emitted to the OPS channel rather than the DEV channel.
The new environment variable cockroach_rpc_use_default_connection_class enables operators to switch back to the prior default behavior of sending most network/RPC workloads, except system traffic, through a single RPC/TCP connection, in case the environment does not tolerate multiple TCP connections. v24.1 defaults to using multiple connections, each dedicated to a particular types of traffic, specifically for or data. For more information, see additional release notes that reference this variable name.
In unredacted , the crdb_internal.transaction_contention_events table file has two new columns:
- waiting_stmt_query: the query of the waiting statement.
- blocking_txn_queries_unordered: the unordered list of the blocking transaction’s queries.
Transaction replay protection state is now passed between the outgoing and incoming for a range during a . This avoids cases where lease transfers can cause transactions to throw TransactionAbortedError(ABORT_REASON_NEW_LEASE_PREVENTS_TXN) errors.
CockroachDB will now automatically generate if there is an increase in CPU utilization. This can help inform investigations into possible issues.
Expanded the flag to include problem ranges. This flag still defaults to true.

Command-line changes

no longer include redundant hex_ columns for system table BYTES columns.
Added the --follower-read-percent flag, which determines the percent (0-100) of read operations that are follower reads, to the command.
The workload schemachange now writes a .otlp.ndjson.gz archive containing OTLP trace bundles for debugging purposes.
creates a tsdump.yaml file. The tsdump raw format automatically creates the YAML file in the default location /tmp/tsdump.yaml. Added a new flag --yaml that allows users to specify the path to create tsdump.yaml instead of using the default location. For example, cockroach debug tsdump --host <host>:<port> \ --format raw --yaml=/some_path/tsdump.yaml > /some_path/tsdump.gob.
Removed the cockroach connect command functionality. This was in CockroachDB v23.2.
Changed the SQL shell help URL to point to .
Added a new encode-uri utility to make generating connection strings for use with easier.

DB Console changes

Store initialization now logs progress every 10 seconds showing the current and total number of initialized.
Introduced a new Lease Preferences graph on the . The Lease Preferences graph will indicate when the current is not the first lease preference and where the current leaseholder satisfies no applied lease preference.
Updated the to always show the entire selected period, instead of just the period that had data.
Error messages displayed upon failure to load DB Console views now include information about the HTTP response status code, if one is present.
The Full Table/Index Scans chart in the now shows the non-negative derivative of the number of full scans tracked.
The now includes two additional graphs:
- Elastic CPU Utilization: displays the CPU utilization by elastic work, compared to the limit set for elastic work.
- Elastic CPU Exhausted Duration Per Second: displays the duration of CPU exhaustion by elastic work, in microseconds.
The txn.restarts.writetooold metric in the Transaction Restarts graph under the now includes all restarts previously categorized as txn.restarts.writetoooldmulti. The former is a now a superset of the latter. The txn.restarts.writetoooldmulti metric will be removed in a future release.

Bug fixes

Fixed a bug that could cause an internal error during distributed execution for an expression like CASE that requires its inputs to be the same type with all NULL inputs.
Fixed NULL input handling for the geospatial st_pointfromgeohash and st_geomfromgeohash.
The geospatial st_makeenvelope now correctly supports xmin or ymin to be greater than xmax or ymax, respectively.
Fixed a bug that could cause v23.1 nodes in clusters that had not to use excessive CPU retrying expected errors related to the incomplete upgrade state.
now does not fail on corrupted log files.
Placeholder arguments can now be used in statements.
Previously, when the session variable use_declarative_schema_changer was set to off, would delete any comments associated with the old primary index and old primary key constraint. This is inconsistent with the behavior of use_declarative_schema_changer=on, which is the default setting, where those comments would be carried over to the new primary index. Furthermore, the old behavior also caused a bug that could prevent command SHOW CREATE t from working.
Previously, when the session variable was set to use_declarative_schema_changer=off and there was an attempt to on a table that has unique secondary indexes on new primary key columns, the unique secondary index would still incorrectly have old primary key columns as its keySuffixColumn after the ALTER PRIMARY KEY. This was problematic because a subsequent dropping of the old primary key columns would unexpectedly drop those unique secondary indexes as well, even without CASCADE.
can now be used to set updates_cluster_last_backup_time_metric without providing an explicit value, matching the behavior of the option when specified during .
Previously, if a table had that stored certain columns ( col ) using the clause, followed by an to col, an incorrect secondary index would persist. The secondary index would continue to have the STORING clause, despite the column being part of the primary key and the fact that CockroachDB does not permit secondary indexes to store any primary key columns. Now, after the ALTER PRIMARY KEY, the STORING clause is dropped on those secondary indexes.
Fixed a bug that caused uploads to to fail because of the absence of an MD5 hash.
now preserves the name of the original primary index when the session variable is use_declarative_schema_changer=off.
Fixed a bug where the added to a table would cause the create_statement from SHOW CREATE t to not be executable and error with unique constraint cannot be NOT VALID.
Fixed a bug where an empty followed by non-empty incremental backups taken inside an application tenant might not allow a due to the use of an incorrect SQL codec.
Fixed a bug in the job that would cause it to skip expired rows if the primary key of the table included columns of the collated STRING or DECIMAL type.
Incorrectly labeled blocks now return an expected syntax error.
no longer returns an error if the connection already exists.
CockroachDB now correctly uses the histograms on columns of collated type. The bug has been present since before v22.1.
Improved an interaction during range that could cause RETRY_ASYNC_WRITE_FAILURE errors to be returned to clients.
Backfilling tables for or could get into a retry loop if data was deleted and those jobs took longer than the GC TTL.
that are part of a mis-replicated range will no longer get stuck on a rebalance operation that was falsely determined to be unsafe.
A memory leak within the insights system was found to occur when was disabled, while leaving sql.metrics.statement_details.enabled enabled. This patch fixes the memory leak by preventing the collection of further statement and transaction insights when sql.metrics.transaction_details.enabled is disabled.
Fixed a rare panic that could happen during a pg_dump import that contains a function that has a subquery in one of its arguments, like SELECT addgeometrycolumn(...). Now, attempting to import a pg_dump with such a function results in an expected error.
jobs could previously lead to growth in an internal system table resulting in slower job-system related queries.
Fixed an issue in CockroachDB where, if operating on a Linux system outside of a CPU cgroup, the system would repeatedly log the error unable to get CPU capacity at 10-second intervals.
Fixed a bug where casts of to simply truncated the decimal portion. These casts now match the PostgreSQL behavior of rounding to the nearest integer, and in cases of a value halfway between two integers, rounding to the nearest even number. This aligns with the “round half to even” rule or “bankers’ rounding”, offering greater overall precision across a group of such cast operations.
Fixed a bug where statements like ADD COLUMN j INT, ADD UNIQUE WITHOUT INDEX (j), which with unique constraints without creating associated indexes, would fail with an internal error.
Previously, from a table to a table could cause leaseholders to never move to the database’s primary region. This is now fixed.
Users with the privilege can now request statement bundles using crdb_internal.request_statement_bundle or through the DB Console page.
Fixed an internal error with a message like: LeafTxn... incompatible with locking request that occurs when performing an update under which cascades to a table with multiple other foreign keys.
Fixed a bug where could fail with an error non-nullable column <x> with no value! Index scanned.. when validating recreated .
Fixed a bug where a sequence name allocated by that conflicted with an existing type name would cause an error.
Fixed a bug where statements could fail with an “unexpected value” error if multiple COMMENT statements were running concurrently.
Previously, in certain cases, using virtual tables such as crdb_internal.system_jobs could result in the internal error attempting to append refresh spans after the tracked timestamp has moved forward. This is now fixed. The bug was introduced in CockroachDB v23.1.
Fixed a bug where operations on the crdb_internal.leases table could cause a node to become unavailable due to a deadlock in the leasing subsystem.
If an individual ‘s circuit breaker had tripped but the range was otherwise functional, for example, because the replica was partially partitioned away from the , it was possible for a gateway to persistently error when contacting this replica instead of retrying against a functional leaseholder elsewhere. The will now retry such errors against other replicas once.
Fixed a bug in changefeed where the HTTP request body may not be initialized on retries, resulting in the error http: ContentLength=... with Body length 0.
Fixed a bug where rangefeed resolved timestamps could get stuck, continually emitting the log message pushing old intents failed: range barrier failed, range split, typically following a .
Fixed a condition where some files were not closed when inspecting backup metadata during BACKUP and RESTORE. Epic: none.
Fixed a bug where some backup metadata files opened during were not closed.
Fixed a bug that caused internal errors when executing an statement where the query involved sorting by columns not explicitly included in the output, due to hidden columns in the input expression.
Fixed a bug where a warning about the need to refresh data would remain displayed on the Active Executions view of the and pages despite enabling Auto Refresh.

Performance improvements

for multi-region tables now default to prioritizing replicas in the same , when available, with node latency as a tie breaker. Previously, latency was the primary criteria. This can improve the performance and predictability of follower reads.
During node startup, stores are now loaded in parallel by default, reducing start times for nodes with many stores.
Improved the efficiency and performance of .
Rangefeeds, the infrastructure used for , now use a more efficient engine that reduces the number of goroutines and the associated Go scheduler pressure and latency.
Rangefeeds, the infrastructure used for , now use a more efficient multiplexing protocol.
The now generates constrained scans on indexes containing boolean, computed expressions.
A separate RPC connection class is now used for most traffic. This improves isolation and reduces interference with foreground SQL traffic, which reduces chances of head-of-line blocking caused by unrelated traffic under high-load conditions. The new COCKROACH_RAFT_USE_DEFAULT_CONNECTION_CLASS environment variable can be set to use the default connection class instead (the previous behavior).
Rangefeed traffic (typically for ) is now separated into its own RPC connection class. This improves isolation and reduces interference with the foreground SQL traffic, which reduces chances of head-of-line blocking caused by unrelated traffic. The new COCKROACH_RANGEFEED_USE_DEFAULT_CONNECTION_CLASS environment variable can be set to use the default connection class, the previous default choice for rangefeeds.
The initial scan traffic for , which can be significant, now uses a different RPC/TCP connection than the foreground SQL/KV traffic. This reduces interference between workloads, and reduces chances of head-of-line blocking issues.
now supports specifying different client IDs for each changefeed, enabling users to define distinct Kafka quota configurations for each. For example, CREATE CHANGEFEED FOR... WITH kafka_sink_config='{"ClientID": "clientID1"}'
Added the changefeed.kafka_throttling_hist_nanos metric, enhancing visibility into throttling times when CockroachDB operations exceed Kafka’s quota limits.
The now generates more efficient query plans for queries with comparisons of and columns, for example, timestamp_col - '1 day'::INTERVAL > now().
Statements from internal executors (use of SQL queries by the cluster itself) now correctly display when filtering by application name $ internal on the Statements page in . Such statements are hidden when $ internal is not specified.

Contributors

This release includes 1851 merged PRs by 108 authors. We would like to thank the following contributors from the CockroachDB community:

Andrew Delph (first-time contributor)
ChanYe East (first-time contributor)
Charles (first-time contributor)
Eric.Yang
Harshit Vishwakarma (first-time contributor)
HighPon
Jasmine Sun (first-time contributor)
Joshua Hildred (first-time contributor)
Kevin Mingtarja (first-time contributor)
Luis Pessoa (first-time contributor)
Nikolai Vladimirov (first-time contributor)
chavacava (first-time contributor)
craig
cty123
da-ket (first-time contributor)
lyang24 (first-time contributor)
zach.graves (first-time contributor)
zyf123123 (first-time contributor)

v24.2 Release notes v23.2 Release notes

​v24.1.31

​Downloads

​Docker image

​Security updates

​v24.1.30

​Downloads

​Docker image

​Bug fixes

​Build changes

​v24.1.29

​Downloads

​Docker image

​Bug fixes

​v24.1.28

​Downloads

​Docker image

​Bug fixes

​v24.1.27

​Downloads

​Docker image

​Bug fixes

​v24.1.26

​Downloads

​Docker image

​Bug fixes

​v24.1.25

​Downloads

​Docker image

​Bug fixes

​v24.1.24

​Downloads

​Docker image

​SQL language changes

​Operational changes

​Bug fixes

​Performance improvements

​v24.1.23

​Downloads

​Docker image

​General changes

​Bug fixes

​Build changes

​Miscellaneous

​v24.1.22

​Downloads

​Docker image

​Bug fixes

​v24.1.21

​Downloads

​Docker image

​Bug fixes

​v24.1.20

​Downloads

​Docker image

​Bug fixes

​Performance improvements

​v24.1.19

​Downloads

​Docker image

​Operational changes

​DB Console changes

​Bug fixes

​v24.1.18

​Downloads

​Docker image

​SQL language changes

​Bug fixes

​v24.1.17

​Downloads

​Docker image

​Bug fixes

​v24.1.16

​Downloads

​Docker image

​Bug fixes

​v24.1.15

​Downloads

​Docker image

​Operational changes

​Bug fixes

v24.1.31

Downloads

Docker image

Security updates

v24.1.30

Downloads

Docker image

Bug fixes

Build changes

v24.1.29

Downloads

Docker image

Bug fixes

v24.1.28

Downloads

Docker image

Bug fixes

v24.1.27

Downloads

Docker image

Bug fixes

v24.1.26

Downloads

Docker image

Bug fixes

v24.1.25

Downloads

Docker image

Bug fixes

v24.1.24

Downloads

Docker image

SQL language changes

Operational changes

Bug fixes

Performance improvements

v24.1.23

Downloads

Docker image

General changes

Bug fixes

Build changes

Miscellaneous

v24.1.22

Downloads

Docker image

Bug fixes

v24.1.21

Downloads

Docker image

Bug fixes

v24.1.20

Downloads

Docker image

Bug fixes

Performance improvements

v24.1.19

Downloads

Docker image

Operational changes

DB Console changes

Bug fixes

v24.1.18

Downloads

Docker image

SQL language changes

Bug fixes

v24.1.17

Downloads

Docker image

Bug fixes

v24.1.16

Downloads

Docker image

Bug fixes

v24.1.15

Downloads

Docker image

Operational changes

Bug fixes