| Feature | +Description | +
|---|---|
Full-text search using TSVector and TSQuery + |
+ A full-text search is used to perform queries on natural-language documents such as articles, websites, or other written formats, with results often sorted by relevance. +You can rely on new built-in functions to make use of the new TSVECTOR and TSQUERY data types. + |
+
Improved developer experience for multi-region apps + |
+ If you have functionality that requires low latency and cannot tolerate delays between regions, you can enable the |
+
Streamline migrations with improved COPY performance + |
+ Enhancements to the functionality behind COPY statements resulted in 2x faster migrations using AWS DMS. + |
+
Redact PII from statement bundles + |
+ Leverage statement bundles for debugging without introducing data privacy concerns. You can now redact personally identifiable information (PII) from statement bundles for PCI compliance. + |
+
User-Defined Function (UDF) enhancements + |
+ User-defined functions offer enhanced flexibility, performance, and reusability. This release brings a number of UDF enhancements, including: Inlining of supported UDFs within the query plan to improve performance; support for subqueries in statements, support for expressions with a
+UDFs can now also be used in Changefeed expressions (Enterprise) and |
+
DELETE FROM ... USING + |
+ We have added support for the |
+
| Feature | +Description | +
|---|---|
Support user-defined composite types + |
+ You can now create your own enumerated data types. + +For example: +CREATE TYPE t AS (a INT, b INT); +CREATE TABLE a (a t); +INSERT INTO a VALUES((1, 2)) +SELECT (a).b FROM a+ |
+
Declarative schema changer supports user-defined functions UDFs + |
+ The statements |
+
Declarative schema changer fully supports constraints + |
+ The statements |
+
Add configurable setting to adjust grant lease options + |
+ A new session variable +By default, when granting or revoking a role from another role, the system waits until all transactions that are consulting the current set of role memberships to complete. This is done to preserve CockroachDB’s default isolation level. However, the downside of this wait is that grant and revoke will take longer than the longest currently executing transaction. + +In some cases, you may not care about whether concurrent transactions will immediately see the side-effects of the role grant or revoke operation, but would instead prefer that the operation finish quickly. + +For more information about this setting and how it works, see the Limitations section of the GRANT documentation. + |
+
| Feature | +Description | +
|---|---|
New SQL shell editor with tab completion + |
+ The SQL shell has a new user interface that allows tab completion and more advanced navigation, streamlining developer workflows. + +After pressing tab, you can navigate database objects, keywords, and functions using arrow keys, pressing tab again to select one and return to the console. You can also use pattern matching to filter these entities and find what you need faster. + |
+
Support multiple active portals (Preview) + + |
+ The multiple active portals feature of the Postgres wire protocol (pgwire) is available in CockroachDB, with limitations. This allows for more efficient data retrieval by reducing the number of roundtrips required between the client and server. + +Third-party tools such as asyncpg use this feature to implement efficient asynchronous communication between the PostgreSQL server and client. This can allow for faster, more scalable applications that can handle large amounts of data without slowing down the user experience. + |
+
Full support for asyncpg + |
+ CockroachDB now offers full support for asyncpg, a PostgreSQL database interface library designed specifically for Python's asyncio framework. It provides an efficient implementation of the PostgreSQL server binary protocol for high-performance asynchronous database applications. + +Asyncpg is commonly used with ORM libraries such as SQLAlchemy to provide a simple, flexible, and efficient adapter for working with PostgreSQL databases. This makes it ideal for handling large volumes of data and scaling applications to meet demanding performance requirements. + |
+
| Feature | +Description | +
|---|---|
Improvements to the redaction of data in observability artifacts + |
+ We have made a number of improvements to ensure that sensitive data can be redacted in observability artifacts produced by CockroachDB, such as debug.zip and statement bundles. These improvements, available to all Self-Hosted customers, also help Cockroach Labs to comply with PCI DSS in CockroachDB Dedicated. + |
+
FIPS-ready CockroachDB binaries + |
+ FIPS-ready binaries and Docker images are available for CockroachDB 23.1.0 and above. Federal Information Processing Standards (FIPS) 140-2 is a standard used to approve cryptographic modules by the U.S. and Canadian governments for systems maintained by relevant agencies and organizations working with them for the purposes of encrypting and decrypting sensitive data. + FIPS-ready CockroachDB binaries are designed for workloads that require FIPS 140-2. FIPS-ready CockroachDB delegates cryptographic operations to the OpenSSL library available on the host operating system, rather than Go's cryptographic libraries. We recommend that OpenSSL has a FIPS 140-2 certificate. FIPS mode must be enabled in the Linux kernel to ensure that FIPS 140-2 is enforced by the operating system. + |
+
Support Oauth authentication protocol for changefeeds + |
+ See this item in Change Data Capture (Changefeeds). + |
+
Support encrypted backups with keys stored in Azure Key Vault + |
+ You can now take and restore encrypted backups using RSA keys stored in Azure Key Vault. + |
+
Expand on External Connections for Changefeeds + |
+ See the Changefeeds section for more information. + |
+
New fine-grained system privilege to view all jobs + |
+ The new |
+
| Feature | +Description | +
|---|---|
Create scheduled exports using changefeeds + |
+ Changefeeds can offer benefits over existing export functionality for customers who need higher levels of scale and observability. You can now create Changefeeds as Export functionality. + |
+
Use a webhook as a changefeed sink + |
+ The use of a webhook sink to deliver changefeed messages to an arbitrary HTTPS endpoint has been promoted from Preview to GA. + |
+
CDC Queries + |
+ CDC Queries (formerly CDC Transformations) have been promoted from Preview to GA. + |
+
Use External Connections (GA) to remove a data exfiltration vector + |
+ Use external connections to specify and interact with resources that are external from CockroachDB. With CREATE EXTERNAL CONNECTION, you define a name for an external connection while passing the provider URI and query parameters. BACKUP, RESTORE, IMPORT, EXPORT, and CREATE CHANGEFEED queries can interact with the defined external connection instead of a required, provider-specific URI. As a result, you can decouple the management and permissions of the external resource from the operation in which you're using them. + +With the move from Preview to GA, this feature brings many new capabilities, such as fine-grained permission and support for schema registries, webhook and GC PubSub sinks, and the SHOW command. + |
+
Changefeed locality + |
+ CREATE CHANGEFEED now accepts a 'WITH execution_locality' option to restrict execution of the changefeed process to nodes within the specified locality filter. + |
+
Improved changefeed resilience + |
+ Changefeeds are more stable as the result of improved error handling. Changefeeds now default to retrying requests when encountering any error, except those deemed terminal. + |
+
Support Oauth authentication protocol for changefeeds + |
+ Oauth authentication uses a third-party software provider to authenticate with Kafka instead of providing CockroachDB with direct access to Kafka cluster credentials. The third-party authentication server provides a temporary credential token that CockroachDB then uses to connect to a customer’s Kafka cluster. This represents a security best practice, allowing users to authenticate without directly storing or sharing their credentials. + |
+
| Feature | +Description | +
|---|---|
Support longer incremental backup chains + |
+ We now support up to 400 incremental backups, an 8x increase, enabling you to preserve your data even more effectively (reducing RPO) while being more cost-efficient. Incremental backups contain only the data that has changed since the last backup, so they are smaller and faster to produce. + |
+
Restrict backups to a locality + |
+ You can now [restrict backup execution](take-locality-restricted-backups.html) to a specific region/locality. Only the nodes in the specified locality filter will execute the backup, so only those nodes will need access to the backup storage bucket. + +If the node executing the backup does not have a specific range to be backed up, it will read it from the closest replica it can. + |
+
Support implicit authentication on Azure + |
+ You can now use implicit authentication on Azure for cloud storage authentication. + +If the node executing the backup does not have a specific range to be backed up, it will read it from the closest replica it can. + |
+
Support encrypted backups with keys stored in Azure Key Vault + |
+ You can now take and restore encrypted backups using RSA keys stored in Azure Key Vault. + |
+
Enforce supported backup versions + |
+ To help ensure backups and restores are successful, CockroachDB now enforces its previous support for restoring backups from up to two minor versions prior. Previously, restoring backups produced from even earlier versions was possible, but unreliable. Now, this operation is prevented with an error. + |
+
| Feature | +Description | +
|---|---|
Key Visualizer (Preview) + |
+ Using a visual heatmap of the latest historical range activity across the cluster, you can quickly identify hot spots and full table scans, enabling you to target ranges for performance investigations. + |
+
Enhanced Intelligent Insights experience includes transaction-level insights and metrics + |
+ We have expanded the [Insights](../v23.1/ui-insights-page.html#transaction-executions-view) section of the Console, offering improved discoverability and data for tuning and optimizing your workload. Contention insights reveal the waiting statement for cases where blocking conflicts occur. Transaction-level insights help you identify impacted areas of your application and prioritize your investigations, enabling you to drill down to individual statements with suboptimal plans. + |
+
Enhanced statement metrics + |
+ Easily correlate high-level cluster metrics (e.g., CPU, latency, etc.) with per-statement CPU utilization, latency metrics (P50, P90, P99, min, max), idle/client time, and MVCC garbage statistics. + |
+
Faster performance and an enhanced UX for the SQL Activity pages + |
+ Reliably and quickly find SQL activity information using a new interactive ‘Search Criteria’ capability in the console. + |
+
Supplement troubleshooting flows with additional observability into indexes used per statement + |
+ Observability information is available to correlate statements (and their plans) to indexes. You can now map index usage statistics with statements and transactions which streamlines troubleshooting flows such as dropping infrequently used indexes, creating or updating table statistics, reducing MVCC garbage, and alleviating resource hot spots. + |
+
| Feature | +Description | +
|---|---|
Decommission Pre-Flight Checks + |
+ Decommissioning operations now check that each replica on a node that is slated to be decommissioned can be moved to another node. + +Any ranges that are not yet fully upreplicated will block the decommission process. + +When errors are detected that would prevent successful decommissioning,, the errors are printed to STDERR and the decommissioning command exits. + |
+
Delegated Snapshots: Send Raft snapshots between follower replicas + |
+ Delegated Snapshots make multi-region deployments more cost-efficient by decreasing the use of remote snapshots if there is a local snapshot with the data. + +Sending data locally reduces your network costs and frees up the WAN bandwidth for the important data that must be transferred + +Previously, customers with multi-site deployments paid more for network bandwidth than strictly necessary due to system operations that required snapshots. Additionally, because of congested TCP channels between regions, transferring snapshots could negatively impact user traffic and slow snapshot transfers. + +Delegated Snapshots fixes this problem by sending snapshots from a local replica whenever a close-by replica exists and isn’t busy. + |
+
Faster leaseholder recovery + |
+ The default CockroachDB lease duration has been reduced from 9 seconds to 6 seconds, to reduce range unavailability following leaseholder loss. Some other related settings have also had their defaults reduced, including heartbeat intervals, Raft election timeouts, and network timeouts. + |
+
Lower default TTL for garbage collection (GC) + |
+ The default GC TTL value in 23.1.0 is being reduced from 25 hrs to 4 hrs for new clusters. + +This change is being made to improve read performance, storage utilization, and cluster stability in high write traffic scenarios. +Scheduled backups will not be affected by this change as protected timestamps will ensure data isn't garbage-collected until it has been backed up. Changefeeds will also not be affected. If you want a 25-hour or larger GC TTL value (for example, to support AS OF SYSTEM TIME queries that go further back in time), you can explicitly set GC TTL to the desired value. + +This change will only apply to new clusters. Existing clusters will retain the 25-hour default when upgrading, unless you have previously overridden it with an explicit value, in which case, that value will be retained. Backups taken from clusters running versions prior to v23.1 will similarly retain the GC TTL configured when the backup was taken. + |
+