What's New in v23.2 - CockroachDB

CockroachDB v23.2 is a required . This page contains a complete list of features and changes in v23.2.

For a summary of the most significant changes in v23.2, 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:

v23.2.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-v23.2.31.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.31.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.31.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.31.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.31.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.31.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.31.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.31.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.31.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.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:v23.2.31

v23.2.30

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-v23.2.30.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.30.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.30.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.30.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.30.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.30.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.30.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.30.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.30.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.30.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.30

v23.2.29

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-v23.2.29.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.29.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.29.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.29.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.29.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.29.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.29.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.29.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.29.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.29.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.29

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.

v23.2.28

Release Date: September 4, 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-v23.2.28.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.28.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.28.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.28.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.28.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.28.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.28.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.28.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.28.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.28.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.28

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.

v23.2.27

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-v23.2.27.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.27.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.27.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.27.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.27.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.27.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.27.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.27.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.27.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.27.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.27

Operational changes

The goschedstats.always_use_short_sample_period.enabled cluster setting should be set to true for any serious production cluster; this will prevent unnecessary queuing in admission control CPU queues.

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.

Performance improvements

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

v23.2.26

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-v23.2.26.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.26.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.26.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.26.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.26.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.26.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.26.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.26.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.26.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.26.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.26

Bug fixes

Fixed a bug where using values for the cluster setting changefeed.aggregator.flush_jitter and the changefeed option min_checkpoint_frequency resulting in changefeed.aggregator.flush_jitter * min_checkpoint_frequency < 1 would cause a panic. Jitter will now be disabled in this case.
Improved the performance of SHOW CREATE TABLE on multi-region databases with a large numbers of objects.
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 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.

v23.2.25

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-v23.2.25.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.25.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.25.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.25.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.25.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.25.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.25.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.25.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.25.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.25.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.25

SQL language changes

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 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 that caused changefeeds to fail on startup when scanning a single key.
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 that could leave behind a dangling reference to a dropped role if that role had default privileges granted to itself. The bug was caused by defining privileges such as: ALTER DEFAULT PRIVILEGES FOR ROLE self_referencing_role GRANT INSERT ON TABLES TO self_referencing_role.
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.

v23.2.24

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-v23.2.24.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.24.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.24.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.24.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.24.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.24.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.24.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.24.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.24.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.24.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.24

Bug fixes

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

v23.2.23

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-v23.2.23.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.23.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.23.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.23.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.23.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.23.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.23.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.23.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.23.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.23.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.23

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.

v23.2.22

Release Date: April 2, 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-v23.2.22.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.22.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.22.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.22.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.22.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.22.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.22.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.22.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.22.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.22.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.22

General changes

The protected timestamp (PTS) 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.

Bug fixes

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 that used the primary key column as the predicate expression.
Fixed a rare bug in which a query could fail with the error could not find computed column expression for column in table while dropping a virtual computed column from a table. This bug was introduced in v23.2.4.
Fixed a bug that could cause nil pointer dereference errors when executing statements with user-defined functions (UDFs). The error could also occur when executing statements with some built-in functions, like obj_description.

Miscellaneous

When configuring the sql.ttl.default_delete_rate_limit cluster setting, a notice is displayed informing the user that the TTL rate limit is per leaseholder per table with a link to the docs.

v23.2.21

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-v23.2.21.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.21.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.21.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.21.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.21.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.21.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.21.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.21.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.21.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.21.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.21

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.

Bug fixes

Fixed a bug where under rare circumstances draining a node could fail with 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 has existed since v23.1.
Fixed a bounded memory leak that could previously occur when evaluating some memory-intensive queries via the vectorized engine. The leak has been present since v20.2.
Previously, in changefeeds using CDC queries and the Parquet format, the output would include duplicate columns when it contained a user-defined primary key. Now, the columns are de-duplicated in Parquet changefeed messages.

v23.2.20

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-v23.2.20.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.20.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.20.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.20.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.20.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.20.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.20.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.20.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.20.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.20.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.20

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.

Operational changes

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

Bug fixes

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 bounded memory leak that could occur 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 leak had been present since before v19.2.
Fixed a bug where changefeeds using CDC queries could have duplicate columns in the Parquet output.
Fixed a bug that prevented the CREATE statement for a routine from being included in a statement bundle when the routine was created on a schema other than public. The bug had existed since v23.1.

v23.2.19

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-v23.2.19.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.19.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.19.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.19.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.19.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.19.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.19.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.19.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.19.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.19.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.19

Security updates

The cluster setting server.jwt_authentication.issuers now takes the issuers configuration value from the URI. This can be set to one of the following values:
1. Simple string that can be parsed as a valid issuer URL. For example: 'https://accounts.google.com'.
2. String that can be parsed as a valid JSON array of issuer URLs list. For example: ['example.com/adfs','https://accounts.google.com'].
3. String that can be parsed as valid JSON and deserialized into a map of issuer URLs to corresponding JWKS URIs. In this case, the JWKS URI present in the issuer’s well-known endpoint will be overridden. For example: '{"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, the JWKS URI is directly used to get the key set. In all other cases when JWKSAutoFetchEnabled is set, the JWKS URI is obtained first from the issuer’s well-known endpoint and then this endpoint is used.

General changes

In order to improve the granularity of changefeed pipeline metrics, the changefeed metrics changefeed.admit_latency and changefeed.commit_latency now have histogram buckets from 5ms to 60m (previously 500ms to 5m ). The changefeed metrics changefeed.parallel_io_queue_nanos, changefeed.parallel_io_result_queue_nanos, changefeed.sink_batch_hist_nanos, changefeed.flush_hist_nanos, and changefeed.kafka_throttling_hist_nanos have histogram buckets from 5ms to 10m (previously 500ms to 5m ).
Added support for multiple seed brokers in the new Kafka sink.
Added a 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.

SQL language changes

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

Operational changes

Telemetry delivery is now considered successful even in cases where we experience a network timeout. This will prevent throttling in cases outside an operator’s control.
When a schema change job completes, 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

CREATE SCHEMA now returns the correct error if the schema name is missing.
Fixed an issue where corrupted table statistics could cause the CockroachDB process to crash.
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.
CockroachDB now better respects 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 start-single-node. Now, cluster restarts correctly disable licensing.
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 could cause an internal error if a table with an implicit ( rowid ) primary key was locked from within a subquery, for example, 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.
CLOSE CURSOR statements are now allowed in read-only transactions, similar to PostgreSQL. The bug has been present since at least v23.1.
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 enabled.
A new column of type JSON or JSONB that has a UNIQUE constraint will now be blocked from being added to a table if the cluster has not yet finalized the upgrade to v23.2.

v23.2.18

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-v23.2.18.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.18.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.18.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.18.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.18.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.18.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.18.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.18.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.18.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.18.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.18

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.

v23.2.17

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-v23.2.17.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.17.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.17.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.17.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.17.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.17.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.17.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.17.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.17.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.17.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.17

Security updates

All cluster settings that accept strings are now fully redacted when transmitted as part of Cockroach Labs’ diagnostics telemetry. The payload includes a record of modified cluster settings and their values when they are not strings. If you previously applied the mitigations in Technical Advisory 133479, 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 setting values.

General changes

COCKROACH_SKIP_ENABLING_DIAGNOSTIC_REPORTING is no longer mentioned in the cockroach demo command.

Enterprise edition changes

Added system.users to the list of system tables that changefeeds protect with protected timestamps (PTS). This table is required for CDC queries.

Operational changes

Added a new cluster setting ui.database_locality_metadata.enabled, which allows operators to disable loading extended database and table region information in the DB Console’s Databases and Table Details pages. This information can cause significant CPU load on large clusters with many ranges. Versions of this page from v24.3 onwards do not have this problem. If you require this data, you can use the SHOW RANGES FROM {DATABASE| TABLE} query via SQL to compute on-demand.

Bug fixes

Previously, CockroachDB could encounter an internal error of the form interface conversion: coldata.Column is in an edge case. This is now fixed. The bug was present in versions v22.2.13 and later, v23.1.9 and later, and v23.2 and later.
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.
Fixed an unhandled error that could occur when using REVOKE... ON SEQUENCE... FROM user on an object that was not a sequence.
Addressed a panic that could occur inside CREATE TABLE AS that occurred if sequence builtin expressions had invalid function overloads.
String constants can now be compared against collated strings.
Previously, when executing queries with index or lookup joins when the ordering needed to be maintained, CockroachDB in some cases could get into a pathological state which would lead to increased query latency, possibly by several orders of magnitude. This bug was introduced in v22.2 and is now fixed.
Addressed a bug with DROP CASCADE that 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.
An error message is no longer returned when a non-admin user runs DROP ROLE IF EXISTS on a user that does not exist.
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 (e.g., 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 like 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.

Performance improvements

CockroachDB now avoids loading unnecessary file blocks shortly after a rebalance in a rare case.
Reduced the write-amplification impact of rebalances by splitting snapshot sstable files into smaller ones before ingesting them into Pebble.

v23.2.16

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-v23.2.16.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.16.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.16.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.16.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.16.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.16.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.16.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.16.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.16.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.16.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.16

General changes

Changed the license cockroach is distributed under to the new CockroachDB Software License (CSL).
The cluster setting diagnostics.reporting.enabled is now ignored if the cluster has a Enterprise Trial or Enterprise Free license, or if the reporting job is unable to load any license at all.
Added the sink error metric ( changefeed.sink_errors ) and expanded the reporting of the internal retries metric ( changefeed.internal_retry_message_count ) to all changefeed sinks that perform internal retries.
Allowed access to DB console APIs via JWT, which can be supplied as a Bearer token in the Authorization header.

DB Console changes

DB Console will reflect any throttling behavior from the cluster due to an expired license or missing telemetry data. Enterprise licenses are not affected.
Due to the inaccuracy of the Range Count column on the Databases page, and the cost incurred to fetch the correct range count for every database in a cluster, this data will no longer be visible. This data is still available via a SHOW RANGES query.

Bug fixes

Fixed an error that could happen if an aggregate function was used as the value in a SET command.
Added automated clean-up/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 bug that caused incorrect evaluation of CASE, COALESCE, and IF expressions with branches producing fixed-width string-like types, such as CHAR. In addition, the BPCHAR type has been fixed so that it no longer incorrectly imposes a length limit of 1.
Fixed a bug that could lead to incorrect results in rare cases. The bug requires a JOIN between two tables, with an equality between columns with equivalent, but not identical types (e.g., OID and REGCLASS ). In addition, the JOIN must lookup an index that includes a computed column that references one of the equivalent columns. This bug has existed since before v23.1.
Fixed a bug that could lead to incorrect results in rare cases. The bug requires a lookup join into a table with a computed index column, where the computed column expression is composite sensitive. A composite sensitive expression can compare differently if supplied non-identical, but equivalent input values (e.g. 2.0::DECIMAL vs 2.00::DECIMAL ). This bug has existed since before v23.1.
Fixed a bug where a span stats request on a mixed-version cluster resulted in an NPE.
The franz-go library has been updated to fix a potential deadlock on changefeed restarts.
Fixed an issue where changefeeds would fail to update protected timestamp records in the face of retryable errors.
Fixed a bug that could result in changefeeds using CDC queries failing due to a system table being garbage collected.
Fixed a rare bug in which an update of a primary key column that is also the only column in a separate column family can sometimes fail to update the primary index. This bug has existed since v22.2. Requirements to hit the bug are:
1. A table with multiple column families.
2. A column family containing a single primary key column.
3. That column family is not the first column family.
4. That column family existed before its column was in the primary key.
5. That column must be of type FLOAT4/8, DECIMAL, JSON, collated string type, or array.
6. An update that changes that column from a composite value to a non-composite value.
The proretset column of the pg_catalog.pg_proc table is now properly set to true for set-returning builtin functions.
Fixed a bug in the query optimizer that could cause CockroachDB nodes to crash in rare cases. The bug could occur when a query contains a filter in the form col IN (elem0, elem1,..., elemN) only when N is very large, e.g., 1.6+ million, and when col exists in a hash-sharded index or, exists in a table with an indexed, computed column dependent on col.
Users with the admin role can now run ALTER DEFAULT PRIVILEGES FOR target_role... on any target_role. Previously, this could result in a privilege error, which is incorrect as admins are allowed to perform any operation.
REASSIGN OWNED BY will now transfer ownership of the public schema. Previously, it would always skip over the public schema even if it was owned by the target role.
Added a timer for inner changefeed sink client flushes. Fixed a bug where timers were not correctly registered with the metric system.
Fixed an error that could be caused by using an AS OF SYSTEM TIME expression that references a user-defined (or unknown) type name. These kinds of expressions are invalid, but previously the error was not handled properly. This will now return the correct error message.
Fixed a bug where backup schedules could advance a protected timestamp too early, which caused incremental backups to fail.

Performance improvements

Performance has been improved during periodic polling of table history when the schema_locked table storage parameter is not enabled.
Reduced the write-amplification impact of rebalances by splitting snapshot SSTable files into smaller ones before ingesting them into Pebble.

v23.2.15

Release Date: November 15, 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-v23.2.15.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.15.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.15.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.15.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.15.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.15.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.15.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.15.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.15.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.15.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.15

Performance improvements

Reduced the write-amplification impact of rebalances by splitting snapshot sstable files before ingesting them into Pebble.

v23.2.14

Release Date: October 31, 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-v23.2.14.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.14.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.14.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.14.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.14.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.14.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.14.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.14.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.14.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.14.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.14

General changes

Added internal client name options to distinguish backup data transfer bytes from those of other clients, such as changefeeds, for updated CockroachDB Cloud .

v23.2.13

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-v23.2.13.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.13.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.13.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.13.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.13.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.13.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.13.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.13.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.13.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.13.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.13

Enterprise edition changes

The description for the changefeed.sink_io_workers now lists all that support the setting.
Network metrics have been added for the following :
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 child metrics are enabled, 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.
The new changefeed.total_ranges allows observation of the number of ranges that are watched by a changefeed aggregator. It uses the same polling interval as changefeed.lagging_ranges, which is controlled by the changefeed option lagging_ranges_polling_interval.
The following groups of and have been renamed to include the buffer they are associated with. The previous metrics are still maintained for backward compatibility.
- changefeed.buffer_entries.*
- changefeed.buffer_entries_mem.*
- changefeed.buffer_pushback_nanos.*
Added timers and corresponding [metrics](https://www.cockroachlabs.com/docs/v24.2/metrics.html for key parts of the pipeline to help debug issues with feeds. The changefeed.stage.{stage}.latency metrics now emit latency histograms for each stage. The metrics respect the changefeed scope label to debug a specific feed.

Operational changes

The new ranges.decommissioning shows the number of ranges with a replica on a .
The following new show the number of RPC TCP connections established to remote nodes:
- rpc.connection.connected: the number of gRPC TCP level connections established to remote nodes.
- rpc.client.bytes.egress: the number of TCP bytes sent over gRPC on connections initiated by the cluster.
- rpc.client.bytes.ingress: the number of TCP bytes received over gRPC on connections initiated by the cluster.
Added a new configuration parameter, server.cidr_mapping_url, which maps IPv4 CIDR blocks to arbitrary tag names.
The sql.bytesin and sql.bytesout are now aggregate metrics if child metrics are enabled.
The following new track the number of bytes sent by an individual to each sink:
- changefeed.network.bytes_in
- changefeed.network.bytes_out
You can now set the log format for the STDERR changefeed sink using the format field in the stderr sink section of the configuration.

DB Console changes

The now shows a notification if the cluster has no Enterprise license set. Refer to upcoming license changes for more information.

Bug fixes

Fixed a bug where the command SHOW CLUSTER SETTING FOR VIRTUAL CLUSTER would erroneously return NULL for some settings.
Fixed a bug where a node could fail to start with the error could not insert session...: unexpected value if an ambiguous result error occurred while inserting data into the sqlliveness table.
Fixed a bug that could prevent due to the upgrade pre-condition for repairing descriptor corruption.
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 failing to heartbeat its node liveness record.
Fixed a bug that could result in the erroneous log message expiration of liveness record... is not greater than expiration of the previous lease... after liveness heartbeat.
Fixed a bug where queries that are not initiated within a SQL session could fail to respect a statement timeout, including , queries issued by the that perform introspection, and the .
Fixed a bug where a connection could be incorrectly dropped if the client was attempting to change a schema at the same time that the same schema’s objects were being dropped.
Fixed a bug that could cause the following error to be logged when executing a query under isolation if it involved a table with NOT NULL virtual columns: internal error: Non-nullable column....
Fixed a potential memory leak in that use a cloud storage sink. The memory leak could occur if both of the changefeed.fast_gzip.enabled and changefeed.cloudstorage.async_flush.enabled were true and if the changefeed received an error while attempting to write to the sink.
Fixed a bug introduced in v23.2.6, where forecasting could predict a result of zero rows for a downward-trending statistic when sql.stats.forecasts.max_decrease is false. The setting is now enabled (set to 1/3 by default).
Fixed a bug introduced in v23.1 that can cause incorrect results in the following scenario:
1. The query contains a correlated subquery.
2. The correlated subquery has a GroupBy or DistinctOn operator with an outer-column reference in its input.
3. The correlated subquery is in the input of a SELECT or JOIN clause that has a filter that sets the outer-column reference equal to an inner column that is in the input of the grouping operator.
4. The set of grouping columns does not include the replacement column explicitly.
Fixed a bug where were not considered when implicit authentication was used.
Fixed a bug that could prevent a from resuming from a prolonged paused state.

v23.2.12

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-v23.2.12.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.12.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.12.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.12.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.12.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.12.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.12.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.12.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.12.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.12.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.12

Enterprise edition changes

Added a changefeed.protect_timestamp.lag metric, which controls how much the changefeed should lag behind the . A changefeed now only updates its PTS if changefeed.protect_timestamp.lag has passed between the last PTS and the changefeed high-water mark. - , , and no longer expose user sensitive information like client_key.

SQL language changes

The plan_cache_mode=force_generic_plan can now be used to force prepared statements to use a query plan that is once and reused in future executions without re-optimization, as long as the plan does not become stale due to or a collection of new . The setting takes effect during commands. now 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 plan_cache_mode=auto can now be used to instruct the to automatically determine whether to use “custom” or “generic” query plans for the execution of a prepared statement. Custom query plans are optimized on every execution, while generic plans are optimized 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 logging events that report connection breakage during . Previously, these logs existed but were unstructured. These logs appear in the OPS . There are two new events:
- The node_shutdown_connection_timeout event is logged after the timeout defined by the transpires, if there are still open SQL connections.
- The node_shutdown_transaction_timeout event is logged after the timeout defined by the , if there are still open on those SQL connections.
Added the ranges.decommissioning metric, representing the number of which have a on a .
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 we initiated.
- rpc.client.bytes.ingress is the number of TCP bytes received via gRPC on connections we initiated.
Added a new configuration parameter server.cidr_mapping_url, which maps IPv4 CIDR blocks to arbitrary tag names.
Modified metrics sql.bytesin and sql.bytesout to be aggregation metrics If the cluster setting is enabled.
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 cluster setting is enabled, the metric will have a kafka label.
- . If the cluster setting is enabled, the metric will have a webhook label.
- . If the cluster setting is enabled, the metric will have a pubsub label.
- . If the cluster setting is enabled, the metric will have a sql label.

DB Console changes

The time-series graphs now have hover behavior that focuses on individual lines and shows values under the mouse pointer.
Users with the can download from .
The now displays an alert message when the or if there are fewer than 15 days left before the license expires.
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 where declarative and legacy were incorrectly allowed to be executed 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 type, e.g., CREATE INDEX ON t ((col::an_enum)).
input parameters can no longer have the VOID type.
Internally issued queries that are not initiated within a no longer respect a statement timeout. This includes: , queries issued by the that perform introspection, and the Cloud .
Fixed a bug where the schema_locked did not prevent a table from being referenced by a .
Users with the can now request, view, and cancel in the .
Fixed a bug where a could lead to a panic with the message side-transport update saw closed timestamp regression. The bug could occur when a node was overloaded and failing to .
The expiration of liveness record... is not greater than expiration of the previous lease... after liveness heartbeat is no longer generated.
Fixed a bug where the require_explicit_primary_keys would prevent all statements from working.
Fixed a slow-building memory leak when using .
Fixed a potential memory leak in . 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.

v23.2.11

Release Date: September 16, 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-v23.2.11.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.11.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.11.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.11.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.11.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.11.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.11.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.11.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.11.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.11.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.11

Bug fixes

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 where a could lead to a side-transport update saw closed timestamp regression panic. The bug could occur when a node was and failing to heartbeat its record.
Resolved a concerning message: expiration of liveness record... is not greater than expiration of the previous lease... after liveness heartbeat. This message is no longer possible.

v23.2.10

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-v23.2.10.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.10.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.10.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.10.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.10.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.10.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.10.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.10.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.10.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.10.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.10

Security updates

URLs in the following SQL statements are now sanitized of any secrets, such as keys or passwords, before being written to :

Enterprise edition changes

Added a new utilizing the franz-go library and our own batching_sink behind a ( changefeed.new_kafka_sink_enabled, disabled by default).
The v2 Kafka and Google Cloud Pub/Sub now display notices indicating the topics they will emit to.

SQL language changes

Added the . The default value is true, which results in behavior that matches the existing behavior of CockroachDB. When set to false, then the GRANT OPTION is not implcitly given to the owner of an object. The object owner still implicitly has all privileges on the object, just not the ability to grant them to other users.
Fixed a bug where the DISCARD statement was disallowed when the session setting was set to on.

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 causing gateway nodes to crash while executing statements in tables. This bug had been present since v23.2.
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 comments, e.g., . 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 SQL session. This bug had been present since v23.1.
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 overly eager syntax validation, which did not allow the DESCENDING clause for non-terminal columns of an . Only the last column of an inverted index should be prevented from being DESCENDING, and 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.
Fixed small memory leaks that would occur during .
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; now there will be an error message.
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 were introduced in v22.2.
Fixed a bug where a hash-sharded constraint could not be created if it referred to columns that had a backslash in the name.
Fixed a bug where TYPEDESC SCHEMA CHANGE jobs could end up retrying forever if the descriptor targeted by them was already dropped.
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

Contributors

This release includes 80 merged PRs by 28 authors.

v23.2.9

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-v23.2.9.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.9.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.9.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.9.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.9.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.9.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.9.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.9.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.9.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.9.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.9

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.
Some debugging-only information about physical plans is no longer collected in the system.job_info table for , because it has the potential to grow very large.
For the , TCL 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 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 where a or command could leave references behind inside types, which could prevent subsequent commands from working.
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 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 occur either directly from an statement or indirectly from an or statement, which implicitly modifies the crdb_internal_region UDT. This bug had existed since UDTs were introduced in v20.2.
Fixed a bug in which constant LIKE 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 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 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 v22.1.
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 bug when a database with a .
Fixed a bug when inputting public role as user name for , such as has_database_privilege and has_schema_privilege.
Fixed a bug where the could crash if range information is 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.
In the , events now display correctly even when no are included in the ALTER ROLE statement.
Fixed a bug where with could hit undefined column errors on .

Performance improvements

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 write hotspot that can slow down foreground traffic.

Contributors

This release includes 100 merged PRs by 33 authors.

v23.2.8

Release Date: July 15, 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-v23.2.8.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.8.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.8.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.8.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.8.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.8.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.8.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.8.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.8.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.8.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.8

Performance improvements

Updated the with a small performance win for very large clusters.
Updated the to avoid unnecessary mutex contention.,

Bug fixes

Fixed a bug where the disallow_full_table_scans was not working for tables with .

Contributors

This release includes 5 merged PRs by 4 authors.

v23.2.7

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-v23.2.7.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.7.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.7.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.7.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.7.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.7.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.7.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.7.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.7.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.7.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.7

Enterprise edition changes

can use the bulk oracle for planning, which distributes work evenly across all in the locality filter, including followers if enabled. Set the changefeed.random_replica_selection.enabled to true to enable this planning behavior. To use the previous bin-packing oracle, set the cluster setting changefeed.random_replica_selection.enabled to false.
no longer removes the when modifying changefeed properties.

SQL language changes

Precision is no longer limited when encoding geo data types to JSON.
When the new optimizer_push_offset_into_index_join is enabled, the attempts to produce more efficient query plans by attempting to push offset expressions into index join expressions to produce more efficient query plans.

General changes

CockroachDB v23.2.7 and subsequent v23.2 releases are eligible for .

Operational changes

Improved metrics related to reporting for volumes that dynamically change their size over time.

Security changes

Improved the automated cleanup when dropping roles inside descriptors.

Bug fixes

Fixed a bug where a range with a replication factor of 1 to be scaled up to a replication factor of 2.
Fixed a bug that could cause leases to thrash between nodes when perturbed with a replication factor of 1.
Fixed a bug where, when the ttl_row_stats_poll_interval storage parameter is non-zero, the job to update row statistics for a table with enabled could be blocked from completing by the queries issued to update the row statistics. Now, if the job completes, these queries are cancelled, and 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 queries to update the row statistics complete.
Fixed a bug where the results_buffer_size could not be configured using the options query parameter in the connection string, but only as a top-level query parameter. This variable cannot be changed by using the SET command after the session begins.
Fixed a bug where dropping a role or user could leave references behind inside types. This in turn could prevent the command from working correctly.
Fixed a bug where the command could hang for a table if its indexes are referred to by views or functions using the force syntax syntax.
Fixed a bug where the command omitted user-defined composite types. This bug was introduced in v23.1.
Fixed a bug where if a column name that contains UTF-8 characters is referenced in the STORING() clause of the command, the cannot detect whether the column is already handled by an existing index.
Fixed a bug where the erroneously includes virtual columns that are referenced in the STORING() clause of the command.
Fixed a bug introduced in v20.2, where a change to a user-defined type could cause queries against tables using that type to fail with the error like histogram.go: span must be fully contained in the bucket. This bug could occur if the change was from an command or from an or command, which implicitly change the non-public crdb_internal_region type.
Fixed a bug where telemetry logs could emit the same statement fingerprint ID for different SQL statements.
Fixed a bug where adding a column with a default value of an empty array could fail.
Fixed a bug where the could erroneously succeed despite a violation of an ALTER TABLE... ADD CONSTRAINT UNIQUE constraint. Now such a violation results in an error message with the error code 42601.
Fixed a panic in v24.1, v23.2, and v23.1 when the changefeed.aggregator.flush_jitter is configured and a changefeed’s option is set to zero.
Fixed a bug where the public schema was erroneously created with its owner set to the admin role instead of the database owner. Ownership of the public schema can be altered after the schema is created.
Fixed a bug introduced in v23.2.0 where inserting rows into a could cause an internal error if the source was a VALUES clause with a single row and at least one boolean expression.

Performance improvements

The optimizer now generates more efficient query plans for some queries with clauses.

Contributors

This release includes 77 merged PRs by 30 authors.

v23.2.6

Release Date: June 11, 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-v23.2.6.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.6.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.6.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.6.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.6.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.6.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.6.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.6.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.6.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.6.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.6

Enterprise edition changes

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).

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.
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.
The can now plan constrained scans over partial indexes in more cases, particularly on with predicates referencing .
The row-level TTL setting is now set to 100 by default, which sets the rate limit for deleting expired rows to 100.

Operational changes

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 , 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 , sql.stats.activity.updates.failed, to measure the number of update attempts made by the SQL activity update job that failed with errors. The SQL activity update job is used to pre-aggregate top K information within the SQL stats subsystem and write the results to system.statement_activity and system.transaction_activity.
Added a new counter , sql.stats.flush.fingerprint.count, that tracks the number of unique statement and transaction fingerprints included in the SQL stats flush.
Added the sql.pgwire.pipeline.count , which measures how many wire protocol commands have been received by the server, but have not yet started 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 events are now logged to the unconditionally. Previously, these would only be logged if the server.auth_log.sql_sessions.enabled was set to true. All other SESSIONS log messages are still only logged if server.auth_log.sql_sessions.enabled or server.auth_log.sql_connections.enabled are set to true. To not show client_authentication_ok and client_session_end events, disable the SESSIONS log channel entirely.

DB Console changes

The details and Table details pages now display the correct stats in the Table Stats Last Updated.
Viewing the sorted by % of Runtime now correctly sorts entries by the runtime amount.

Bug fixes

Fixed a bug where combined with ( server.identity_map.configuration ) did not work. For the feature to work correctly, the client must specify a valid database 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.
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 where privileges granted for were incorrectly showing up in , but were not useful because there was no associated object name. The privileges no longer appear in SHOW SYSTEM GRANTS. Instead, the SHOW GRANTS ON EXTERNAL CONNECTION statement should be used.
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 routine to return incorrect results when the routine included:
- At least one parameter.
- An IF statement with one leak-proof branch and one branch with side effects.
Fixed a bug that could result in an internal error when attempting to create a routine using the (currently unsupported) %ROWTYPE syntax for a variable declaration.
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 introduced in v23.2 that could cause a variable assignment to not be executed if the variable was never referenced after the assignment.
Fixed a bug where CockroachDB could run into an attempting to append refresh spans after the tracked timestamp has moved forward internal error in some edge cases. The bug had been present since v22.2.
A will now log rather than fail if it reports an out-of-bound progress fraction.
Fixed a bug that would occur when is followed by 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.
Fixed a bug that could lead to descriptors with self references that pointed to incorrect descriptor IDs. Now, tables that see the error invalid inbound foreign key... origin table ID should be or invalid outbound foreign key... reference table ID should be will automatically repair post deserialization.
Fixed a bug where a failed job could leave the system in a state where re-attempting the restore was not possible without manual intervention.
in the 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");.
Fixed a crash introduced in v23.2.5 that could occur when planning on a table with a using a user-defined type when the newly introduced sql.stats.virtual_computed_columns.enabled is set to true. (The setting was introduced in v23.2.4 and set to false by default.)
Added automated clean up and validation for inside descriptors.
Fixed a bug where and could leave references behind inside types, which could prevent from working.
Fixed a bug where a change to a could cause queries against tables using that type to fail with the 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 crdb_internal_region type). This was present since user-defined types were introduced in v20.2.

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 operators more accurately. It may produce more efficient query plans in some cases.
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.

Contributors

This release includes 115 merged PRs by 32 authors.

v23.2.5

Release Date: May 7, 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-v23.2.5.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.5.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.5.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.5.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.5.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.5.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.5.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.5.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.5.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.5.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.5

SQL language changes

The new enables collection of on virtual .
The new optimizer_use_virtual_computed_column_stats configures the to consider table statistics on virtual computed columns.
The new FORCE_INVERTED_INDEX configures the to prefer a query plan scan over any inverted index of the hinted table. If no such query plan can be generated, an error is logged.
The can now plan constrained scans over in more cases, particularly on partial indexes with predicates referencing virtual .

Operational changes

A minimum scheduler concurrency is now enforced per so that a node with many stores does not spread workers too thinly. This avoids high scheduler latency across on a store when load is imbalanced.
A optimization to reduce duplicates during aggregator restarts has been disabled due to poor performance.

DB Console changes

The Commit Latency chart in the now aggregates by max instead of by sum for multi-node changefeeds. This more accurately reflects the amount of time for events to be acknowledged by the downstream sink.

Bug fixes

Fixed a slow memory leak when opening many new . This bug was introduced in v22.2.9 and v23.1.0.
Fixed a bug that occurred when using to drop and re-add a with the same name.
options MINVALUE and MAXVALUE automatically adjust to new types bounds. This mirrors the behavior of PostgreSQL.
Fixed a bug that could prevent timeseries graphs shown on the DB Console SQL Activity page from rendering correctly when specifying a custom time range.
Fixed a bug present since at least v21.1 that could lead to incorrect evaluation of an IN expression with:
- type on the left side, and
- Values on the right side that are outside of the range of the left side.
Fixed a leak in reported memory usage (not the actual memory usage) by the internal memory accounting system, the limit for which is configured via the flag when a long-running sessions issues hundreds of thousands or more . This reporting bug could cause root: memory budget exceeded errors for other queries. The bug was introduced in v23.1.17 and v23.2.3.
Fixed a bug introduced in v23.2.4 that could prevent collection of on tables that have on virtual of when the newly-introduced is set to true (defaults to false). The setting was introduced in v23.2.4 and is disabled by default.
Fixed a bug where a statement could fail if a sequence existed that did not support the being granted.
Fixed an existing bug where an unused value cannot be dropped from an if theENUM itself is referenced by a . A value can now be dropped from anENUM as long as the value itself is not being referenced by any other data element, including a user-defined function.

Contributors

This release includes 79 merged PRs by 33 authors.

v23.2.4

Release Date: April 11, 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-v23.2.4.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.4.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.4.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.4.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.4.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.4.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.4.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.4.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.4.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.4.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.4

SQL language changes

Mutation statements such as and as well as locking statements such as are not allowed in or . Previously, a bug existed where mutation statements and locking statements in implicit single-statement transactions using AS OF SYSTEM TIME were allowed.
The new cluster setting , when enabled, allows the collection of on .
The new optimizer_use_virtual_computed_column_stats, when enabled, configures the to use on .

DB Console changes

Fixed an issue where clusters with multiple per node could list inaccurate region and node information on the .
Users will no longer see displayed on the . Previously views would be listed with no information, only displaying errors.

Bug fixes

Previously, on long-running that issue many (hundreds of thousands or more) , CockroachDB’s internal memory accounting system, the limit for which is configured via the ) could leak. This bug, in turn, could result in the error message "root: memory budget exceeded" for other queries. The bug was present in v23.2.3 and is now fixed.
Previously, from to could cause to never move to the . This is now fixed.
A user with the can no longer see constants inside of queries that originate from other users in the . Previously, this redaction did not occur.
Previously, the and the commands incorrectly required the user to have the . However, a user always should be able to view their own queries, even without these privileges. This is now fixed.
Fixed a bug where on certain would open a very large number of connections to the backup storage provider.
Fixed a bug that occurred when using to and back a with the same name.
Fixed a bug in which it was possible to set transaction_read_only to false during an .
Fixed a bug where some files were not closed when inspecting during and .
Fixed an intermittent page crash on the view.

Contributors

This release includes 65 merged PRs by 37 authors

v23.2.3

Release Date: March 20, 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-v23.2.3.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.3.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.3.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.3.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.3.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.3.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.3.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.3.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.3.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.3.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.3

Security updates

The session cookie is now marked HttpOnly to prevent it from being read by any Javascript code. Cookies are also marked Secure for the browser when the cluster is running in secure mode.
Clusters using can now optionally fetch signing keys from configured issuers instead of configuring static signing keys for each issuer. When the new cluster setting server.jwt_authentication.jwks_auto_fetch.enabled is set to true, signing keys are automatically fetched from the issuer using metadata published in its OpenID configuration. In this case, static signing keys in server.jwt_authentication.jwks are ignored. When automatic fetching is enabled, there may be a slight increase in network latency for each JWT authentication request, proportional to the latency between the cluster and the issuer’s endpoint.

Enterprise edition changes

Fixed a bug where creating a changefeed with the and options that targeted tables with a DECIMAL(n) column (i.e., zero-scale DECIMAL column) would cause a panic.

SQL language changes

Changed the sql.index_recommendation.drop_unused_duration cluster setting to public so that it is documented on the page.
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.
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.

Operational changes

Expanded the flag to include problem ranges. This flag still defaults to true.
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.

Command-line changes

Updated the SQL shell help URL to point to the page.
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.

DB Console changes

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.
Updated the to always show the entire selected period, instead of just the period that had data.
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 Full Table/Index Scans chart in the now shows the non-negative derivative of the number of full scans tracked.

Bug fixes

Fixed a bug where a could omit events in rare cases, logging the error cdc ux violation: detected timestamp... that is less or equal to the local frontier. This could happen in the following scenario:
1. A runs on a follower that lags significantly behind the .
2. A transaction commits and removes its transaction record before its resolution is applied on the follower.
3. The follower’s has advanced past the transaction commit timestamp.
4. The rangefeed attempts to push the transaction to a new timestamp (at least 10 seconds after the transaction began).
5. This may cause the rangefeed to prematurely emit a checkpoint before emitting writes at lower timestamps, which in turn may cause the to drop these events entirely, never emitting them.
Decommissioning replicas that are part of a mis-replicated range will no longer get stuck on a rebalance operation that was falsely determined to be unsafe. This bug was introduced in v23.1.0.
CockroachDB will no longer spam the logs with unable to get CPU capacity errors every 10 seconds when running outside of a CPU cgroup.
jobs could previously lead to growth in an internal system table resulting in slower job-system related queries.
Fixed a bug that caused an inscrutable error when a name allocated by SERIAL conflicted with an existing type name.
Fixed an internal error with a message like: LeafTxn... incompatible with locking request that occurs when performing an update under that 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 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.
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 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 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.
Users with the privilege can now request statement bundles using crdb_internal.request_statement_bundle or through the DB Console page.
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 that caused internal errors when executing an statement.
Fixed a bug that could lead to schema changes with a large number of descriptors doing full table scans on system.leases.
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 range merge. This bug was introduced in v23.2.1.
Fixed a bug that occurred when using to drop and re-add a constraint with the same name.
Fixed a bug that caused a slow memory leak that can accumulate when opening many new connections. The bug was present in v22.2.9+ and v23.1+ versions.

Contributors

This release includes 118 merged PRs by 42 authors.

v23.2.2

Release Date: February 27, 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-v23.2.2.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.2.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.2.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.2.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.2.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.2.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.2.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.2.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.2.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.2.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.2

Bug fixes

Fixed a bug where resolved timestamps could get stuck, continually emitting the log message pushing old intents failed: range barrier failed, range split, typically following a . This bug was introduced in v23.2.1.

Contributors

This release includes 2 merged PRs by 2 authors.

v23.2.1

Release Date: February 20, 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-v23.2.1.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.1.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.1.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.1.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.1.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.1.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.1.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.1.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.1.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.1.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.1

Security updates

Introduced the server.redact_sensitive_settings.enabled , which is false by default. If set to true, then the values of the following settings will be redacted when accessed through SHOW commands or other introspection interfaces. In the future, any other sensitive cluster settings that are added will be redacted as well. Users who have the MODIFYCLUSTERSETTING can always view the unredacted settings.
- server.oidc_authentication.client_id
- server.oidc_authentication.client_secret
If the server.redact_sensitive_settings.enabled is set to true, then the MANAGEVIRTUALCLUSTER is required to view the values of the per-virtual-cluster overrides for sensitive cluster settings.
The session cookie is now marked HttpOnly to prevent it from being read by any JavaScript code.
cookies are marked Secure for the browser when the cluster is running in secure mode.

General changes

Updated Go version to 1.21.3.

Enterprise edition changes

Added a new fips_ready, which can be used to verify the readiness of the .
now retries for approximately 3 minutes before failing. This is increased from 20 µs.
Fixed a bug where that targeted schema-locked tables could fail due to a very old highwater timestamp being incorrectly persisted.
Fixed a bug where creating a that targeted tables with a column (i.e., zero-scale DECIMAL column), format='avro', and diff would cause a panic.

SQL language changes

Added the sql.ttl.default_select_rate_limit and the ttl_select_rate_limit table to set the select rate limit. This sets the number of records per table per second per node that can be selected by the .
Fixed a bug in where altering the name of a or that was used in a PL/pgSQL or could break them. This bug was only present in v23.2 alpha and beta releases.
Added support for on a table that has columns typed as of (like ). Tables that use multiple user-defined types with the same name but different are still unsupported.
The new implementation used under (and under when the optimizer_use_lock_op_for_serializable is true ) now locks all instead of only the first column family.
Fixed a bug where under on multi-column-family tables was not locking containing only key columns.
It is now possible to run statements with . The EXPLAIN (OPT) variant will show the body of the procedure, while other variants will only show the procedure name and arguments.
output now contains detailed information about the plans for CASCADE actions.

Operational changes

Per-node logging now logs the top 5 hot ranges on the local node instead of the top 5 hot ranges cluster-wide.

Command-line changes

Added a new command cockroach debug enterprise-check-fips, which diagnoses errors in deployments.
The new flag --enterprise-require-fips-ready can be added to any to prevent startup if certain prerequisites for compliance are not met.
commands now appropriately invoke .Close in the case of an error.

DB Console changes

Updated the “CPU Time” label on the to “SQL CPU Time” and added clarifications to its tooltip.
are now enabled for Serverless clusters.
The is enhanced with charts that visualize number of packets received, number of receiving packets with error, number of receiving packets that got dropped, number of packets sent, number of sending packets with error, and number of sending packets that got dropped.
The tab is now shown for the and pages, for Serverless clusters.

Bug fixes

Fixed a durability bug in storage, caused by incorrect syncing of filesystem metadata. Previously, it was possible to lose writes of a particular kind ( AddSSTable ) that were used by e.g. . This loss was possible only under power-off or operating system crash conditions. Under such conditions, CockroachDB could enter a crash loop on node restart. In the worst case of a coordinated power-off/crash across multiple nodes this could lead to an unrecoverable loss of .
Fixed a bug where large running with execution locality (such as some ) could result in the node being assigned most of the work, causing performance degradation and cluster instability.
Fixed a bug that caused node crashes and panics when running queries on . The bug was only present in v23.2.0-beta.1.
Fixed a bug that existed only in v23.2 alpha and beta versions that could have caused side effects to happen out of order for routines in rare cases.
Fixed a bug that existed since v23.1 that prevented naming parameters when dropping a (or procedure).
Fixed a bug where using could fail shortly after node startup.
Locking tables (e.g., with ) on the null-extended side of (e.g., the right side of a LEFT JOIN ) is now disallowed and returns an error. This improves compatibility with PostgreSQL and prevents ambiguity in . This bug has existed since locking with FOR UPDATE was introduced.
Fixed a display bug in the where because not all types of are setting the value for the mutation ID, the value of the ID could previously show as “with ID undefined” on the . Now, the notification omits the undefined value (the rest of the event notification is still displayed).
Fixed the formatting for routines, which could prevent creating a routine with , and could prevent some expressions from being correctly. The bug only existed in v23.2 alpha and beta releases.
Fixed a bug that would cause a syntax error during of a routine. The bug existed only in v23.2 alpha and beta releases.
Fixed a bug that would cause syntax errors when attempting to a database with or . This bug only affected v23.2 alpha and beta releases.
, , and queries are now disallowed under when the table contains a involving a that is updated, and the check constraint also involves a column family that is not updated, but is read. This is a temporary fix to prevent possible violation of the check constraint, and the restriction will be lifted in the future.
Previously, all AggHistogram -powered metrics were not reporting quantiles properly in the . This patch fixes the histograms so that the quantiles in DB Console are reported correctly. these histograms were only broken in the , but were not broken in the , /_status/vars. The list of affected metrics is shown below.
- changefeed.message_size_hist
- changefeed.parallel_io_queue_nanos
- changefeed.sink_batch_hist_nanos
- changefeed.flush_hist_nanos
- changefeed.commit_latency
- changefeed.admit_latency
- jobs.row_level_ttl.span_total_duration
- jobs.row_level_ttl.select_duration
- jobs.row_level_ttl.delete_duration
Fixed a bug introduced in v23.2 that caused internal errors and panics when certain SQL queries were run with automatic collection enabled.
and may no longer be created on REFCURSOR[] s columns. REFCURSOR columns themselves are not indexable.
Fixed a bug that prevented database when the database contained a or that referenced a in the body string. For views, this bug was introduced in v20.2, when were introduced. For routines, this bug was introduced in v22.2, when user-defined functions (UDFs) were introduced.
Fixed a bug that could cause a function resolution error when attempting to use a like now() as a formatting argument to a RAISE statement.
Fixed a bug where CDC custom key columns did not function correctly with . For example, CREATE CHANGEFEED WITH key_column=..., unordered AS SELECT * FROM table now works correctly instead of retrying forever. Note that some functionalities with CDC custom keys are not fully supported, see for more details.
Fixed a bug in truncation that could lead to crash loops, and unrecoverable loss of in the unlikely worst case that all enter this crash loop. The bug manifested when a few things coincided: The cluster was running a bulk write workload (e.g., , , ); a log truncation command was running; and the process crashed at an unfortunate moment (e.g., the process was killed, or killed itself for reasons like detecting a ).
Fixed the value used for the total runtime on SQL statistics. This was using the wrong value previously, causing the page to display values with more than 100%.
Fixed a bug where trying to set an empty search_path resulted in an error.
It is now possible to assign to the parameter of a . Previously, attempts to do this would result in a “variable not found” error at routine creation time. In addition, variable shadowing is now explicitly disabled, where previously it would cause an internal error. These bugs existed in the v23.2.0 release and the v23.2 pre-release versions.
Fixed a bug in the that would cause it to skip expired rows if the of the table included columns of the type. This bug was present since the initial release of row-level TTL in v22.2.0.
Fixed a bug where concurrent statements can cause deadlocks.
CockroachDB can now transparently retry more retryable errors when performing a non-atomic command.
Fixed a bug that caused to fail while a was being created. The symptom of this bug was an error like column "crdb_internal_val_shard_16" does not exist. This bug was present since v23.1.0.
Previously, CockroachDB could encounter the error unable to encode table key: *tree.DTSQuery when operating on columns with the internal TSQuery type in some contexts (e.g., when collecting or when performing a ). This is now fixed. The bug had been present since v23.1 when support for the internal TSQuery type was added.
Previously, in some cases CockroachDB could incorrectly evaluate queries that scanned an and had a in which two sides of the AND expression had “similar” expressions (e.g., ARRAY['str1'] <@ col AND (ARRAY['str1'] && col OR...) ); this is now fixed. The bug had been present since prior to v22.2.
Fixed a bug that could cause queries sent by the to use a rather than the to find the rows to delete. This could lead to some DELETE operations taking a much longer time than they should. This bug was present since v22.2.0.
Fixed an issue with missing data on SQL statistics, and consequently missing data on the , by properly recalculating the value from the current and past hour on the top activity table.
Internal queries issued by the should now use optimal plans. The bug has been present since at least v22.2.
Fixed a bug where a could omit events in rare cases, logging the error cdc ux violation: detected timestamp... that is less or equal to the local frontier. This could happen in the following scenario:
1. A runs on a follower that lags significantly behind the .
2. A transaction commits and removes its before its resolution is applied on the follower.
3. The follower’s has advanced past the transaction commit timestamp.
4. The rangefeed attempts to push the transaction to a new timestamp (at least 10 seconds after the transaction began).
5. This may cause the rangefeed to prematurely emit a checkpoint before emitting writes at lower timestamps, which in turn may cause the to drop these events entirely, never emitting them.

Contributors

This release includes 252 merged PRs by 60 authors.

v23.2.0

Release Date: February 5, 2024 With the release of CockroachDB v23.2, we’ve added new capabilities to help you migrate, build, and operate more efficiently. See 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-v23.2.0.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0.linux-arm64.tgz (SHA256)	cockroach-sql-v23.2.0.linux-arm64.tgz (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0.windows-6.2-amd64.zip (SHA256)

Docker image

docker pull cockroachdb/cockroach:v23.2.0

Feature highlights

This section summarizes the most significant user-facing changes in v23.2.0 and other features recently made available to CockroachDB users across versions. For a complete list of features and changes in v23.2, including bug fixes and performance improvements, see the release notes for previous v23.2 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, see the .

Observability

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
Identify network partitions using updated metrics in the Network page The in the DB console has been updated with additional metrics that surface when the cluster is unstable due to network partitions.	23.2
Troubleshoot 40001 errors from isolation conflicts in highly contended workloads have been enhanced to include additional information (conflicting transaction and location) into 40001 errors that stem from isolation conflicts in highly contentious workloads.	23.2
Identify and troubleshoot your most recent transactions and statements in the console Users can control the . They can turn off automatic polling and instead manually refresh the page. The page will persist recent executions and their statistics and plans to allow users to troubleshoot their recent workload. Previously, the Active executions page would refresh automatically and cause potentially problematic executions to disappear from the page making it difficult to troubleshoot recent workloads.	23.2
Integrate SQL activity with Datadog for end-to-end observability such as statements and transactions can be emitted with fine granularity to Datadog as logs to allow end to end observability using both metrics and logs.	23.2
Customize your own metric dashboard for CockroachDB serverless The CockroachDB Cloud console supports additional in a single dashboard for CockroachDB Serverless.	All^*

Migrations

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
Migrate to CockroachDB using Oracle Golden Gate You can now use to stream data directly into CockroachDB. Migrate data from compatible databases onto CockroachDB using this connector.	All^**
Migrate to CockroachDB using Debezium You can now use to stream data directly into CockroachDB. Migrate data from compatible databases onto CockroachDB using this connector.	All^**

Disaster recovery

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
Physical Cluster Replication is now available in Preview is an asynchonous replication feature that allows your cluster to recover from full-cluster failure with a low RPO and RTO. In 23.2, it is a Preview feature, requiring an , and only available for self-hosted CockroachDB deployments.	23.2

Security and compliance

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
Use Azure IAM to authenticate storage for changefeeds and backup/restore Use to leverage existing azure credentials to authenticate with your Azure Blob Storage bucket.	23.2
Folders UI in CockroachDB Cloud Orgs (Limited Access) CockroachDB Cloud organizations can now organize clusters using and can assign roles and permissions at the folder scope.	All^*

Deployment and operations

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
General Availability for ARM binaries for Linux and Docker With this release, Linux and Docker binaries for the ARM 64-bit architecture are Generally Available (GA) for production workloads. ARM binaries for macOS are experimental and not yet qualified for production use. For more details, installation instructions, and limitations, refer to .	23.2

SQL

Feature	Availability
Feature	Ver.	Self-Hosted	Dedicated	Serverless
Support Read Committed Isolation Level in public preview is a weaker transaction isolation level than Serializable and is the default isolation level in databases such as PostgreSQL, Oracle, and SQL Server. Read Committed isolation allows writes to interleave without aborting transactions and prevents writes from blocking reads, thus minimizing query latency and retries caused by read/write contention.	23.2
Improved UDF capabilities now support mutations (INSERT, UPDATE, UPSERT, and DELETE).	23.2
Support stored procedures and PL/pgSQL PL/pgSQL capabilities such as , conditional logic, loops, and exception handling are now supported, increasing compatibility between CockroachDB and PostgreSQL. An is required.	23.2				Delete operation admission control This feature reduces the potential impact of deleting a large number of rows—directly, as well as implicitly via row-level TTL—on query performance and system stability. For more information, see .	23.2
Replication admission control This mechanism automatically paces work for which longer exection times are acceptable (such as index backfills) at the speed of the slowest replica in order to maintain cluster stability and throughput. For more information, see	23.2
Column Level Encryption CockroachDB now supports through a set of built-in functions. This feature allows you to encrypt one or more columns in every row of a database table, and can be useful for compliance scenarios such as adhering to PCI or GDPR. An is required.	23.2
Revoke CREATE privilege by default for public schema Newer versions of PostgreSQL (15 and above) do not grant the by default on the public schema. This change can be disruptive but to preserve Postgres compatibility it is now guarded behind a cluster setting as an opt in feature. This is controlled using a cluster setting: `SET CLUSTER SETTING sql.auth.public_schema_create_privilege.enabled=true;`	23.2
Easily find Default Privileges for a Role This feature adds a simple syntax to see the . SHOW DEFAULT PRIVILEGES FOR GRANTEE root;	23.2

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.

The pre-v23.1 output produced by SHOW RANGES, crdb_internal.ranges, and crdb_internal.ranges_no_leases was deprecated in v23.1 and is now replaced by default with output that’s compatible with coalesced ranges (anges that pack multiple tables/indexes/partitions into individual ranges). See the for SHOW RANGES for more details.
When a deployment is configured to use a time zone for log file output using formats crdb-v1 or crdb-v2, new output log entries cannot be processed by nodes that have not been upgraded to v23.2.
When customizing the , the special sequence %M now expands to the full host name instead of the combination of host name and port number. To include the port number explicitly, use %>. The special sequence %m now expands to the host name up to the first period.
The command stores data retrieved from SQL tables in the remote cluster using the TSV format by default.
The will only apply to newly created changefeeds in v23.2. For existing changefeeds, you can set the option so that changefeeds do not experience infinite retries and accumulate protected change data. You can use the statement to add protect_data_from_gc_on_pause to existing changefeeds.
The direct export of traces to Jaeger and the trace.jaeger.agent have been removed. The direct export functionality had been obsoleted since 2022; it stopped working altogether sometime in 2023 with the following error: data does not fit within one UDP packet; size 65006, max 65000, spans NN. Since 2022, Jaeger supports ingestion of traces using OTLP; and CockroachDB has supported emitting traces using OTLP since v22.1. Operators and developers who want to inspect traces are thus invited to use the OTLP protocol instead. The corresponding cluster setting is trace.opentelemetry.collector. For a successful deployment, an intermediate OTLP collector/forwarder should be configured. For an example of how to orchestrate the OpenTelemetry collector and Jaeger together using Docker Compose, or how to configure the otel-collector, see the more-detailed entry in v23.2-alpha.3 backward-incompatible changes.

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.

The new sql.txn.read_committed_syntax.enabled, controls whether transactions run under READ COMMITTED or SERIALIZABLE isolation. It defaults to false. When set to true, the following statements will configure transactions to run under READ COMMITTED isolation:
- BEGIN TRANSACTION ISOLATION LEVEL READ COMMITTED
- SET TRANSACTION ISOLATION LEVEL READ COMMITTED
- SET default_transaction_isolation = 'read committed'
- SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL READ COMMITTED
The sql.txn.read_committed_syntax.enabled was renamed to .
Users who have the can now grant and revoke role membership in any non-admin role. This change also removes the , which was added in v23.1. In v23.2, the cluster setting is effectively always true.
The sql.metrics.statement_details.gateway_node.enabled now defaults to false to reduce the number of rows generated in SQL Statistics pages.
The kv.rangefeed.enabled no longer controls access to RANGEFEED SQL commands. Instead, use feature.changefeed.enabled.
The related to have been renamed for consistency. For example, bulkio.stream_ingestion.minimum_flush_interval is now named physical_replication.consumer.minimum_flush_interval.
CockroachDB now periodically dumps the state of its internal memory accounting system into the heap_profiler/ directory when a heap profile is taken. To disable this behavior, set the diagnostics.memory_monitoring_dumps.enabled to false.
Introduced the kv.gc.sticky_hint.enabled in v23.1.13. This setting helps expedite after range deletions. For example, when a SQL table or index is dropped. kv.gc.sticky_hint.enabled is enabled by default and deprecated in v23.2.
CockroachDB now enables the pacing mechanism in rangefeed closed timestamp notifications, by setting the default kv.rangefeed.closed_timestamp_smear_interval cluster setting to 1ms. This makes rangefeed closed timestamp delivery more uniform and less spikey, which reduces its impact on the Go scheduler and, ultimately, foreground SQL latencies.

Deprecations

The protect_data_from_gc_on_pause option has been deprecated. This option is no longer needed since changefeed jobs always protect data.
The cockroach connect functionality has been deprecated.

Known limitations

For information about new and unresolved limitations in CockroachDB v23.2, with suggested workarounds where applicable, see .

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.

v23.2.0-rc.2

Release Date: January 9, 2024

Downloads

CockroachDB v23.2.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-v23.2.0-rc.2.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-rc.2.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-rc.2.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-rc.2.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-rc.2.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-rc.2.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-rc.2.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-rc.2.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-rc.2.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-rc.2.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:

The ARM image is in Limited Access.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-rc.2

Bug fixes

Fixed a bug introduced in v23.2 that caused internal errors and panics when certain queries ran with automatic .
Fixed a bug where mixed-version clusters with both v23.1 and v23.2 nodes could detect a false-positive replica inconsistency in .

Contributors

This release includes 12 merged PRs by 9 authors.

v23.2.0-rc.1

Release Date: December 21, 2023

Downloads

CockroachDB v23.2.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-v23.2.0-rc.1.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-rc.1.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-rc.1.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-rc.1.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-rc.1.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-rc.1.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-rc.1.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-rc.1.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-rc.1.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-rc.1.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:

The ARM image is in Limited Access.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-rc.1

Enterprise edition changes

Added a SQL function crdb_internal.fips_ready() that can be used to verify the readiness of the gateway node.
now retries for just over 3 minutes before failing.

SQL language changes

CALL statements can now be run with . The EXPLAIN (OPT) variant will show the body of the procedure, while other variants will show only the procedure name and arguments.
Added support for a table that has columns typed as arrays of user-defined types (like ). Tables that use multiple user-defined types with the same name but different schemas are still unsupported.
The implementation used under Read Committed isolation (and under when is set to true ) now locks all instead of only the first column family.

Command-line changes

Added the command that diagnoses errors in deployments.
Added the flag --enterprise-require-fips-ready that can be run with any to prevent startup if certain prerequisites for compliance are not met.

DB Console changes

Updated the CPU Time label to SQL CPU Time and added clarification to its tooltip on the and pages.
Removed the ID when it is undefined from the event description in the .

Bug fixes

Fixed a bug that caused node crashes and panics when running queries on tables with UNIQUE constraints or indexes. The bug is only present in version v23.2.0-beta.1.
, , and queries are now disallowed under Read Committed isolation when the table contains a involving a that is updated, and that CHECK constraint also involves a column family that is not updated, but is read. This restriction is a temporary fix to prevent possible violation of the CHECK constraint. However, it is important to note that this restriction will be lifted in the future.
Fixed a bug where using may fail shortly after node startup.
Fixed the formatting for plpgsql routines, which could prevent the creation of a routine with loop labels and could prevent some expressions from being redacted correctly. The bug only existed in alpha and beta versions of v23.2.
Fixed a bug that would cause a syntax error during redaction of a PL/pgSQL routine. The bug existed only in alpha and beta versions of the v23.2 release.
Fixed a bug that would cause syntax errors when attempting to with PL/pgSQL UDFs or stored procedures. This bug only affected alpha and beta versions of v23.2.
Fixed a bug in PL/pgSQL where altering the name of a or UDT that was used in a PL/pgSQL function or procedure could break them. This is only present in v23.2 alpha and beta releases.
Fixed a bug where under Read Committed isolation on multi-column-family tables was not locking containing only key columns.
Fixed a bug where all AggHistogram-powered metrics were not reporting quantiles properly in the . The quantiles in the DB Console are now reported correctly. This bug was only present in histograms in the features, and did not affect metrics reporting in the endpoint, /_status/vars. The affected metrics were:
- changefeed.message_size_hist
- changefeed.parallel_io_queue_nanos
- changefeed.sink_batch_hist_nanos
- changefeed.flush_hist_nanos
- changefeed.commit_latency
- changefeed.admit_latency
- jobs.row_level_ttl.span_total_duration
- jobs.row_level_ttl.select_duration
- jobs.row_level_ttl.delete_duration

Contributors

This release includes 49 merged PRs by 26 authors.

v23.2.0-beta.3

Release Date: December 13, 2023

Downloads

CockroachDB v23.2.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.

Operating System	Architecture	Full executable	SQL-only executable
Linux	Intel	cockroach-v23.2.0-beta.3.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-beta.3.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-beta.3.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-beta.3.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-beta.3.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-beta.3.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-beta.3.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-beta.3.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-beta.3.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-beta.3.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:

The ARM image is Experimental and not yet qualified for production use and not eligible for support or uptime SLA commitments.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-beta.3

General changes

Updated Go version to 1.21.3.

SQL language changes

Added the sql.ttl.default_select_rate_limit and the ttl_select_rate_limit to set the TTL select rate limit. This sets the number of records per table per second per node that can be selected by the TTL job.

Bug fixes

Fixed a bug that could result in an incorrect too few columns error for queries that use ANY <array> syntax with a subquery.
Fixed a bug that could cause too few columns / too many columns errors for queries that used IN or NOT IN with a non-trivial right operand, such as a subquery (rather than a constant tuple).
Fixed a bug where with expressions could fail on materialized when the declarative schema changer was used.
Fixed a bug that could cause PL/pgSQL routines with SELECT INTO syntax to return early. This bug existed only in pre-release versions v23.2.0-beta.1 and v23.2.0-beta.2.
Fixed a bug that could cause side effects to happen out of order for PL/pgSQL routines in rare cases. This bug existed only in v23.2 alpha versions and previous v23.2 beta versions.
Previously, in rare cases, CockroachDB could incorrectly evaluate queries with lookup where equality cols are key when performing lookups on multiple ranges. This could either manifest as a stuck query or result in incorrect output. The bug was introduced in v22.2 and is now fixed.
Fixed a durability bug in Raft log storage that was caused by incorrect syncing of filesystem metadata. It was possible to lose writes of a particular kind ( AddSSTable ) used by (e.g.) RESTORE. This loss was possible only under power-off or OS crash conditions. As a result, CockroachDB could enter a crash loop on restart. In the worst case of a coordinated power-off/crash across multiple nodes, this could lead to an unrecoverable loss of quorum.
Fixed a bug where large jobs running with option could result in the being assigned most of the work causing performance degradation and cluster instability.
Fixed a bug that prevented naming UDT parameters when (or procedure). This bug has existed since v23.1.
Locking tables (e.g., with ) on the null-extended side of outer joins (e.g., the right side of a LEFT JOIN ) is now disallowed and returns an error. This improves compatibility with PostgreSQL and prevents ambiguity in locking semantics. This bug has existed since locking with FOR UPDATE was introduced.

Contributors

This release includes 26 merged PRs by 20 authors.

v23.2.0-beta.2

Release Date: December 5, 2023

Downloads

CockroachDB v23.2.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-v23.2.0-beta.2.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-beta.2.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-beta.2.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-beta.2.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-beta.2.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-beta.2.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-beta.2.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-beta.2.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-beta.2.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-beta.2.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:

The ARM image is Experimental and not yet qualified for production use and not eligible for support or uptime SLA commitments.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-beta.2

General changes

CockroachDB now periodically dumps the state of its internal memory accounting system into the heap_profiler/ directory when a heap profile is taken. To disable this behavior, set the diagnostics.memory_monitoring_dumps.enabled cluster setting to false.
Multi-level compactions have been disabled to investigate possible performance issues with foreground throughput and latency.

Enterprise Edition changes

When using Physical Cluster Replication, you can now initiate a cutover as of LATEST before the initial scan completes.
Sensitive information such as api_secret, sasl_password, client_cert, and ca_cert, is now redacted in output from commands SHOW CHANGEFEED JOB, SHOW CHANGEFEED JOBS, and SHOW JOBS.
The physical_replication.frontier_lag_nanos metric and the related DB Console graph have been removed because they sometimes display incorrect information. For alerting, it is recommended to use the new metric physical_replication.replicated_time_seconds metric instead.
Fixed a bug in physical cluster replication where replicating from a primary cluster that is on a version prior to v23.2.x to a standby cluster running on v23.2.x could fail because of an undefined builtin function in the primary cluster.

DB Console changes

In the , the Max Checkpoint Latency chart title now refers to “Lag” rather than “Latency”, to better reflect the intention of the underlying metric, which measures how recently the changefeed was last checkpointed.
Times on the X-Axis of bar charts in Statement details pages are now correctly formatted in UTC.
In the SQL Activity Transaction Details page, you can now view a transaction fingerprint ID across multiple applications by specifying the application name in the appNames URL GET parameter using a comma-separated encoded string of transaction fingerprint IDs.

Bug fixes

Fixed a bug that prevented the Now button on time range selectors in the DB Console from working as expected when a custom time period was previously selected.
Fixed a bug that prevented the SQL Activity page from showing internal statements when the sql.stats.response.show_internal.enabled cluster setting was set to true.
Fixed a bug where an active replication report update could get stuck in a retry loop on clusters with over 10000 ranges. This could prevent a node from shutting down cleanly.
Fixed a bug introduced in v23.1 that could cause an internal error when using the text format (as opposed to binary) when with a user-defined composite type.
Fixed a bug that could cause a replica to be stuck processing in a queue’s replica set when the replica had recently been removed from purgatory for processing but was destroyed, or the replica’s ID changed before being processed. These replicas are now removed from the queue when they are encountered.
Fixed a bug that could cause a to fail if it references both an enum and a table that has undergone a schema change.
Fixed a bug that could cause cluster version finalization to contend with descriptor lease renewals on large clusters. Descriptor lease renewals previously had a higher priority than cluster upgrade finalization. Finalization now always has a higher priority than descriptor lease renewal.
Fixed a bug that prevented backups from distributing work evenly across all replicas, including followers, regardless of leaseholder placement.
Fixed a bug introduced in v23.2.0-beta.1 that could cause a single composite-typed variable to be incorrectly handled as the target of a PostgreSQL INTO clause.
Fixed a bug that could cause a BEGIN statement log to record incorrect information in the Age field, which could also cause them to appear erroneously in slow-query logs.

Performance improvements

Query planning time has been reduced significantly for some queries in which many tables are joined.

Contributors

This release includes 91 merged PRs by 35 authors.

v23.2.0-beta.1

Release Date: November 27, 2023

Downloads

CockroachDB v23.2.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-v23.2.0-beta.1.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-beta.1.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-beta.1.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-beta.1.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-beta.1.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-beta.1.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-beta.1.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-beta.1.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-beta.1.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-beta.1.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:

The ARM image is Experimental and not yet qualified for production use and not eligible for support or uptime SLA commitments.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-beta.1

SQL language changes

commands now use the by default, which makes COPY commands subject to . The new session variable copy_transaction_quality_of_service controls the quality-of-service level for COPY commands. Previously, COPY used the same level as other commands, determined by the default_transaction_quality_of_service session variable, which is set to regular by default. regular is not subject to admission control.

DB Console changes

The now correctly renders the background color for the email signup, which fixes an issue where it was difficult to read the text.
Fixed a bug where selecting the internal application name prefix $ internal from the Application Name dropdown on the was not showing internal queries. The filtering logic will now show if there are statements with the $ internal application name prefix.

Bug fixes

Fixed a bug where an empty corresponding to a did not respect system-level span configurations such as , which potentially caused reads above the protected timestamp to fail.
Fixed error handling for GetFiles so that it does not cause a nil pointer dereference.

Contributors

This release includes 33 merged PRs by 21 authors.

v23.2.0-alpha.7

Release Date: November 20, 2023

Downloads

CockroachDB v23.2.0-alpha.7 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-v23.2.0-alpha.7.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.7.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-alpha.7.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-alpha.7.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-alpha.7.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.7.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-alpha.7.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.7.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-alpha.7.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-alpha.7.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:

The ARM image is Experimental and not yet qualified for production use and not eligible for support or uptime SLA commitments.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-alpha.7

SQL language changes

Previously, if was set to off, then was run on a column which contained a NULL value, an error with code 23514 ( check_violation ) would be returned. Now in this scenario the error returned will have code 23502 ( not_null_violation ) to match PostgreSQL.
The sql.txn.read_committed_syntax.enabled was renamed to .

Command-line changes

The cockroach connect functionality has been deprecated.

DB Console changes

Previously, the forward arrow button on the would not move the time window forward if the current end time was less than “Now() - time window”. For example, with a 10 minute time window, it was not possible to move forward if current end time is less that “Now() - 10 minutes”. This caused the forward arrow button to become disabled even though there was more data to display. Now this scenario is handled by the forward arrow button selecting the latest available time window (similar to the Now button).

Bug fixes

Removed duplication of metrics names on charts’ tooltips.
Fixed a bug that could cause to hang if were changed after regions were added.
A bug in the code prevented users from setting the (set via the format-options structure) within their log configuration. Specifically, when users tried to use these options in file-defaults with any type log format, the log configuration was previously unable to be parsed due to validation errors. This was because the file-defaults.format-options were propagated to the sinks.stderr.format-options. sinks.stderr only supports a format of . Therefore, the incorrectly propagated format-options, which are only supported by the json log format, were identified as not being supported when validating sinks.stderr. This bug is now fixed and the file-defaults.format-options are only propagated to sinks.stderr.format-options if both of these conditions are true: 1. file-defaults.format is one of or crdb-v2-tty. 2. sinks.stderr.format-options are not explicitly set in the log configuration.
Previously, when executing queries with or or both when the ordering needs to be maintained, CockroachDB in some cases would get into a pathological behavior which would lead to increased query latency, possibly by one or two orders of magnitude. This bug was introduced in v22.2 and is now fixed.
Previously, the incorrectly required the user to have the admin role. Now, it correctly only requires the user to have any on the table being inspected.
Fixed a bug that could cause a to skip scanning rows from the local region when performing a with a as the input.

Performance improvements

This change prevents failed requests from being issued on follower nodes that are or unhealthy which prevents latency spikes if those nodes later go offline.

Contributors

This release includes 95 merged PRs by 33 authors.

v23.2.0-alpha.6

Release Date: November 7, 2023

Downloads

CockroachDB v23.2.0-alpha.6 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-v23.2.0-alpha.6.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.6.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-alpha.6.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-alpha.6.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-alpha.6.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.6.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-alpha.6.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.6.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-alpha.6.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-alpha.6.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:

The ARM image is Experimental and not yet qualified for production use and not eligible for support or uptime SLA commitments.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-alpha.6

General changes

The CockroachDB Docker image is now based on Red Hat’s ubi9/ubi-minimal image instead of the ubi8/ubi-minimal image.

SQL language changes

Added the built-in jsonb_array_to_string_array that converts array to array.
The built-in jsonb_array_to_string_array can now return objects.

Operational changes

Introduced the kv.gc.sticky_hint.enabled that helps expediting after range deletions. For example, when a SQL table or index is dropped. kv.gc.sticky_hint.enabled is enabled by default in v23.2. The setting has been deprecated in v23.2.
Introduced a new that allows an operator to configure the concurrency.
will now collect the active traces of all running or reverting traceable jobs. This includes , , , and .

Cluster virtualization

The that controls access to CREATE VIRTUAL CLUSTER and other virtual cluster management syntax is now called MANAGEVIRTUALCLUSTER.

Bug fixes

Fixed a bug that could prevent from working if it was performed during a cluster upgrade.
Fixed a bug where the opclass for a is not shown if CockroachDB creates a trigram index and later displays it via .
Fixed a bug where CockroachDB could incorrectly evaluate and index into tables with at least three . This would result in either the non-nullable column with no value internal error, or the query would return incorrect results. This bug was introduced in v22.2.
Fixed a bug where would incorrectly disable while new secondary indexes were being backfilled when using the .
Fixed a bug where the unique_constraint_catalog and unique_constraint_schema columns in could be incorrect for cross schema or cross database references.
Fixed a bug in a method that was used by some of the observability infrastructure. This method could be triggered if a file was overwritten with a different chunking strategy.
Fixed a bug where the result of for a table that had a with a default expression was incorrect because the statement could not be parsed.
Fixed the SQL activity update job to: avoid conflicts on update, reduce the amount of data cached to only what the overview page requires, and fix the correctness of the top queries.
Fixed a bug that could prevent from advancing in the face of some range deletion operations.
Fixed a bug where could get stuck if was executed concurrently.
Fixed a bug that could cause internal errors or panics while attempting to forecast on a numeric column.
Rolled back deletes no longer cause a discrepancy between computed statistics and the actual stored values.

Performance improvements

Addressed a performance regression that can happen when the declarative is used to create an index with a concurrent workload.

Contributors

This release includes 117 merged PRs by 49 authors.

v23.2.0-alpha.5

Release Date: October 30, 2023

Downloads

CockroachDB v23.2.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-v23.2.0-alpha.5.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.5.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-alpha.5.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-alpha.5.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-alpha.5.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.5.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-alpha.5.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.5.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-alpha.5.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-alpha.5.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:

The ARM image is Experimental and not yet qualified for production use and not eligible for support or uptime SLA commitments.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-alpha.5

SQL language changes

Added support for the special OTHERS condition in PL/pgSQL exception blocks, which allows matching any error code apart from query_canceled and assert_failure. Note that Class 40 errors ( 40000, 40001, 40003, 40002, and 40P01 ) cannot be caught either. This is tracked in.

Bug fixes

Previously, queries with the aggregate function could produce incorrect results in some cases due to the query optimizer performing invalid optimizations. This is now fixed. This bug had been present since the ST_Union function was introduced in v20.2.0.

Contributors

This release includes 27 merged PRs by 17 authors.

v23.2.0-alpha.4

Release Date: October 23, 2023

Downloads

CockroachDB v23.2.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-v23.2.0-alpha.4.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.4.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-alpha.4.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-alpha.4.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-alpha.4.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.4.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-alpha.4.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.4.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-alpha.4.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-alpha.4.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:

The ARM image is Experimental and not yet qualified for production use and not eligible for support or uptime SLA commitments.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-alpha.4

General changes

Updated the licenses/CCT.txt file to reflect the latest Cockroachdb Community License.

Enterprise edition changes

Renamed related to for consistency. For example, bulkio.stream_ingestion.minimum_flush_interval is now physical_replication.consumer.minimum_flush_interval.

SQL language changes

has two columns that surface the schedule options. These columns have been renamed to align with the documented option names: on_previous_running and on_execution_failure.
Added support for the PLpgSQL CLOSE statement, which allows a PLpgSQL routine to close a cursor with the name specified by a cursor variable.
When a with remove_regions is performed, the restore job will now fail if the object contains a table.
It is now possible to open a within a PLpgSQL function or procedure with an exception block. If an error occurs, creation of the cursor is rolled back before control reaches the exception handler.
If a resumes on a new cluster (e.g., after or a cluster restore), the backup schedule will pause. The user may without changing it, but should take special care to ensure no other schedule is backing up to the same . The user may also want to cancel the paused schedule and start a new one.
Added support for PLpgSQL FETCH and MOVE statements. Similar to SQL FETCH / MOVE statements, commands that would seek the backward will fail. In addition, expressions other than constant integers are not yet supported for the count option.
Added support for the REFCURSOR data type. REFCURSOR is a special string type that is used to handle cursors. PLpgSQL cursor declarations are required to use a variable of type REFCURSOR, and the name of a cursor can be passed to and from a PLpgSQL function or procedure.
Added two changes to :
- Multiple FOR UPDATE clauses on fully parenthesized queries are now disallowed. For example, the following statements are now disallowed:
  (SELECT 1 FOR UPDATE) FOR UPDATE; SELECT * FROM ((SELECT 1 FOR UPDATE) FOR UPDATE) AS x;
  Whereas statements like the following are still allowed:
  SELECT * FROM (SELECT 1 FOR UPDATE) AS x FOR UPDATE; SELECT (SELECT 1 FOR UPDATE) FOR UPDATE;
  This does not match PostgreSQL, which allows all of these, but does match CockroachDB behavior for ORDER BY and LIMIT.
- FOR UPDATE is now allowed on statements with VALUES in the FROM list, or as a subquery. For example, the following statements are now allowed:
  SELECT (VALUES (1)) FOR UPDATE; SELECT * FROM (VALUES (1)) AS x FOR UPDATE;
  Using FOR UPDATE directly on VALUES is still disallowed:
  VALUES (1) FOR UPDATE; (VALUES (1)) FOR UPDATE; INSERT INTO t VALUES (1) FOR UPDATE;
  This matches PostgreSQL.
FOR UPDATE is now permitted on some queries that were previously disallowed. Queries that use the following operations are now allowed to have FOR UPDATE OF as long as the prohibited operation is in a subquery not locked by the FOR UPDATE OF:
- UNION
- INTERSECT
- EXCEPT
- DISTINCT
- GROUP BY
- HAVING
- Aggregations
- For example, the following query is now allowed because the subquery using the prohibited operations is not affected by the FOR UPDATE OF:
  SELECT * FROM t, (SELECT DISTINCT 0, 0 UNION SELECT a, count(*) FROM t GROUP BY a HAVING a > 0) AS u FOR UPDATE OF t;
  This matches PostgreSQL.
Identifiers after numeric constants that are not separated by whitespace are now disallowed to match PostgreSQL 15 behavior.
Added the new column contention_type to the table. This column indicates the type of encountered. Current values are LOCK_WAIT and SERIALIZATION_CONFLICT.
Changed the error message: statement error cannot execute FOR UPDATE in a read-only transaction to statement error cannot execute SELECT FOR UPDATE in a read-only transaction to match PostgreSQL.
Added a new optimizer_use_lock_op_for_serializable, which when set enables a new implementation of SELECT FOR UPDATE. This new implementation of SELECT FOR UPDATE acquires row locks after any joins and filtering, and always acquires row locks on the primary index of the table being locked. This more closely matches behavior in PostgreSQL, but at the cost of more round trips from gateway node to replica leaseholder. Under read-committed isolation (and other isolation levels weaker than serializable), CockroachDB will always use this new implementation of SELECT FOR UPDATE regardless of the value of optimizer_use_lock_op_for_serializable to ensure correctness.

Operational changes

Added a new server.http.base_path that controls the redirection of the browser after successful login with . It is unlikely that this setting would need adjustment. However, it is helpful in cases where CockroachDB is running behind a load balancer or proxy that serves CockroachDB under a subpath, such as https:// <hostname>/crdb/. In those cases, it is necessary for the browser to redirect to / crdb after login instead of /, which has always been the hard-coded default.

Cluster virtualization

The following settings can now only be set from the system virtual cluster:
- All the physical_replication.* settings
- server.rangelog.ttl
- timeseries.storage.*
The cluster.organization and enterprise.license can now only be set via the system virtual cluster. Attempting to set them from any other virtual cluster results in an error.
A new flag --internal-rpc-port-range allows operators to specify the port range used by virtual clusters for node-to-node communication. Users implementing or cluster virtualization public preview features should use this flag if they require the cockroach processes to only communicate using ports in a known port range.
Two guardrails are available to system operators to help with users upgrading from a deployment without cluster virtualization enabled to a deployment using cluster virtualization. This is intended to help in cases where the user is not connected to the correct SQL interface to perform certain configuration operations. There are two guardrails included:
- The sql.restrict_system_interface.enabled cluster setting encourages users to use a virtual cluster for their application workload. When set, certain common operations that end users may execute to set up an application workload are disallowed, such as running DDL statements or modifying an application level cluster setting. Users will receive an error similar to:
  ERROR: blocked DDL from the system interface SQLSTATE: 42501 HINT: Object creation blocked via sql.restrict_system_interface.enabled to prevent likely user errors. Try running the DDL from a virtual cluster instead.
- The sql.error_tip_system_interface.enabled cluster setting enhances errors reported when a user mistakenly uses a storage-level SQL feature within any virtual cluster besides the system virtual cluster. For example, when attempting to modify a cluster setting that was previously at the application level, an error like the following occurs:
  NOTICE: ignoring attempt to modify "kv.rangefeed.enabled" HINT: The setting is only modifiable by the operator. Normally, an error would be reported, but the operation is silently accepted here as configured by "sql.error_tip_system_interface.enabled".
- For a cluster setting that was always system-level, an error like the following occurs:
  ERROR: cannot modify storage-level setting from virtual cluster SQLSTATE: 42501 HINT: Connect to the system interface and modify the cluster setting from there.
The predefined config profiles related to cluster virtualization now automatically set the new sql.restrict_system_interface.enabled and sql.error_tip_system_interface.enabled.
The hidden --secondary-tenant-port-offset option has been removed. Users who were previously using this option should use --internal-rpc-port-range instead.
Added support for automatic finalization of a virtual cluster’s version upgrade. A new setting cluster.auto_upgrade.enabled was added to enable and disable automatic cluster version upgrade (finalization). It will be used in automatic upgrade of both the storage cluster and its virtual clusters.

Command-line changes

has an additional flag that is default off include-running-job-traces that will enable collecting the in-flight traces of traceable jobs, such as , , , and dump them in a jobs/ subdirectory in the zip.

DB Console changes

The will now correctly display timestamps for creation, last modified, and the completed time fields.
The will show the following details when CockroachDB has information on a transaction execution with a 40001 error code and it has captured the conflicting transaction meta details (only available if the transaction had not yet committed at the time of execution). A section called Failed Execution will appear when this information is available and it will contain:
- Blocking transaction execution ID
- Blocking transaction fingerprint ID
- Conflict location
- Database, table, and index names
Added progressive loading functionality to the .

Bug fixes

Fixed a bug in where the primary cluster would not be able to take when a primary cluster node was unavailable.
Fixed a bug in where it was possible to see the contention details of other transactions. Now, CockroachDB will only surface contention details for the current transaction.
will now be satisfied by promoting existing non-voters. Previously, there was a bug where voter constraints were never satisfied due to all existing replicas being considered necessary to satisfy a replica constraint.
Fixed a bug where indoption inside pg_index was not properly encoded causing clients to be unable to decode it as int2vector.
This patch fixes an issue where the fails to honor the statement_timeout session setting when generating constrained index scans for queries with large IN lists or = ANY predicates on multiple index key columns, which may lead to an out of memory condition on the node.
This patch fixes a performance issue in join queries with a LIMIT clause, where the may fail to push a WHERE clause filter into a join due to how the LIMIT operation is internally rewritten. This causes a full scan of the table referenced in the filter.
Fixed a bug that caused internal errors during query optimization in rare cases. The bug has been present since version v2.1.11, but it is more likely to occur in version v21.2.0 and later, though it is still rare. The bug only presents when a query contains min and max .

Performance improvements

This patch adds support for insert fast-path uniqueness checks on tables where the source is a VALUES clause with a single row. This results in a reduction in latency for single-row inserts to REGIONAL BY ROW tables and hash-sharded REGIONAL BY ROW tables with unique indexes.

Contributors

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

Finn Mattis (first-time contributor)
craig

v23.2.0-alpha.3

Release Date: October 10, 2023

Downloads

CockroachDB v23.2.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-v23.2.0-alpha.3.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.3.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-alpha.3.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-alpha.3.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-alpha.3.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.3.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-alpha.3.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.3.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-alpha.3.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-alpha.3.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:

The ARM image is Experimental and not yet qualified for production use and not eligible for support or uptime SLA commitments.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-alpha.3

Backward-incompatible changes

The direct export of traces to Jaeger and the trace.jaeger.agent have been removed. The direct export functionality had been obsoleted since 2022; it stopped working altogether sometime in 2023 with the following error: data does not fit within one UDP packet; size 65006, max 65000, spans NN. Since 2022, Jaeger supports ingestion of traces using OTLP; and CockroachDB has supported emitting traces using OTLP since v22.1. Operators and developers who want to inspect traces are thus invited to use the OTLP protocol instead. The corresponding cluster setting is trace.opentelemetry.collector. For a successful deployment, an intermediate OTLP collector/forwarder should be configured.

You can orchestrate the OpenTeletry collector and Jaeger together using Docker Compose by adapting the following example:

otel-collector:
  image: otel/opentelemetry-collector-contrib
  container_name: otel-collector
  volumes:
    - ./otel-collector-config.yaml:/etc/otelcol-contrib/config.yaml
  ports:
    - 1888:1888 # pprof extension
    - 8888:8888 # Prometheus metrics exposed by the collector
    - 8889:8889 # Prometheus exporter metrics
    - 13133:13133 # health_check extension
    - 4317:4317 # OTLP gRPC receiver
    - 4318:4318 # OTLP http receiver
    - 55679:55679 # zpages extension

jaeger:
  image: jaegertracing/all-in-one
  container_name: jaeger
  ports:
    - "16685:16685"
    - "16686:16686"
    - "14250:14250"
    - "14268:14268"
    - "14269:14269"
    - "6831:6831/udp"
  environment:
    - COLLECTOR_ZIPKIN_HTTP_PORT=9411
    - COLLECTOR_OTLP_ENABLED=true

To configure the otel-collector, you can adapt this example:

receivers:
  otlp: # the OTLP receiver the app is sending traces to
    protocols:
      grpc:
      http:

processors:
  batch:

exporters:
  otlp/jaeger: # Jaeger supports OTLP directly
    endpoint: http://jaeger:4317
    tls:
      insecure: true

service:
  pipelines:
    traces/dev:
      receivers: [otlp]
      processors: [batch]
      exporters: [otlp/jaeger]

To use this configuration, unset Jaeger via SET CLUSTER SETTING trace.jaeger.agent='', and then set the OTLP collector using SET CLUSTER SETTING trace.opentelemetry.collector='localhost:4317'.

Enterprise edition changes

now support the confluent-cloud:// sink scheme. This scheme can be used to connect to Kafka hosted on Confluent Cloud. The scheme functions identically to Kafka, but it has it’s own authentication parameters. Namely, it requires api_key and api_secret to be passed as parameters in the sink URI. They must be URL encoded. An example URI is: 'confluent-cloud://pkc-lzvrd.us-west4.gcp.confluent.cloud:9092?api_key=<KEY>&api_secret=<SECRET>'. By default, the options tls_enabled=true, sasl_handshake=true, sasl_enabled=true, and sasl_mechanism=PLAIN are applied. For more information about authenticating with Confluent Cloud, see https://docs.confluent.io/platform/current/security/security_tutorial.html#overview. The sink scheme still supports non-authentication parameters such as topic_name and topic_prefix. It also supports the standard Kafka changefeed options (ex. kafka_sink_config ).

SQL language changes

The option strip_localities, which was added in, has been renamed to remove_regions. This option will lead to a “region-less restore”; it is used to strip the locality and region information from a backup when there are mismatched cluster regions between the backup’s cluster and the target cluster. Note that a restore using this option will fail if the backup’s cluster had table localities. This is because the RESTORE statement has a contract that all tables must be available to serve writes once it finishes.
Added initial support for executing the PLpgSQL OPEN statement, which allows a PLpgSQL routine to create a . Currently, opening bound or unnamed cursors is not supported. In addition, OPEN statements cannot be used in a routine with an exception block.
Added support for declaring bound , which associate a query with a cursor in a PLpgSQL routine before it is opened.
The SELECT FOR SHARE and SELECT FOR KEY SHARE statements previously did not acquire any locks. Users issuing these statements would expect them to acquire shared locks (multiple readers allowed, but no writers). This patch switches over the behavior to acquire such read locks when the user has selected the . For serializable transactions, we default to the previous behavior, unless the enable_shared_locking_for_serializable is set to true.
When a PLpgSQL exception handler catches an error, it now rolls back any changes to database state that occurred within the block. Exception blocks are not currently permitted to catch and errors.
Added support for unnamed PLpgSQL , which generate a unique name when no cursor name was specified.
Fixed a bug that caused CockroachDB to stop collecting new statistics about and .
Make the max_event_frequency visible for public documentation and usage. This is the maximum event frequency at which we sample executions for telemetry.

Operational changes

Added the following for proposals and reproposals: raft.commands.proposed, raft.commands.reproposed.unchanged, and raft.commands.reproposed.new-lai.
Removed the spanconfig.store.enabled and the ability to use the COCKROACH_DISABLE_SPAN_CONFIGS environment variable.
Renamed the fluent.sink.conn.errors to log.fluent.sink.conn.errors. The addition of the log. prefix was to better group together logging-related metrics. The behavior and purpose of the metric remains unchanged.
Set the Metric Type metadata on the log.fluent.sink.conn.errors. Previously, the Metric Type was incorrectly left unset. Note that this is an update to the metric’s metadata; the behavior and purpose of the metric remains unchanged.
Added a new log.buffered.messages.dropped. Buffered network logging sinks have a max-buffer-size attribute, which determines, in bytes, how many log messages can be buffered. Any fluent-server or http-server log sink that makes use of a buffering attribute in its configuration (enabled by default) qualifies as a buffered network logging sink. If this buffer becomes full, and an additional log message is sent to the buffered log sink, the buffer would exceed this max-buffer-size. Therefore, the buffered log sink drops older messages in the buffer to handle, in order to make room for the new. log.buffered.messages.dropped counts the number of messages dropped from the buffer. Note that the count is shared across all buffered logging sinks.
Added the log.messages.count. This metric measures the count of messages logged on the node since startup. Note that this does not measure the fan-out of single log messages to the various configured . This metric can be helpful in understanding log rates and volumes.
Added the file-based-headers field found in the http-defaults section of the log config, which accepts ‘key-filepath’ pairs. This allows values found at filepaths to be updated without restarting the cluster by sending SIGHUP to notify that values need to be refreshed.
Added the kv.snapshot.ingest_as_write_threshold, which controls the size threshold below which snapshots are converted to regular writes. It defaults to 100KiB.

Cluster virtualization

The name of the virtual cluster that the SQL client is connected to can now be inspected via the SQL virtual_cluster_name.

Command-line changes

The following have been renamed; the previous names remain available for backward-compatibility.

Previous name	New Name
`server.shutdown.drain_wait`	`server.shutdown.initial_wait`
`server.shutdown.lease_transfer_wait`	`server.shutdown.lease_transfer_iteration.timeout`
`server.shutdown.query_wait`	`server.shutdown.transactions.timeout`
`server.shutdown.connection_wait`	`server.shutdown.connections.timeout`
`server.shutdown.jobs_wait`	`server.shutdown.jobs.timeout`

DB Console changes

Fixed an error on the when there was a workload, and then the workload stopped so that no queries ran against the database in the last hour.
On the , now the information about which metric is used to create each chart is available on the chart’s tooltip.

Bug fixes

Fixed the error message that is returned when the user attempts to drop an value that is used at least twice in an column.
Added a check for values before using mean on the , fixing a crash.
Fixed the metric name for Schema Registry Registrations on the .
Fixed a panic that could occur if a query used a larger than 2^31-1 bytes. This was triggered by attempting to a 2.7 GiB CSV file.
Fixed a bug where atttypmod in pg_attribute was not populated for / types, which meant that ORMs could not know the precision of these types properly.

Contributors

This release includes 130 merged PRs by 43 authors.

v23.2.0-alpha.2

Release Date: October 2, 2023

Downloads

CockroachDB v23.2.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-v23.2.0-alpha.2.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.2.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-alpha.2.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-alpha.2.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-alpha.2.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.2.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-alpha.2.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.2.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-alpha.2.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-alpha.2.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:

The ARM image is Experimental and not yet qualified for production use and not eligible for support or uptime SLA commitments.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-alpha.2

Security updates

The SIGHUP signal now clears the cached expiration times for that are reported by the security.certificate.expiration.client metric.

General changes

Increased the maximum permitted value of the COCKROACH_RPC_INITIAL_WINDOW_SIZE environment variable to 64MB. In conjunction with tuning your operating system’s maximum TCP window size, this can increase the throughput that Raft replication can sustain over high latency network links.

SQL language changes

The discard is now limited to once per minute by default. The message now includes both the number of transactions and the number of statements that were discarded.
The kv.rangefeed.enabled no longer controls access to RANGEFEED SQL commands. Instead, use feature.changefeed.enabled.
SQL commands that were previously limited to the admin can now be used by users with the VIEWCLUSTERMETADATA or REPAIRCLUSTERMETADATA system privilege, depending on whether the operation is read-only or modifies state.
Added a last_error column to the cluster_execution_insights, node_execution_insights, cluster_txn_execution_insights, and node_txn_execution_insights tables. These columns contain error messages for failed executions.
The new backup option updates_cluster_monitoring_metrics tracks the timestamp of the last backup failure due to a KMS error. This option is disabled by default.
The new restore option strip_localities optionally strips the locality information from a backup when restoring to a cluster with different regions than the source cluster.

Restoring a cluster or database that contains regional-by-row tables, or restoring a regional-by-row table, requires you to modify the database:

To restore a cluster with regional-by-row tables, you must drop the zone config of the database, then drop the type d.public.crdb_internal_region.
To restore a database that contains regional-by-row tables, or to restore a regional-by-row table, you must drop the type d.public.crdb_internal_region.
You must alter the crdb_region column to set the default region for newly-written rows.
You must discard the previous zone config, which contains outdated information, such as that related to the partitions and constraints after the restore. This column specifies each row’s home region and is a prefix to the table’s primary key. Stripping localities does not modify this column, because it would require the entire table to be written.

This change is part of a larger effort, and this feature is subject to change. #110606

Added a check to disallow queries that use predicate locking, since explicit uniqueness checks are not yet supported under Read Committed isolation. INSERT, UPDATE, and UPSERT statements against some REGIONAL BY ROW tables will fail under Read Committed isolation with the following error:

  unimplemented: explicit unique checks are not yet supported under read committed isolation SQLSTATE: 0A000

For more details about which REGIONAL BY ROW tables are affected, refer to Issue #110873. #110879 - The created field produced by SHOW STATISTICS has been updated from TIMESTAMP to TIMESTAMPTZ. Statistic creation times are now displayed in the session time zone if it is set.

Operational changes

Removed the node-level engine.stalls timeseries metric. This metric has not been updated for several releases.

DB Console changes

The legend is now always displayed on charts in DB Console Metrics pages. In addition, when you select an item from the legend that represents a single line in the chart, that line is selected in the chart.
When collecting a , you can now filter by a specific or collect diagnostics for all plan gists.
and detail pages now include an Error Message row. Users with the VIEWACTIVITY can view the full error message, and users with the VIEWACTIVTYREDACTED system privilege can view the redacted error message. If a user has both privileges, VIEWACTIVITYTREDACTED ` takes precedence.
A new dashboard in the tracks how often distributed queries with errors were rerun using the “rerun as local” mechanism, as well as how often those reruns failed. the number of times distributed queries that resulted in errors were rerun as local as well as when those reruns failed. The “rerun as local” mechanism is new in v23.2 and is enabled by default. For more information, contact your Cockroach Labs account representative.
The DB Console Insights page now shows the error message when a transaction fails at the COMMIT stage.
The now includes the following graphs to monitor :
- IO Overload - Charts normalized metric based on admission control target thresholds. Replaces LSM L0 Health graph which used raw metrics.
- KV Admission Slots Exhausted - Replaces KV Admission Slots graph.
- Flow Tokens Wait Time: 75th percentile - Use to monitor the new replication admission control feature.
- Requests Waiting For Flow Tokens - Use to monitor the new replication admission control feature.
- Blocked Replication Streams - Use to monitor the new replication admission control feature.

Bug fixes

Fixed a race condition in the that could result in a failed SQL request when the request could have been successfully retried.
Fixed a bug where a command with an IDENTITY column did not properly propagate the type of the column into the sequence.
Fixed a panic when decoding a gist in a foreign database that does not contain a table referred to by the gist.
A synthetic dropped column have been added to the pg_attribute table. This column tracks the attribution numbers for dropped attributions, to work around issues with ORMs that are not designed to handle gaps in attribution numbering in the pg_attribute table.
Fixed a rare internal error in the unnest and information_schema._pg_expandarray where passed string arguments could be cast to an array.
External connection URLs now accept the scheme azure-blob for connections to Azure Blob Storage and the scheme azure-kms for connections to Azure KMS. For backward compatibility, schemes azure and azure-storage schemes continue to work for connections to Azure Blob Storage.
Fixed a bug where vectorized COPY FROM could produce a plan with more than one RenderNodes, when only zero or one should be allowed. This could result in multiple render nodes in a table with a hash sharded primary key.
Fixed a bug in DB Console’s Statement Diagnostic page that could cause the page to crash if the response was larger than 50 KB. The page now keeps pulling results until no maximum size errors are encountered.
Fixed a bug where DB Console instances proxied at different subpaths that use OIDC pointed to an incorrect relative OIDC login path.
Fixed a bug where changing the setting server.telemetry.hot_ranges_stats.interval had no effect.

Performance improvements

Fixed a performance bug that could result in rewriting a 128-MB file each time a store file is created, renamed, or removed when is enabled on a large store with many small files.
Improved compaction heuristics to mitigate read amplification growth and admission control throttling when processing large deletes, such as during node decommissioning, replica rebalancing, or when dropping tables.

Contributors

This release includes 157 merged PRs by 54 authors.

v23.2.0-alpha.1

Release Date: September 26, 2023

Downloads

CockroachDB v23.2.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-v23.2.0-alpha.1.linux-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.1.linux-amd64.tgz (SHA256)
Linux	ARM	cockroach-v23.2.0-alpha.1.linux-arm64.tgz (Experimental) (SHA256)	cockroach-sql-v23.2.0-alpha.1.linux-arm64.tgz (Experimental) (SHA256)
Mac (Experimental)	Intel	cockroach-v23.2.0-alpha.1.darwin-10.9-amd64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.1.darwin-10.9-amd64.tgz (SHA256)
Mac (Experimental)	ARM	cockroach-v23.2.0-alpha.1.darwin-11.0-arm64.tgz (SHA256)	cockroach-sql-v23.2.0-alpha.1.darwin-11.0-arm64.tgz (SHA256)
Windows (Experimental)	Intel	cockroach-v23.2.0-alpha.1.windows-6.2-amd64.zip (SHA256)	cockroach-sql-v23.2.0-alpha.1.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:

The ARM image is Experimental and not yet qualified for production use and not eligible for support or uptime SLA commitments.
The Intel image is Generally Available for production use.

To download the Docker image:

docker pull cockroachdb/cockroach-unstable:v23.2.0-alpha.1

Backward-incompatible changes

The pre-v23.1 output produced by SHOW RANGES, crdb_internal.ranges, and crdb_internal.ranges_no_leases was deprecated in 23.1 and is now replaced by default with output that’s compatible with coalesced ranges (i.e., ranges that pack multiple tables/indexes/partitions into individual ranges). See the for SHOW RANGES for more details.
When a deployment is configured to use a time zone (new feature) for log file output using formats crdb-v1 or crdb-v2, it becomes impossible to process the new output log files using the from a previous version. The newest cockroach debug merge-logs code must be used instead.
When customizing the , the special sequence %M now expands to the full host name instead of the combination of host name and port number. To include the port number explicitly, use %>. The special sequence %m now expands to the host name up to the first period.
The command stores data retrieved from SQL tables in the remote cluster using the TSV format by default.
The will only apply to newly created changefeeds in v23.2. For existing changefeeds, you can set the option so that changefeeds do not experience infinite retries and accumulate protected change data. You can use the statement to add protect_data_from_gc_on_pause to existing changefeeds.
The changefeed.new_pubsub_sink_enabled cluster setting is now enabled by default, which improves changefeed throughput. With this setting enabled, the top-level fields in JSON-encoded messages are capitalized: {Key:..., Value:..., Topic:...}. After upgrading to CockroachDB v23.2, you may need to reconfigure downstream systems to parse the new message format. If you disable this setting, changefeeds emitting to Pub/Sub sinks with JSON-encoded events have the top-level message fields all lowercase: {key:..., value:..., topic:...}.

Security updates

Users who have the can now grant and revoke role membership in any non-admin role. This change also removes the , which was added in v23.1. In v23.2, the cluster setting is effectively always true.

General changes

You can now set command arguments using the COCKROACH_ARGS environment variable.
Extended the with a storeMetrics field.
CockroachDB would previously use separate for each table, index, or partition. This is no longer true. It is possible now to have multiple tables, indexes, and partitions get packed into the same range. For users with many of these schema objects, this will reduce the total range count in their clusters. This is especially true if individual tables, indexes, or partitions are smaller than the default configured maximum range size (controlled using , specifically the range_max_bytes parameter). We made this change to improve scalability with respect to the number of schema objects, since the underlying range count is now no longer a bottleneck. Users upgrading from v22.2, when finalizing their upgrade, may observe a round of range merges and snapshot transfers (to power said range merges) as a result of this change. If users want to opt-out of this optimization, they can configure the following cluster setting: SET CLUSTER SETTING spanconfig.storage_coalesce_adjacent.enabled = false;
will now use a new internal implementation for writing Parquet files using the Parquet spec version 2.6. There should be no significant impact to the structure of files being written. There is one minor change: all columns written to Parquet files will be nullable (i.e., the Parquet repetition type is OPTIONAL ).
for CockroachDB now rely on GEOS 3.11 instead of GEOS 3.8.
CockroachDB no longer distributes libgeos for the experimental . Users can instead install GEOS directly from the source: https://libgeos.org/usage/download/.
The Formatting of byte figures in Pebble logs has been improved. Tools that parse these logs might need updating.
CockroachDB now has a new , --experimental-shared-storage to rebalance data faster from node to node.
Fixed a bug where, internally, if we print a 0 decimal with a very low exponent we use excessive memory. This is not possible when using the type, but may be possible when using crdb_internal functions.

Enterprise edition changes

The Compression and RequiredAcks options are now case-insensitive.
emit significantly fewer duplicate messages during node and cluster restarts.
CockroachDB has a new changefeed.protect_timestamp.max_age setting (by default 4 days), which will cancel running changefeed jobs if they fail to make forward progress for a period of time. This setting is used if the explicit gc_protect_expires_after option is not set. In addition, the protect_data_from_gc_on_pause option has been deprecated. This option is no longer needed since changefeed jobs always protect data.
Changefeeds now officially support the Parquet format using specification version 2.6. It is only usable with the . The syntax to use Parquet is: CREATE CHANGEFEED FOR foo INTO... WITH format=parquet. It supports all standard changefeed options and features including CDC transformations, except it does not support the topic_in_value option.
Changefeeds that create files over an HTTP connection may now be specified using INTO 'file-https://' to disambiguate with webhook-https.
The pgcrypto encrypt, encrypt_iv, decrypt, and decrypt_iv are now implemented. These functions require an enterprise license on a CCL distribution.
CockroachDB now paces the rangefeed goroutine creation rate to improve scheduler latency. This improves observability by adding an additional column in the crdb_internal.active_rangefeed table to indicate if the range is currently in catchup scan mode.

SQL language changes

Fixed the helper message on SQL statements to include the optional FROM cause.
CockroachDB now supports enabling forward and ordering on values.
Added a new column visibility to crdb_internal.table_indexes and information_schema.statistics. Also added a new column visibility to the output of following SQL statements:
SHOW INDEX FROM (table_name);
SHOW INDEXES FROM (table_name);
SHOW KEYS FROM (table_name);
SHOW INDEX FROM DATABASE (database_name);
SHOW INDEXES FROM DATABASE (database_name);
SHOW KEYS FROM DATABASE (database_name);
This new column contains a floating point number specifying the level of visibility of the index, from 0 (not visible) to 1 (fully visible). If the value is between 0 and 1, the index will be visible to the corresponding fraction of queries.
ALTER INDEX... VISIBILITY... is now supported. It can change an index visibility to any visibility between 0.0 and 1.0. Visibility 0.0 means the index is not visible to the , while visibility 1.0 means the index is fully visible. A value in the range between 0.0 and 1.0 means the index will be visible to the corresponding fraction of queries.
CockroachDB now has support for non-aggregate expressions involving columns outside of the grouping columns when the grouping columns include all key columns of a unique index and those key columns are not nullable.
CockroachDB now supports and . This allows users to set the index visibility to any visibility between 0.0 and 1.0. Visibility 0.0 means the index is not visible to the optimizer, while visibility 1.0 means the index is fully visible. A value in the range between 0.0 and 1.0 means the index will be visible to the corresponding fraction of queries.
now supports DESC order primary key columns.
Added the ST_BdPolyFromText which copies the behavior of the PostGIS function. Takes in only a multilinestring geometry and returns a polygon. It will return an error if anything other than a multilinestring is input, and will return an error if internally a multipolygon is created for some reason. NULL inputs also return NULL.
now shows the schedule options with which the schedules were created. SHOW SCHEDULES FOR BACKUP additionally shows if the schedule is a full or incremental backup schedule.
You can no longer use PREPARE with statements. Previously, this was allowed, but attempts to EXECUTE the prepared EXPLAIN ANALYZE statements would result in an error.
ttl_expiration_expression now allows stable operators and functions. This allows intervals to be directly added to TIMESTAMPTZ expressions. See https://www.postgresql.org/docs/15/xfunc-volatility.html.
CockroachDB now allows INSERT commands in statement bodies.
CockroachDB now allows UPDATE and UPSERT commands in UDF statement bodies.
The READ COMMITTED is now supported. It can be used in the following ways:
- When starting a transaction, use BEGIN ISOLATION LEVEL READ COMMITTED.
- After starting a transaction, but before performing reads or writes, use SET TRANSACTION ISOLATION READ COMMITTED.
- Configure it as the default isolation level using the default_transaction_isolation session variable. To see the isolation level of the currently running transaction, use either SHOW TRANSACTION ISOLATION LEVEL or SHOW transaction_isolation.
Added version gates which require all nodes in a given cluster to have a minimum binary version number, which in turn is required for creating forward indexes on JSON columns and for ordering JSON columns.
CockroachDB now allows DELETE commands in UDF statement bodies.
Added a new cluster setting sql.auth.public_schema_create_privilege.enabled which controls whether users receive on the public schema or not. The setting applies at the time that the public schema is created, which happens whenever a database is created. The setting is true by default.
statements now have descriptor, index, column, constraint, and other ID values decorated with names when available. There is now also a new EXPLAIN (DDL, SHAPE) statement that provides information on costly operations planned by the declarative schema changer, like which index backfills and validations will get performed.
A new statistic KV pairs read is now exposed on output in some cases (when this number is different from the KV rows read statistic or when the VERBOSE option is requested). This new statistic is also added to the telemetry sampled query events.
The KV rows read statistic in EXPLAIN ANALYZE output has been renamed to KV rows decoded to better reflect its meaning.
Table names are now allowed in SELECT lists inside and UDF definitions.
for a backup job will regenerate the DistSQL plan diagram with per-node and per-processor progress information. This will help users better understand the state of a running backup job.
The crdb_internal.node_transactions and crdb_internal.cluster_transactions tables now have columns for isolation_level, priority, and quality_of_service.
The command will now emit span statistics when the DETAILS option is specified. The statistics are included in a new column named span_stats, as a JSON object. The statistics are calculated for the identifier of each row. SHOW RANGES WITH DETAILS will compute span statistics for each range. SHOW RANGES WITH TABLES, DETAILS will compute span statistics for each table, and so on. The span_stats JSON object has the following keys:
- approximate_disk_bytes
- [key|val|sys|live|intent]_count
- [key|val|sys|live|intent]_bytes approximate_disk_bytes is an approximation of the total on-disk size of the given object. key_count is the number of meta keys tracked under key_bytes. key_bytes is the number of bytes stored in all non-system point keys, including live, meta, old, and deleted keys. Only meta keys really account for the “full” key; value keys only for the timestamp suffix. val_count is the number of meta values tracked under val_bytes. val_bytes is the number of bytes in all non-system version values, including meta values. sys_count is the number of meta keys tracked under sys_bytes. sys_bytes is the number of bytes stored in system-local key-value pairs. This tracks the same quantity as (key_bytes + val_bytes), but for system-local metadata keys (which aren’t counted in either key_bytes or val_bytes). live_count is the number of meta keys tracked under live_bytes. live_bytes is the number of bytes stored in keys and values which can in principle be read by means of a Scan or Get in the far future, including intents but not deletion tombstones (or their intents). Note that the size of the meta key-value pair (which could be explicit or implicit) is included in this. Only the meta key-value pair counts for the actual length of the encoded key (regular pairs only count the timestamp suffix). intent_count is the number of keys tracked under intent_bytes. It is equal to the number of meta keys in the system with a non-empty Transaction proto. intent_bytes is the number of bytes in intent key-value pairs (without their meta keys).
Introduced the pg_lsn data type, which is used to store the lsn associated with replication.
Users now can issue one with a combination of any number of ADD COLUMN, any number of DROP COLUMN, one ALTER PRIMARY KEY, and any number of ADD CONSTRAINT clauses. For example, with this PR, we now support statements like:
CREATE TABLE t (i INT PRIMARY KEY, j INT NOT NULL, k INT NOT NULL); ALTER TABLE t ADD COLUMN p INT DEFAULT 30, ALTER PRIMARY KEY USING COLUMNS (j), DROP COLUMN k, ADD CHECK (i > 0);
Added the ability to add numeric values to LSNs, or sub a decimal value from a LSN.
Implemented the pg_lsn - pg_lsn = decimal built-in function, which subtracts 2 LSNs to return a decimal.
Added limited support for scalar PL/pgSQL functions. Supported statements are variable declarations, variable assignments, IF statements, simple LOOP statements (with no conditions), EXIT and CONTINUE statements, and RETURN statements.
Implemented the spatial built-in ST_AsMVTGeom.
Pg_class’s relreplident field was previously unpopulated. It is now populated with d for all tables (as each table has a primary key) and n otherwise.
Added the pg_sequence_last_value built-in function, which returns the last value generated by the sequence.
can now be passed a WITH EXECUTION LOCALITY option similar to , to restrict execution of the job to nodes with matching localities.
Added the REPLICATION user role option, which allows a user to use the streaming replication protocol. There is a corresponding .
A new view-only , max_connections was added. This can be used with SHOW to view the maximum amount of non-superuser SQL connections allowed at a given time.
Added the nameconcatoid built-in function, which concatenates a name with an OID.
The pg_catalog.pg_language table is now populated with data about the languages used to define functions.
The information_schema.routines view is now populated with information about functions.
The information_schema.parameters table is now populated with information about function parameters.
Added support for the PLpgSQL RAISE statement, which allows sending notices to the client and raising errors. Currently the notice is only sent to the client. Support for logging notices will be added in a future release.
The public pseudo-role now receives the EXECUTE privilege by default for all user-defined functions that are created. This can be adjusted by using ALTER DEFAULT PRIVILEGES.
The crdb_interanal.node_statement_statistics table redacts the error message if the user has the VIEWACTIVITYREDACTED privilege, and does not redact the error message if the user has VIEWACTIVITY. If the user has both, VIEWACTIVITYREDACTED takes precedence and the last error is redacted.
The crdb_internal.cluster_locks table now has a isolation_level column indicating the isolation level.
In CommonSQLExecDetails, which is emitted as part of the SQL audit logs, SQL exec logs, and telemetry events, there is a new field: StmtPosInTxn. It represents the statement’s index in the transaction, starting at 1.
cluster_logical_timestamp now returns an error when called at isolation levels lower than SERIALIZABLE.
EXPLAIN ANALYZE output now includes:
- The isolation level of the statement’s transaction.
- The priority of the statement’s transaction.
- The quality of service level of the statement’s transaction.
Added a new session variable, enable_implicit_fk_locking_for_serializable, which controls locking during foreign key checks under SERIALIZABLE isolation. With this set to true, foreign key checks of the referenced (parent) table, such as those performed during an INSERT or UPDATE of the referencing (child) table, will lock the referenced row using SELECT FOR SHARE locking. This is somewhat analogous to the existing enable_implicit_select_for_update variable but applies to the foreign key checks of a mutation statement instead of the initial row fetch. Under weaker isolation levels such as read committed, SELECT FOR SHARE locking will always be used to ensure the database maintains the foreign key constraint, regardless of the current setting of enable_implicit_fk_locking_for_serializable.
Add a new session variable, enable_durable_locking_for_serializable, which controls locking durability under SERIALIZABLE isolation. With this set to true, SELECT FOR UPDATE locks, SELECT FOR SHARED locks, and constraint check locks (e.g., locks acquired during foreign key checks if enable_implicit_fk_locking_for_serializable is set to true) will be guaranteed-durable under serializable isolation, meaning they will always be held to transaction commit. These locks are always guaranteed-durable under weaker isolation levels. By default, under serializable isolation these locks are best-effort rather than guaranteed-durable, meaning in some cases (e.g., leaseholder transfer, node loss, etc.) they could be released before the transaction commits. Serializable isolation does not rely on locking for correctness, only using it to improve performance under contention, so this default is a deliberate choice to avoid the performance overhead of lock replication.
The cluster setting server.cpu_profile.enabled has been removed. server.cpu_profile.cpu_usage_combined_threshold can enable and disable CPU profiling.
Added support for CONSTANT variable declarations in PLpgSQL routines. Any assignment to a variable declared with the CONSTANT keyword will raise a compile-time error.
Added a new syntax to SHOW DEFAULT PRIVILEGES, SHOW DEFAULT PRIVILEGES FOR GRANTEE <grantee>, that shows the default privileges that a grantee received.
The Statement diagnostics feature has been extended to support collecting a bundle for a particular plan. Namely, the existing fingerprint-based matching has been extended to also include plan-gist-based matching. Such bundles will miss a couple of things: plan.txt file as well as the tracing of the optimizer. At the moment, the feature is only exposed via an overload to the crdb_internal.request_statement_bundle built-in function. We now also support “anti-match”: collecting a bundle for any plan other than the provided plan gist.
’s timestamp columns are now TIMESTAMPTZ, meaning they render in the session offset.
Attempting to when safe updates are enabled (sql_safe_updates = on) now additionally warns users that indexes referencing that column will be automatically dropped.
NOTICEs are now emitted for each index dropped by an ALTER TABLE... DROP COLUMN... statement.
SHOW JOBS now returns times (created, last_run, and so on) using the TIMESTAMPTZ column type instead of the TIMESTAMP type, meaning they are now rendered using the session offset.
Added a cluster setting sql.schema.force_declarative_statements to enable/disable DDL in the .
Added the new built-in functions workload_index_recs() and workload_index_recs(TIMESTAMPTZ), which return workload level index recommendations (columns of string, each string represent an index recommendation) from statement level index recommendations (as candidates) in system.statement_statistics. If the TIMESTAMPTZ is given, it will only consider those candidates generated after that TIMESTAMPTZ value.
Added support for specifying PLpgSQL IF statements with ELSIF branches.
The admin API database details endpoint now returns authoritative range statistics.
Added the max_retries_for_read_committed session variable. It defaults to 10, and determines the number of times an individual statement in an explicit READ COMMITTED transaction will be retried if it encounters a retryable transaction error.
Added support for the execution of PLpgSQL functions with exception blocks. This allows a PLpgSQL function to catch and handle arbitrary errors it encounters during its execution.
Added the built-in functions bitmask_or, bitmask_and and bitmask_xor for variable-length input bitwise OR, AND, and XOR operations, respectively.
The oidvectortypes built-in has been implemented, which can format oidvector.
Added support for executing SQL statements directly within PLpgSQL routines. Note that this currently only applies to the subset of statements that can be executed within SQL UDFs, so CREATE TABLE is not supported, for example. INTO syntax is also supported. For example, SELECT * INTO a, b FROM xy;.
A SQL client can now request strict atomicity for mixed DDL/DML transactions with the new session variable strict_ddl_atomicity, which defaults to false. When this variable is set to true, CockroachDB will refuse to accept processing those specific DDL statements inside BEGIN...COMMIT for which it cannot guarantee atomic processing (other DDL statements are still allowed). Note that schema changes implicit in certain operations (e.g., IMPORT) are not protected via the new mechanism and can still fail with XXA00 errors.
Fixed an issue where the UI was missing query text and details on the SQL Activity if there were more than 500 transactions or statements. The statement_activity table now includes all statements for a transaction that are in the transaction_activity table.
Added the . Users with this privilege have SELECT privileges for all tables in the system database.
The statement_activity and transaction_activity tables column execution_total_cluster_seconds is now accurate. The combinedstmts endpoint returns the correct value for the StmtsTotalRuntimeSecs and TxnsTotalRuntimeSecs properties.
The persistedsqlstats table maximum size check is now done once an hour instead of every 10 minutes. This reduces the risk of serialization errors on the statistics tables.
The deprecated session variable idle_in_session_timeout is now hidden from introspection. It was previously changed to idle_session_timeout.
The session variable ssl is now visible through introspection for better compatibility with PostgreSQL.
The session variable session_user is now invisible through introspection, in a way consistent with session_authorization and PostgreSQL.
There is now a CREATEROLE system privilege, which is analogous to the existing CREATEROLE role option, but can also be inherited by role membership.
Added the gen_random_bytes built-in function, which generates cryptographically secure random bytes.
The hash function used by was changed to mod(fnv32(md5(crdb_internal.datums_to_bytes(columns))), bucket_count). Previously, it did not use md5. This change was made to enhance the uniformity of bucket distribution in cases when the bucket count is a power of 2, and the columns being sharded have numerical properties that make the fnv32 function return values with a non-uniformly distributed modulus.
New datetime built-ins (make_date, make_timestamp, and make_timestamptz) have been added, allowing for the creation of timestamps, timestamps with time zones, and dates. In addition, date_trunc now allows for a timestamp to be truncated in a specified timezone (to a specified precision).
There is now a CREATELOGIN system privilege, which is analogous to the existing CREATELOGIN role option, but can also be inherited by role membership.
There is now a CREATEDB system privilege, which is analogous to the existing CREATEDB role option, but can also be inherited by role membership.
There is now a CONTROLJOB system privilege, which is analogous to the existing CONTROLJOB role option, but can also be inherited by role membership.
The persistedsqlstats table maximum size check is now done once an hour instead of every 10 minutes. This reduces the risk of serialization errors on the statistics tables.
The new sql.txn.read_committed_syntax.enabled, controls whether transactions run under READ COMMITTED or SERIALIZABLE isolation. It defaults to false. When set to true, the following statements will configure transactions to run under READ COMMITTED isolation:
- BEGIN TRANSACTION ISOLATION LEVEL READ COMMITTED
- SET TRANSACTION ISOLATION LEVEL READ COMMITTED
- SET default_transaction_isolation = 'read committed'
- SET SESSION CHARACTERISTICS AS TRANSACTION ISOLATION LEVEL READ COMMITTED
The sql.metrics.statement_details.gateway_node.enabled now defaults to false, to reduce the number of rows generated in SQL Statistics pages.
The default value for the ttl_job_cron table storage parameter is now @daily rather than @hourly. This parameter controls the default recurrence of the row-level TTL job. As part of this change, the output of the SHOW CREATE TABLE statements now include the ttl_cron_job parameter only if it is explicitly set.

Operational changes

Removed a timeseries metric that has not been reported for several versions.
Added two new metrics, range.snapshots.(send|recv)-queue-bytes, to track the total size of all snapshots waiting in the snapshot queue.
Exposed a new metric storage.compactions.duration, computed by the storage engine, that provides the cumulative time the storage engine has spent in compactions. This duration may exceed time elapsed, because of concurrent compactions, and may be useful in monitoring compaction concurrency.
Two new store metrics, range.snapshots.cross-region.sent-bytes and range.snapshots.cross-region.rcvd-bytes, were added to track the aggregate of snapshot bytes sent from and received at a store across different regions. Note that these metrics require the nodes’ localities to include a “region” tier key. If a node lacks this key but is involved in cross-region batch activities, an error message will be logged.
Added new store metrics to track the aggregate of snapshot bytes sent from and received at a store across different zones.
- range.snapshots.cross-zone.sent-bytes
- range.snapshots.cross-zone.rcvd-bytes For accurate metrics, follow these recommendations: - Configure region and zone tier keys consistently across nodes. - Within a node locality, ensure unique region and zone tier keys. - Maintain consistent configuration of region and zone tiers across nodes.
Added new store metrics:
- raft.rcvd.bytes
- raft.sent.bytes
- raft.rcvd.cross_region.bytes
- raft.sent.cross_region.bytes
- raft.rcvd.cross_zone.bytes
- raft.sent.cross_zone.bytes
Added new DistSender metrics:
- distsender.batch_requests.replica_addressed.bytes
- distsender.batch_responses.replica_addressed.bytes
- distsender.batch_requests.cross_region.bytes
- distsender.batch_responses.cross_region.bytes
- distsender.batch_requests.cross_zone.bytes
- distsender.batch_responses.cross_zone.bytes.
Added new Node metrics:
- batch_requests.bytes
- batch_responses.bytes
- batch_requests.cross_region.bytes
- batch_responses.cross_region.bytes
- batch_requests.cross_zone.bytes
- batch_responses.cross_zone.bytes
Added new RPC metrics to help you to diagnose RPC connection issues:
- grpc.connection.avg_round_trip_latency
- rpc.connection.failures
- rpc.connection.healthy
- rpc.connection.healthy_nanos
- rpc.connection.heartbeats
- rpc.connection.unhealthy
- rpc.connection.unhealthy_nanos
Added a new metric changefeed.lagging_ranges that shows the number of ranges which are behind in changefeeds. This metric can be used with the metrics_label changefeed option. Added a new changefeed option lagging_ranges_threshold, which is the amount of time a range needs to be behind to be considered lagging. By default this is 3 minutes. Added a new option lagging_ranges_polling_interval, which controls how often the lagging ranges calculation is done. This setting defaults to polling every 1 minute. Note that polling adds latency to the metric being updated. For example, if a range falls behind by 3 minutes, the metric may not update for an additional minute afterwards. Also note that ranges undergoing an initial scan for longer than the threshold are considered to be lagging. Starting a changefeed with an initial scan on a large table will likely increment the metric for each range in the table. However, as ranges complete the initial scan, the number of ranges will decrease.
A histogram metric raft.replication.latency was added. It tracks the time between evaluation and application of the command. This includes time spent in the quota pool, in replication (including re-proposals) as well as log application, but notably not sequencing latency (i.e., contention and latch acquisition).
The default Raft scheduler concurrency cap has been increased from 96 to 128 workers, scaling with 8 workers per CPU up to the cap. The scheduler concurrency can be controlled using the COCKROACH_SCHEDULER_CONCURRENCY environment variable.
The new cluster setting server.hot_ranges_request.node.timeout controls the maximum amount of time that a hot ranges request will spend waiting for a node to provide a response. It defaults to 5 minutes. To disable timeouts, set it to 0.
Two new cluster settings control whether intent resolution is subject to admission control: kv.intent_resolver.send_immediately.bypass_admission_control.enabled and kv.intent_resolver.batch.bypass_admission_control.enabled.
The new cluster setting admission.l0_min_size_per_sub_level reduces the probability of throttling when there is a sequence of small memtable flushes or small files ingested into L0.
The new cluster setting kv.intent_resolver.batcher.in_flight_backpressure_limit.enabled controls whether an in-flight RPC limit is enforced on intent resolution RPCs. It defaults to false.
now skips contacting the ranges for tables on which exclude_data_from_backup is set, and can thus succeed even if an excluded table is unavailable.
Span stats requests will return a partial result if the request encounters any errors. Errors that would have previously terminated the request are now included in the response.
The rangefeed closed timestamp interval controlled by kv.rangefeed.closed_timestamp_refresh_interval now defaults to 3 seconds. This affects how often rangefeeds emit resolved timestamps, and thus how often changefeeds can emit checkpoints. Previously, its default value of 0 would fall back to kv.closed_timestamp.side_transport_interval, which defaults to 200 milliseconds. Users who rely on the setting kv.closed_timestamp.side_transport_interval to control the rangefeed closed timestamp interval should make sure they either set kv.rangefeed.closed_timestamp_refresh_interval to 0 to retain the old behavior (preferably before upgrading), or to an appropriate value.
The default value of timeout for http-servers has been changed from 0 (i.e., “no timeout”) to 2s. This is reflected in the http-defaults section of the log configuration. Users still maintain the ability to override the timeout, or disable it by explicitly setting it to 0 (e.g. timeout: 0).
metrics now include a changefeed.checkpoint_progress metric which is similar to changefeed.max_behind_nanos but supports metrics labels, as well as a changefeed.aggregator_progress metric which can track the progress of individual aggregators (the lowest timestamp for which all aggregators with the label have emitted all values they’re responsible for).
Added support for Prometheus native histograms behind an environment variable flag.
Requests for database details or table details from the UI, or usages of [SHOW RANGES WITH DETAILS]/docs/v23.2/show-ranges.html are no longer subject to errors if the number of requested spans is too large.
The command now has an option to omit goroutine stack dumps. This impacts the creation of nodes/*/stacks.txt and nodes/*/stacks_with_labels.txt within debug ZIP bundles. Users can opt to exclude these goroutine stacks by using the --include-goroutine-stacks=false flag. Note that fetching stack traces for all goroutines is a “stop-the-world” operation, which can momentarily have negative impacts on SQL service latency. Note also that any periodic goroutine dumps previously taken on the node will still be included in nodes/*/goroutines/*.txt.gz, as these would have already been generated and don’t require any stop-the-world operations.
New rangefeed metrics help to troubleshoot rangefeed restarts. The metric names have the format distsender.rangefeed.retry.{reason}.
Rangefeeds regularly attempt to push long-running transactions to a future timestamp in order to emit checkpoints. The interval at which this is attempted has been increased from 250 milliseconds to 1 seconds. This is now configurable via the environment variable COCKROACH_RANGEFEED_PUSH_TXNS_INTERVAL.

Cluster virtualization

When cluster virtualization is enabled:

A selection box displays in DB Console Metrics pages when you are connected to the system virtual cluster, and allows you to view metrics for a specific virtual cluster.
A “no data” empty graph state has been added when switching to a virtual cluster with no data.
A selection box displays on custom charts in the DB Console and allows you to select a specific virtual cluster.
The name of the virtual cluster, when known, is now reported in logging events.
When cockroach debug zip is run for a cluster with virtualization enabled, data about virtual clusters is now stored in a virtual subdirectory rather than a tenants subdirectory.
When cluster virtualization is enabled, the following closed timestamp side-transport settings can be set only from the system virtual cluster: kv.closed_timestamp.target_duration, kv.closed_timestamp.side_transport_interval, and kv.closed_timestamp.lead_for_global_reads_override.

Command-line changes

The CLI commands that output SQL data now support the JSON output format ( --format=json ), in addition to newline-delimited JSON (ND-JSON, --format=ndjson ) that had been supported since v22.2.
now supports the command-line flag --format to select the format used to store SQL table data, in the same way as . In contrast to cockroach sql however, its default value is json (resulting in files named .json ) and the default is not dependent on whether the terminal is interactive.
The SQL shell now supports argument quoting for client-side commands in a similar way to psql: inside single quotes, \ can escape characters and recognize octal/hexadecimal sequences; and inside double quotes characters are passed through. The quote characters themselves, when doubled, result in themselves as part of the string. For example, the following commands both result in a SQL prompt that says go "world":
\set prompt1 'go "world"' \set prompt1 go' '"world"
To add color to the prompt:
\set prompt1 '\033[34mmydb>\033[m'
These quoting rules are similar to PostgreSQL, but are different from the rules used by POSIX shells and of other programming languages like Python or Go. For example, octal and hex escape sequences support a variable number of digits, and double quoted strings preserve the surrounding quotes. When in doubt, refer to the PostgreSQL documentation.
The configuration for log output sinks now accepts a new format-options field. This can be used to customize the output of a given format. Each format accepts different options. One available option for the json output format is datetime-format. For example:
sinks: fluent-groups: custom-json: format: json format-options: {datetime-format: rfc3339}
This introduces a (new) field datetime in each output JSON event, with the format specified by the option. As of this writing, the following values are documented:
- none: disable the creation of the datetime field. This is the default value.
- iso8601 / rfc3339: format the time stamp like “2006-01-02T15:04:05.999999999Z”.
- rfc1123: format the time stamp like “Mon, 02 Jan 2006 15:04:05 +0000”. Enabling the datetime field introduces CPU overhead and is not recommended. When using output to a log collector such as Fluent or Datadog, the log collector can be configured to transform the timestamp provided by CockroachDB without requiring participation from CockroachDB itself. When inspecting a log file containing JSON output produced by CockroachDB, the command cockroach debug merge-log can consume the JSON data and reformat it using the crdb-v2 format which also includes the date and time using the RFC3339 format.
The json log output format now recognizes the extra format option datetime-timezone which selects which timezone to use when formatting the datetime field. datetime-timezone must be combined with datetime-format because the default value for the latter option is none (i.e., datetime is not produced by default). For example:
sinks: fluent-groups: custom-json: format: json format-options: {datetime-format: rfc3339, datetime-timezone: America/New_York}
The json log format now recognizes the format options tag-style and fluent-tag. The existing formats json-compact, json-fluent, json-fluent-compact have been redefined to become aliases for json with different defaults for the two new options.
The crdb-v1 log format now recognizes the format options show-counter and colors. The existing formats crdb-v1-tty, crdb-v1-count, crdb-v1-tty-count have been redefined to become aliases for crdb-v1 with different defaults for the two new options.
The crdb-v2 log format now recognizes the format option colors. The existing formats crdb-v2-tty has been redefined to become aliases for crdb-v2 with a different default for the new option.
The log output formats crdb-v1 and crdb-v2 now support the format option timezone. When specified, the corresponding time zone is used to produce the timestamp column. For example:
file-defaults: format: crdb-v2 format-options: {timezone: america/new_york}
Example logging output:
I230606 12:43:01.553407-040000 1 1@cli/start.go:575 ⋮ [n?] 4 soft memory limit of Go runtime is set to 35 GiB ^^^^^^^ indicates GMT-4 was used
The timezone offset is also always included in the format if it is not zero (e.g., for non-UTC time zones). This is necessary to ensure that the times can be read back precisely.
The command cockroach debug merge-log was adapted to understand time zones in input files read with format crdb-v1 or crdb-v2.
When customizing the SQL interactive prompt, %M and %m now behave more like psql when connecting over a Unix datagram socket.
The default value of the --format parameter to cockroach debug zip is tsv, like other CLI commands that can extract SQL data.
The debug.zip now includes the crdb_internal.probe_range table with a limit of 100 rows to prevent the query from taking too long.
The default value for the --max-sql-memory parameter of the has been increased from 128 MiB to 256 MiB.
The command \demo recommission has been removed from . It had been obsolete and non-functional ever since v20.2.
Added limited statement_statistics to the debug ZIP file.

The following user-visible cluster settings have been renamed. The previous name is still available for backward compatibility.

Previous name	New name
`server.web_session_timeout`	`server.web_session.timeout`
`kv.closed_timestamp.follower_reads_enabled`	`kv.closed_timestamp.follower_reads.enabled`
`kv.range_split.by_load_enabled`	`kv.range_split.by_load.enabled`
`changefeed.balance_range_distribution.enable`	`changefeed.balance_range_distribution.enabled`
`changefeed.batch_reduction_retry_enabled`	`changefeed.batch_reduction_retry.enabled`
`server.clock.forward_jump_check_enabled`	`server.clock.forward_jump_check.enabled`
`server.oidc_authentication.autologin`	`server.oidc_authentication.autologin.enabled`
`sql.metrics.statement_details.dump_to_logs`	`sql.metrics.statement_details.dump_to_logs.enabled`
`sql.trace.log_statement_execute`	`sql.log.all_statements.enabled`
`trace.debug.enable`	`trace.http_debug_endpoint.enabled`

The following cluster settings have been renamed. The previous names are available for backward-compatibility.
Previous name New name
spanconfig.tenant_coalesce_adjacent.enabled spanconfig.range_coalescing.application.enabled
spanconfig.storage_coalesce_adjacent.enabled spanconfig.range_coalescing.system.enabled
The new cockroach gen metric-list command generates metadata that describes the various metrics collected by an idle server. The list does not include dynamic metric names whose names are generated based on the workload.

DB Console changes

The time window selection for metrics charts is now encoded in the URL via query params.
The now has a tabbed UI that will allow users to toggle between the Overview and other future views for advanced debugging and observability.
Renamed “recent executions” to “active executions” in the UI.
The has been updated with new graphs to track backfill progress, protected timestamps age, and the number of schema registry registrations. The updates include renaming the Sink Byte Traffic graph to Emitted Bytes and the Max Changefeed Latency graph to Max Checkpoint Latency.
A new Networking tab has been added to the DB Console metrics dashboard. Metrics for network bytes sent and received are now displayed in the Networking tab rather than the Hardware tab. In addition, the following metrics have been added:
- cr.node.round-trip-latency-p50
- cr.node.round-trip-latency-p99
- cr.node.rpc.connection.unhealthy

#104394

The Job Details page now has a profiler tab for more advanced observability into a job’s execution. Currently, we support collecting a cluster-wide CPU profile of the job.
The active executions views in the SQL Activity pages now support toggling between automatic and manual refresh. A manual refresh button was also added along with a timestamp indicating when the last refresh was performed.
The visibility of the cluster setting ui.display_timezone has been set to public. Documentation of the cluster setting has been added. No functionality has been changed.
Added a table in the Profiler job details page that lists all the available files describing a job’s execution details
Add columns for p50, p90, p99 percentiles and latency min and max on Explain Plan tab on the .
Fixed a broken query for the database details page that was causing an infinite loading state.
Added summary cards with total/average values for statistics on the Statement Execution Details page.
The DB Console now Shows a warning when the time period selected on SQL Activity pages is older than the oldest data available.
Users without the VIEWCLUSTERSETTINGS permission but with VIEWACTIVITY or VIEWACTIVITYREDACTED can now see index recommendations.
The DB Console now allows non-admin users to view the .
Non-admin users are able to use the Database Details page.
Non-admin users are able to use the Database Table page.
The “SQL Connection Rate” metric on the is downsampled using the MAX function instead of SUM. This improves situations where zooming out would cause the connection rate to increase for downsampled data.

Bug fixes

Fixed an internal error that can occur when replaces a view with fewer columns and another entity depended on the view.
If views are created with circular dependencies, CockroachDB now returns an error ( cyclic view dependency for relation ) instead of crashing the node. This bug was present since at least 21.1.
Fixed a potential bug whereby a failed or cancelled could in some cases leave some of the imported rows behind after it was cancelled, in the rare event that the writing processes were slow enough to continue writing after the cleanup process started.
Fixed a very rare bug that could cause keys to get unexpectedly deleted when rebalances occurred in a write-heavy workload.
It is now possible to properly redirect the output of SQL queries using the ndjson output table format in . This bug had been introduced in v22.2.
The unaccent built-in no longer removes spaces.
The details of errors pertaining to invalid descriptors are not included any more in redacted debug ZIP files.
Fixed a bug where join expressions were processed incorrectly.
Fixed a bug that could cause a to return a value that does not conform to the return type of the UDF. This bug was only present for UDFs that return user-defined types. The bug was present since v23.1.
Fixed a bug where if a user was logged in while a different session dropped that user, the dropped user would still inherit privileges from the public role. Now, CockroachDB checks that the user exists before allowing it to inherit privileges from the public role. In addition, any active web sessions are now revoked when a user is dropped.
Fixed a bug in upstream etcd-io/raft which could result in pulling unlimited amount of logs into memory, and lead to out-of-memory errors. Now the log scan has a limited memory footprint.
Fixed a bug where, in rare circumstances, a replication could get stuck when proposed near lease or leadership changes, especially under overload, and the [replica circuit breakers]( ../v23.2 could trip. A previous attempt to fix this issue has been reverted in favor of this fix.
CockroachDB now automatically deletes statistics for dropped tables from the system.table_statistics table.
Fixed a rare internal error which occurs when a query uses a “project set” operation involving simple column expressions.
The PreVote and CheckQuorum mechanisms are now fully enabled. These prevent spurious elections when followers already have an active leader, and cause leaders to step down if they don’t hear back from a quorum of followers. This improves reliability under partial and asymmetric network partitions, by avoiding spurious elections and preventing unavailability where a partially partitioned node could steal leadership away from an established leaseholder who would then no longer be able to reach the leader and submit writes.
Fixed a bug that could produce incorrect values for in rare cases. The bug only occurred when the virtual column expression’s type did not match the type of the virtual column.
Fixed a rounding error that could cause distributed execution for some decimal aggregate functions to return slightly inaccurate results in rare cases.
Fixed the StatementStatistics.Nodes to contain all of the nodes involved in the query. Fixed the region info in for virtual clusters.
Fixed a bug that caused to fail if there are tables and functions of the same name.
Fixed edge cases in decimal and float evaluation for division operators. 'NaN'::DECIMAL / 0 will now return NaN instead of a division-by-zero error, and 0 / 'inf'::DECIMAL will return 0 instead of 0E-2019.
Fixed a bug present since before v22.2 that could cause a query with LIMIT and ORDER BY to return results in the wrong order. This bug could cause incorrect results as well if the LIMIT was nested within an outer query (e.g., under another LIMIT ).
Added missing SQLInstanceIDs used to execute the statement to the telemetry SampledQuery event.
Fixed a bug where inserting geometries into a table with an inverted index involving a NaN coordinate could result in a panic. This now produces errors instead.
Avoid displaying undefined regions on the .
The uses less memory when uploading a file.
CASE, IF, COALESCE, and IFNULL expressions now return an error when passed a generator function as an argument. This mirrors the behavior of PostgreSQL.
Fixed a bug that allowed views created with CREATE OR REPLACE VIEW to reference user-defined types in other databases, even with sql.cross_db_views.enabled set to false. This bug was present since user-defined types were introduced in v20.1.
Removed a source of unnecessary Raft snapshots during replica movement.
Fixed a bug where in rare situations nodes would get stuck during start-up. It would manifest itself through a stack frame sitting on a select in waitForAdditionalStoreInit for extended periods of time (i.e., minutes).
Fixed a bug that caused internal errors when using an aggregate function in an ORDER BY clause of a or statement. Aggregate functions are no longer allowed in these contexts. The bug has been present since at least v20.2.
The filter on the works when application name is an empty string.
The now loads with the fingerprint details even if no application is specified in the URL.
The no longer times out.
The last SQL statement in a user-defined function with a VOID return type can now produce any number of columns of any type. This bug was present since UDFs were introduced in v22.2.
Fixed a bug that caused nodes to crash when attempting to EXECUTE a prepared statement with an argument that referenced a user-defined function. This bug was present since user-defined functions were introduced in v22.2.
Fixed a bug where a release could incorrectly emit a “cannot publish new versions for descriptors” error instead of a retryable error.
Users with the VIEWACTIVITY privilege now are able to see other users sessions from both the CLI and the DB Console.
Fixed a bug in whereby \demo add could sometimes crash with an error ” index out of range [...] with length... ”. This bug had been introduced in v19.x.
Fixed a bug introduced in v20.2 where the command \demo decommission in cockroach demo could leave the demo cluster in a broken state.
Fixed a bug where would sometimes incorrectly hang upon shutting down a server after encountering an internal error. This bug had been introduced some time in v22.x.
Fixed a bug in the index recommendations provided in the output where ALTER INDEX... VISIBLE index recommendations may suggest making the wrong index visible when there are multiple invisible indexes in a table.
Users with the can now view correct values for timezones.
Fixed a bug present since v23.1.0 that would cause queries on the pg_catalog.pg_statistic_ext table to fail if a table was dropped recently. This bug also caused the \d CLI shortcut to encounter errors.
Fixed a bug where pg_attribute and pg_attrdef did not properly return results for generated columns.
Fixed a bug where a SpanStatsRequest would return post-replicated MVCC stats. Now, a SpanStatsRequest returns the logical MVCC stats for the requested span.
Fixed the column name on the selects on the tables crdb_internal.node_txn_execution_insights and crdb_internal.cluster_txn_execution_insights upon the creation of debug.zip.
Fixed the type resolution logic for CASE statements to more closely match Postgres’ logic. In particular, we now adhere to rule 5 listed in the PostgreSQL documentation, which requires that we select the first non-unknown input type as the candidate type, then consider each other non-unknown input type, left to right ( CASE treats its ELSE clause (if any) as the “first” input, with the THEN clauses(s) considered after that). If the candidate type can be implicitly converted to the other type, but not vice-versa, select the other type as the new candidate type. Then continue considering the remaining inputs. If, at any stage of this process, a preferred type is selected, stop considering additional inputs (note that CockroachDB does not yet support the concept of a “preferred type”).
Fixed an issue on the where no metrics would load when viewing metrics for a virtual cluster with a hyphenated name in a global context.
Fixed a potential livelock between a high-priority transactional read and a normal-priority write. The read pushes the timestamp of the write, but if the read gets pushed as well, it may repeatedly fail to refresh because it keeps encountering the intent of the write.
Fixed a nil dereference panic during node startup that could be caused by an incorrect initialization order.
The difference built-in had its return type incorrectly set to a string instead of an integer.
Fixed a bug that could cause a transaction performing multiple parallel foreign key checks to return a concurrent txn use detected error.
Fixed a bug causing performance regression when disabling sql.metrics.statement_details.enabled which caused execution stats to be collected for all queries instead of the default one percent.
Fixed a bug where certain SQL session variables meant to be hidden from introspection were showing up in information_schema.session_variables, which was incoherent with the handling in pg_catalog.pg_settings.
CockroachDB now properly handles RPC failures on writes using the parallel commit protocol that execute in parallel to the commit operation, avoiding incorrect retryable failures and transaction unexpectedly committed assertions by detecting when writes cannot be retried idempotently, instead returning an AmbiguousResultError.
Fixed a bug where dependencies on sequences from tables would be reported with the wrong value for the classid column in the pg_catalog.pg_depend table.
Two ALTER RANGE default CONFIGURE ZONE statements on the same line no longer displays an error.
Fixed a DB Console issue where the DROP_UNUSED index recommendations produced by the table details page produced an invalid DROP INDEX statement.
Removed buggy descriptor repair. Previously, upgrading from v22.2.X to v23.1.9 incorrectly removed TTL storage parameters from tables (visible by running a SHOW CREATE TABLE <ttl-table>; statement) while attempting to repair table descriptors. This resulted in the node that attempted to run the TTL job crashing due to a panic caused by the missing TTL storage parameters.
cockroach debug pebble commands now work correctly with encrypted stores which don’t use the default cockroach-data path without having to also pass --store.
Fixed a bug where CREATE INDEX for could fail with ERROR: duplicate key value violates unique constraint if concurrent inserts happened simultaneously.
Observability pages no longer crash when they encounter zeros (e.g., a session with no memory allocated).
Removed the kv.snapshot_recovery.max_rate:
- In v23.2, this setting is disabled; it is a no-op. If you previously set kv.snapshot_recovery.max_rate on a cluster running v23.1 and upgraded to v23.2, the setting is ignored, and the setting is used instead.
- In v24.1 and later, this setting is removed entirely. If you had previously set kv.snapshot_recovery.max_rate prior to upgrade, it will be cleared, and any attempts to set it will fail with the error message: ERROR: unknown cluster setting 'kv.snapshot_recovery.max_rate'.
Fixed a bug in which a CREATE FUNCTION may produce a syntax error if the UDF body wrapped in tagged dollar quotes (e.g., $func$ ), contains two consecutive dollar signs $$. If the UDF body is known to contain dollar signs, then the caller should use tagged dollar quotes or single quotes when defining the UDF. For example:
CREATE FUNCTION f(a STRING) RETURNS STRING LANGUAGE SQL AS $func$ SELECT concat('$$', a); $func$
CockroachDB now prevents setting max_range_size below the COCKROACH_MIN_RANGE_MAX_BYTES environment variable, which defaults to 64 MiB (half of the default minimum range size).
Fixed a bug that could occasionally cause schema change jobs, such as table or index drops, to appear stuck in state “waiting for MVCC GC” for much longer than expected. The fix only applies to future schema changes. To process existing stuck jobs, manually force-enqueue the relevant ranges in the MVCC GC queue from the DB Console’s Advanced Debug page.
Fixed a bug introduced when the ChartCatalog API endpoint was introduced, where the endpoint did not correctly report the unit of metrics.
Fixed a bug that could occur when the “multiple active portals” execution mode (Preview) was enabled to evaluate queries such as lookup joins. The bug could result in an internal error like unexpected 40960 leftover bytes if the portal was not fully consumed.
Fixed a bug where an ALTER TABLE... ADD CONSTRAINT CHECK... statement that utilized a user-defined function in the CHECK could cause a validation error.
Fixed a bug where RESET (ttl_expire_after) could incorrectly remove ttl_expiration_expression.
Fixed a bug where the format_type built-in did not honor typemod information for array types, leading to incorrect output.
Fixed a bug introduced in v22.2 that incorrectly allowed users without the EXECUTE privilege to execute a user-defined function.

Performance improvements

The now plans inverted index scans for queries using IN or the = operators without the fetch val ( -> ) operator. For example: json_col = '{"b":"c"}' OR json_col IN ('"a"', '1')
Queries that have subqueries in equality expressions are now more efficiently planned by the optimizer.
Query planning time has been reduced for some queries with multiple .
CockroachDB now enables the pacing mechanism in rangefeed closed timestamp notifications, by setting the default kv.rangefeed.closed_timestamp_smear_interval cluster setting to 1ms. This makes rangefeed closed timestamp delivery more uniform and less spikey, which reduces its impact on the Go scheduler and, ultimately, foreground SQL latencies.
Some large, long-running statements now perform less work during their commit phase and can run faster.
Ranges now only quiesce after 3 seconds without proposals, to avoid frequent unquiescence which incurs an additional Raft proposal. This is configurable via the COCKROACH_QUIESCE_AFTER_TICKS environment variable, which defaults to 6.
SQL statements that must clean up intents from many different previously abandoned transactions now do so moderately more efficiently.
The optimizer can now avoid a grouping stage in more cases when de-duplicating the input to an or INSERT... ON CONFLICT statement.
The optimizer can now eliminate joins in more cases.
CockroachDB now improves the time to disk space reclamation when deleting rows. Previously, in scenarios where rows had large variations in row size, it was possible for disk space to not be reclaimed after MVCC garbage collection deleted the rows.
CockroachDB now has improved disk space reclamation heuristics, making disk space reclamation more timely.
bool_and and bool_or aggregates will now scale linearly instead of quadratically when used as a window function with a non-shrinking window,
CockroachDB now has reduced lock contention on ssmemstorage.RecordStatement. This is useful for workloads that execute the same statement concurrently on the same SQL instance.
The optimizer now produces more efficient query plans in some cases for queries with subqueries and user-defined functions.
The default Raft entry cache size has been increased from 16 MB to 1/256 of system memory with a minimum of 32 MB, divided evenly between all stores. This can be configured using the COCKROACH_RAFT_ENTRY_CACHE_SIZE environment variable.
CockroachDB now automatically collects table statistics on the system.jobs table, which will enable the optimizer to produce better query plans for internal queries that access the system.jobs table. This may result in better performance of the system.
The impact of high concurrency blind writes to the same key on goroutine scheduling latency was reduced.
to Webhook or Pub/Sub endpoints now support much higher throughput
This release improved the cost of resolving a user-defined enum type that has many values.
Queries that compare collated strings now use less memory and may execute faster.
Added a scheduler based rangefeed processor which improves rangefeed and changefeed performance for very large tables. The new processor is disabled by default, but can be enabled by setting kv.rangefeed.scheduler.enabled cluster setting to true.
This release disables sql.defaults.zigzag_join.enabled by default.

Build changes

Go has been upgraded to 1.20.8.
The top-level Makefile was replaced by a stub GNUmakefile which defers its behavior to dev. The common targets make [all], make test, and make install remain for compatibility with most UNIX installation guides. The previous make rules remain available via make -C build/GNUmakefile.obsolete.

Contributors

This release includes 3208 merged PRs by 124 authors.

v24.1 Release notes v23.1 Release notes

Previous name	New name
`spanconfig.tenant_coalesce_adjacent.enabled`	`spanconfig.range_coalescing.application.enabled`
`spanconfig.storage_coalesce_adjacent.enabled`	`spanconfig.range_coalescing.system.enabled`

​v23.2.31

​Downloads

​Docker image

​v23.2.30

​Downloads

​Docker image

​v23.2.29

​Downloads

​Docker image

​Bug fixes

​v23.2.28

​Downloads

​Docker image

​Performance improvements

​v23.2.27

​Downloads

​Docker image

​Operational changes

​Bug fixes

​Performance improvements

​v23.2.26

​Downloads

​Docker image

​Bug fixes

​v23.2.25

​Downloads

​Docker image

​SQL language changes

​Bug fixes

​v23.2.24

​Downloads

​Docker image

​Bug fixes

​v23.2.23

​Downloads

​Docker image

​Bug fixes

​v23.2.22

​Downloads

​Docker image

​General changes

​Bug fixes

​Miscellaneous

​v23.2.21

​Downloads

​Docker image

​SQL language changes

​Bug fixes

​v23.2.20

​Downloads

​Docker image

​SQL language changes

​Operational changes

​Bug fixes

​v23.2.19

​Downloads

​Docker image

​Security updates

​General changes

​SQL language changes

​Operational changes

​Bug fixes

​v23.2.18

​Downloads

​Docker image

​SQL language changes

​v23.2.17

​Downloads

​Docker image

​Security updates

​General changes

​Enterprise edition changes

​Operational changes

​Bug fixes

​Performance improvements

​v23.2.16

​Downloads

​Docker image

​General changes

​DB Console changes

v23.2.31

Downloads

Docker image

v23.2.30

Downloads

Docker image

v23.2.29

Downloads

Docker image

Bug fixes

v23.2.28

Downloads

Docker image

Performance improvements

v23.2.27

Downloads

Docker image

Operational changes

Bug fixes

Performance improvements

v23.2.26

Downloads

Docker image

Bug fixes

v23.2.25

Downloads

Docker image

SQL language changes

Bug fixes

v23.2.24

Downloads

Docker image

Bug fixes

v23.2.23

Downloads

Docker image

Bug fixes

v23.2.22

Downloads

Docker image

General changes

Bug fixes

Miscellaneous

v23.2.21

Downloads

Docker image

SQL language changes

Bug fixes

v23.2.20

Downloads

Docker image

SQL language changes

Operational changes

Bug fixes

v23.2.19

Downloads

Docker image

Security updates

General changes

SQL language changes

Operational changes

Bug fixes

v23.2.18

Downloads

Docker image

SQL language changes

v23.2.17

Downloads

Docker image

Security updates

General changes

Enterprise edition changes

Operational changes

Bug fixes

Performance improvements

v23.2.16

Downloads

Docker image

General changes

DB Console changes