RATATOSK
← All releases

Vitessv23.0.0

Security 11Breaking changes 27Deprecations 15Important fixes 49Enhancements 47Dependency updates 17Other changes 110

Get Vitess alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Check before upgrading

Prerequisites1
Manual sequence for vitess-operator upgrades from 8.0.x to 8.4.x

Add innodb_fast_shutdown=0 in the YAML extra cnf and apply it, wait for all pods to be healthy, change the image to vitess/lite:v23.0.0, then remove the setting and apply again. This sequence is needed only for the move to 8.4.x, not for upgrades or downgrades between 8.4.x versions.

>  ⚠️ Upgrading to this release with vitess-operator:
>
> If you are using the `vitess-operator`, considering that we are bumping the MySQL version from `8.0.40` to `8.4.6`, you will have to manually upgrade:
>
> 1. Add `innodb_fast_shutdown=0` to your extra cnf in your YAML file.
> 2. Apply this file.
> 3. Wait for all the pods to be healthy.
> 4. Then change your YAML file to use the new Docker Images (`vitess/lite:v23.0.0`).
> 5. Remove `innodb_fast_shutdown=0` from your extra cnf in your YAML file.
> 6. Apply this file.
>
> This is only needed once when going from the latest `8.0.x` to `8.4.x`. Once you're on `8.4.x`, it is possible to upgrade and downgrade between `8.4.x` versions without needing to run `innodb_fast_shutdown=0`.
github.com/vitessio/vitess/releases/tag/v23.0.0
Known issues2
Experimental throttler remains under active development

Work is ongoing, and breaking changes may occur in future releases.

Vitess v23.0.0 introduces a new, experimental Query Throttler framework for rate-limiting incoming queries ([RFC issue #18412](https://github.com/vitessio/vitess/issues/18412), [PR #18449](https://github.com/vitessio/vitess/pull/18449), [PR #18657](https://github.com/vitessio/vitess/pull/18657)). Work on this new throttler is ongoing with the potential for breaking changes in the future.
github.com/vitessio/vitess/releases/tag/v23.0.0
Availability risks from disabling EmergencyReparentShard-based recoveries

Frequent reliance on this control may indicate an anti-pattern.

**Note: disabling `EmergencyReparentShard`-based recoveries introduces availability risks; please use with extreme caution! If you rely on this functionality often, for example in automation, this may be signs of an anti-pattern. If so, please open an issue to discuss supporting your use case natively in VTOrc.**
github.com/vitessio/vitess/releases/tag/v23.0.0

Security11Security status unclear1

Consul static-file authentication requires a loaded credential

Affectssetups using --consul-auth-static-file
Additional actionThe JSON file must allow at least one credential to be loaded.

Previously, an empty or invalid JSON file—including {}—could let startup continue without authentication. Such files now cause startup to fail.

Show release-note lines
### <a id="minor-changes-topo"/>Topology</a>
#### <a id="consul-auth-static-file-check-creds"/>`--consul-auth-static-file` requires 1 or more credentials</a>
The `--consul-auth-static-file` flag used in several components now requires that 1 or more credentials can be loaded from the provided json file ([PR #18152](https://github.com/vitessio/vitess/pull/18152)).
**Impact**: Configurations with empty or invalid credential files will now fail at startup rather than silently continuing with no authentication.
 * Check `consultopo` loaded `>=1` credentials w/`-consul_auth_static_file` [#18152](https://github.com/vitessio/vitess/pull/18152)
github.com/vitessio/vitess/releases/tag/v23.0.0

GetSchema respects the EnableViews setting

Affectstablet servers with EnableViews disabled
Additional actionEnableViews disabled

Previously, clients could still fetch view definitions through GetSchema despite that setting. Now, SchemaTableType_VIEWS returns an empty result, and SchemaTableType_ALL returns only table definitions.

Show release-note lines
 * Fix GetSchema RPC to prevent returning view definitions when EnableViews is disabled [#18513](https://github.com/vitessio/vitess/pull/18513)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

vtctldclient GetPermissions clears password checksums

Affectssetups using vtctldclient GetPermissions

The JSON output omits unpopulated fields.

Show release-note lines
 * [release-23.0] Potential fix for code scanning alert no. 2992: Clear-text logging of sensitive information (#18754) [#18760](https://github.com/vitessio/vitess/pull/18760)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

vtctldclient GetPermissions response omits authentication_string

Affectssetups that use vtctldclient GetPermissions

The patch also notes that the field is redacted server-side in v23 and later.

Show release-note lines
 * [release-23.0] `vtctldclient GetPermissions`: hide `authentication_string` from response (#18771) [#18799](https://github.com/vitessio/vitess/pull/18799)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

External-tablet VReplication permission check no longer queries mysql.user

Affectsexternal tablets with reverse replication enabled
Additional actionThe permission check runs during a write-traffic switch when reverse replication is enabled.

Previously, the permission check queried mysql.user, requiring access to that table and making checks difficult to test reliably across wildcard grants, role-based authentication, and database versions. During a write-traffic switch, it now tests permissions with dummy DMLs in a transaction without requiring access to mysql.user.

Show release-note lines
 * VReplication: permission check logic on external tablets -- switch to a more practical solution [#18580](https://github.com/vitessio/vitess/pull/18580)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VTAdmin TLS support for vtctld gRPC connections

Security status unclear
AffectsVTAdmin setups using TLS for the vtctld gRPC connection
Additional actionConfigure --vtctld-grpc-ca, --vtctld-grpc-cert, --vtctld-grpc-key, --vtctld-grpc-server-name, and --vtctld-grpc-crl for vtctld gRPC TLS.

Previously, TLS-only vtctld connections prevented VTAdmin from starting because its proxy used insecure gRPC credentials. With secure dial configuration available, VTAdmin can connect to vtctld over TLS.

Show release-note lines
 * Add vtctldclient TLS support to vtadmin GRPC [#18556](https://github.com/vitessio/vitess/pull/18556)
Five new TLS-related flags were added for secure vtctld connections ([PR #18556](https://github.com/vitessio/vitess/pull/18556)):
| Flag | Description |
|:-----|:------------|
| `--vtctld-grpc-ca` | CA certificate file for vtctld gRPC TLS |
| `--vtctld-grpc-cert` | Client certificate file for vtctld gRPC TLS |
| `--vtctld-grpc-key` | Client key file for vtctld gRPC TLS |
| `--vtctld-grpc-server-name` | Server name for vtctld gRPC TLS validation |
| `--vtctld-grpc-crl` | Certificate revocation list for vtctld gRPC TLS |
These flags enable mTLS (mutual TLS) authentication between VTAdmin and vtctld for enhanced security.
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

File backup path traversal checks added

Affectsinstallations using file backup storage(Inferred)

Joined paths that traverse outside the configured storage root now return an error instead of being used. This check applies to file-backup read, list, start, and remove operations.

Show release-note lines
### Security 
#### Backup and Restore
 * [release-23.0] Address dir traversal in file backup storage `GetBackups` RPC (#18814) [#18818](https://github.com/vitessio/vitess/pull/18818) 
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Java JDBC driver vulnerability fixed by replacing commons-lang

Affectssetups using the Vitess Java JDBC driver(Inferred)

The driver previously used commons-lang 2.6 and imported org.apache.commons.lang.StringUtils; after the upgrade, it uses commons-lang3 3.19.0 and imports org.apache.commons.lang3.StringUtils.

Show release-note lines
#### Java
 * [release-23.0] Resolve `commons-lang` vulnerability in Java driver (#18768) [#18797](https://github.com/vitessio/vitess/pull/18797) 
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VTAdmin JavaScript dependencies updated

Affectssetups using VTAdmin

The updates are intended to address Dependabot vulnerabilities in VTAdmin’s JavaScript dependencies.

Show release-note lines
#### VTAdmin
 * [release-23.0] Address `Moderate` dependabot vulns in VTAdmin (#18744) [#18750](https://github.com/vitessio/vitess/pull/18750)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VTAdmin dependency updates address Dependabot alerts

Affectssetups using VTAdmin(Inferred)

VTAdmin dependencies had triggered Dependabot alerts. The package lockfile now includes updates intended to resolve them, along with updates to other packages.

Show release-note lines
 * [release-23.0] Address `Moderate` dependabot vulns in VTAdmin (#18744) [#18750](https://github.com/vitessio/vitess/pull/18750)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VTAdmin Vite dependencies updated for security

Affectssetups using VTAdmin(Inferred)

The previous dependency ranges had Dependabot security alerts. The manifest and lockfile now use vite ^7.1.12, @vitejs/plugin-react ^5.1.0, vite-plugin-svgr ^4.5.0, and vitest ^4.0.3.

Show release-note lines
 * [release-23.0] vtadmin: upgrade vite to the latest (#18803) [#18812](https://github.com/vitessio/vitess/pull/18812) 
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Breaking changes27

Four deprecated VTGate metrics removed

AffectsVTGate monitoring dashboards or alerting systems using any of the four removed metrics

The metrics had been deprecated in v22.0.0 and are no longer provided. QueryExecutions replaces QueriesProcessed, QueryRoutes replaces QueriesRouted, and QueryExecutionsByTable replaces both by-table metrics.

Show release-note lines
Four deprecated VTGate metrics have been completely removed in v23.0.0. These metrics were deprecated in v22.0.0:
| Metric Name               | Component | Deprecated In |
|---------------------------|-----------|---------------|
| `QueriesProcessed`        | vtgate    | v22.0.0       |
| `QueriesRouted`           | vtgate    | v22.0.0       |
| `QueriesProcessedByTable` | vtgate    | v22.0.0       |
| `QueriesRoutedByTable`    | vtgate    | v22.0.0       |
**Impact**: Any monitoring dashboards or alerting systems using these metrics must be updated to use the replacement metrics introduced in v22.0.0:
- Use `QueryExecutions` instead of `QueriesProcessed`
- Use `QueryRoutes` instead of `QueriesRouted`
- Use `QueryExecutionsByTable` instead of `QueriesProcessedByTable` and `QueriesRoutedByTable`
See the [v22.0.0 release notes](https://github.com/vitessio/vitess/blob/main/changelog/22.0/22.0.0/release_notes.md#new-vtgate-metrics) for details on the new metrics.
| Component |        Metric Name        | Was Deprecated In |                     Deprecation PR                      |
|:---------:|:-------------------------:|:-----------------:|:-------------------------------------------------------:|
| `vtgate`  |    `QueriesProcessed`     |     `v22.0.0`     | [#17727](https://github.com/vitessio/vitess/pull/17727) |
| `vtgate`  |      `QueriesRouted`      |     `v22.0.0`     | [#17727](https://github.com/vitessio/vitess/pull/17727) |
| `vtgate`  | `QueriesProcessedByTable` |     `v22.0.0`     | [#17727](https://github.com/vitessio/vitess/pull/17727) |
| `vtgate`  |  `QueriesRoutedByTable`   |     `v22.0.0`     | [#17727](https://github.com/vitessio/vitess/pull/17727) |
github.com/vitessio/vitess/releases/tag/v23.0.0

Default MySQL version for vitess/lite:latest changes to 8.4.6

Affectsthe vitess/lite:latest image
Action requiredFor vitess-operator, the one-time 8.0.x to 8.4.x sequence: add innodb_fast_shutdown=0 to the YAML extra cnf and apply it; wait for all pods to be healthy; change the YAML to use the new Docker images; then remove the setting and apply the YAML again.

The tag previously selected MySQL 8.0.40; after upgrading, it selects 8.4.6 without a change to the tag.

Show release-note lines
The default major MySQL version used by our `vitess/lite:latest` image is going from `8.0.40` to `8.4.6`.
This change was merged in [#18569](https://github.com/vitessio/vitess/pull/18569).
 * Update MySQL 8.4 to be the default [#18569](https://github.com/vitessio/vitess/pull/18569)
#### Online DDL
 * Online DDL: support `alter vitess_migration ... postpone complete` syntax [#18118](https://github.com/vitessio/vitess/pull/18118)
github.com/vitessio/vitess/releases/tag/v23.0.0

VTGate now advertises MySQL version 8.4.6 by default

AffectsVTGate deployments
Action requiredIf the desired advertised MySQL version is not 8.4.6, set the mysql_server_version flag to that version.

Previously, VTGate advertised MySQL version 8.0.40; the new default may differ from the MySQL version you are running.

Show release-note lines
VTGate also advertises MySQL version `8.4.6` by default instead of `8.0.40`. If that is not what you are running, you can set the `mysql_server_version` flag to advertise the desired version.
 * Update MySQL 8.4 to be the default [#18569](https://github.com/vitessio/vitess/pull/18569)
github.com/vitessio/vitess/releases/tag/v23.0.0

VTGate QueryExecutionsByTable counts successful queries only

Affectssetups that collect or use the VTGate QueryExecutionsByTable metric(Inferred)

Previously, failed query attempts were included, so the metric could overstate successful query volume. Failed queries are now tracked separately by error metrics, and values may decrease for workloads with significant failures.

Show release-note lines
#### VTGate QueryExecutionsByTable Behavior Change
The `QueryExecutionsByTable` metric now only counts successful query executions ([PR #18584](https://github.com/vitessio/vitess/pull/18584)). Previously, it counted all query attempts regardless of success/failure.
**Impact**:
- Metric values may decrease if your workload had significant query failures
- More accurate representation of successful query volume
- Failed queries are tracked separately via error metrics
 * fix: emit QueryExecutionsByTable for success cases only [#18584](https://github.com/vitessio/vitess/pull/18584) 
github.com/vitessio/vitess/releases/tag/v23.0.0

VTTablet --skip-user-metrics flag

AffectsVTTablet setups emitting user-based metrics

In environments with many unique users, per-user username labels can cause metric cardinality explosion. When --skip-user-metrics is enabled, the username label is replaced with UserLabelDisabled.

Show release-note lines
- `--skip-user-metrics` flag if enabled, replaces the username label with "UserLabelDisabled" to prevent metric explosion in environments with many unique users ([PR #18085](https://github.com/vitessio/vitess/pull/18085)).
| `--skip-user-metrics` | vttablet | If enabled, replaces the username label in user-based metrics with "UserLabelDisabled" to prevent metric cardinality explosion in environments with many unique users. | [#18085](https://github.com/vitessio/vitess/pull/18085) |
 * [vttablet] Emit Constant “userLabelDisabled” When skip-user-metrics is Enabled [#18085](https://github.com/vitessio/vitess/pull/18085)
github.com/vitessio/vitess/releases/tag/v23.0.0

Vitess Bullseye Docker images no longer built or published

AffectsVitess Docker images based on debian:bullseye

Builds continue for Debian Bookworm and add Debian Trixie; the default Debian tag remains unchanged.

Show release-note lines
[Bullseye went EOL 1 year ago](https://www.debian.org/releases/), so starting from v23, we will no longer build or publish images based on debian:bullseye ([PR #18609](https://github.com/vitessio/vitess/pull/18609)).
Builds will continue for Debian Bookworm, and add the recently released Debian Trixie. v23 explicitly does not change the default Debian tag to Trixie.
 * docker: add trixie and rm bullseye from build matrix [#18609](https://github.com/vitessio/vitess/pull/18609)
github.com/vitessio/vitess/releases/tag/v23.0.0

Datadog tracer debug mode now defaults to off

Affectsinstallations using the Datadog tracing plugin(Inferred)

Previously, the plugin always enabled debug mode, producing extremely verbose logging that could reach millions of logs depending on traffic. The --datadog-trace-debug-mode option turns it on.

Evidence“Previously debug mode was hardcoded to true for the tracer in the datadog plugin, which made logging extremely verbose. This can easily add up to millions of logs depending on the amount of traffic your application receives, which can be very costly.” vitessio/vitess/pull/18347 ↗
Show release-note lines
 * Configure datadog trace debug mode [#18347](https://github.com/vitessio/vitess/pull/18347)
| `--datadog-trace-debug-mode` | All components | Makes Datadog trace debug mode configurable instead of always-on. Default: false. | [#18347](https://github.com/vitessio/vitess/pull/18347) |
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Immediate Online DDL cut-over for positive --force-cut-over-after values of <= 1ms

AffectsOnline DDL with a positive --force-cut-over-after value of <= 1ms

Previously, forced cut-over waited until sinceReadyToComplete exceeded the configured value. Now cut-over can happen even when the measured elapsed time is lower.

Evidence“- When `--force-cut-over-after` value is `<= 1ms` we consider it as "immediate" even if we somehow measure the time-since-ready to be less than that.” vitessio/vitess/pull/18423 ↗
Show release-note lines
 * Online DDL cutover enhancements [#18423](https://github.com/vitessio/vitess/pull/18423)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VTOrc restarts direct replicas for unreachable primaries

AffectsVTOrc-managed replication

For UnreachablePrimary, VTOrc stops and starts replication on one arbitrary direct replica. If only some replicas are failing to replicate, it classifies the condition as UnreachablePrimaryWithBrokenReplicas and restarts all direct replicas; restarts are limited to one per minute per tablet.

Evidence“However, if there is a non-empty subset of replicas that are failing to replicate (and these are **not** all of the replicas) then we analyze as a new `UnreachablePrimaryWithBrokenReplicas`. This scenario is very highly suspicious of really being an early stage for a `DeadPrimary` scenario, and we want to find out sooner rather than later. Here, we restart all replicas.” vitessio/vitess/pull/18626 ↗
Show release-note lines
 * `vtorc`: implement `restartDirectReplicas` as response to `UnreachablePrimary` [#18626](https://github.com/vitessio/vitess/pull/18626) 
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Deprecated VTGate metrics and engine primitive methods removed

Affectssetups using deprecated VTGate metrics or engine primitive methods(Inferred)

The removed VTGate metrics include QueriesProcessed.

Evidence“This PR removed the deprecated metrics on VTGate and removed deprecated methods on engine primitive.” vitessio/vitess/pull/18149 ↗
Show release-note lines
 * Remove deprecated methods and metrics [#18149](https://github.com/vitessio/vitess/pull/18149) 
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Multi-statement ExecuteFetchAsDba requests rejected

Affectscode or automation submitting multiple semicolon-separated SQL statements to ExecuteFetchAsDba
Action requiredEach statement must be sent in a separate RPC call.

Previously, requests were accepted when every statement was CREATE TABLE or CREATE VIEW; that exception no longer applies.

Show release-note lines
#### <a id="executefetchasdba-multistatement"/>ExecuteFetchAsDba No Longer Accepts Multi-Statement SQL</a>
The `ExecuteFetchAsDba` RPC method in TabletManager now explicitly rejects SQL queries containing multiple statements (as of [PR #18183](https://github.com/vitessio/vitess/pull/18183)).
**Impact**: Code or automation that previously passed multiple semicolon-separated SQL statements to `ExecuteFetchAsDba` will now receive an error. Each SQL statement must be sent in a separate RPC call.
**Migration**: Split multi-statement SQL into individual RPC calls:
```go
// Before (no longer works):
ExecuteFetchAsDba("CREATE TABLE t1 (id INT); CREATE TABLE t2 (id INT);")
// After (required in v23+):
ExecuteFetchAsDba("CREATE TABLE t1 (id INT);")
ExecuteFetchAsDba("CREATE TABLE t2 (id INT);")
```
 * tablet manager's `ExecuteFetchAsDba` does not allow multiple queries [#18183](https://github.com/vitessio/vitess/pull/18183) 
github.com/vitessio/vitess/releases/tag/v23.0.0

Correct error codes from the vttablet tabletmanager client

Affectssetups using the vttablet gRPC tabletmanager client
Action requiredExternal automation relying on google-gRPC error codes must be updated to inspect codes with vterrors.Code(err) and use vtrpcpb.Code values, such as vtrpcpb.Code_NOT_FOUND.

When a tabletmanager RPC failed to execute—for example, because mysqld was down—the client could report Unknown; now that case reports Unavailable, with the error message unchanged.

Evidence“Now tablets with downed-`mysqld` will return the gRPC `Unavailable` code with the error message unchanged, for example” vitessio/vitess/pull/18565 ↗
Show release-note lines
#### <a id="grpc-error-codes"/>gRPC TabletManager Error Code Changes</a>
The `vttablet` gRPC `tabletmanager` client now returns errors wrapped by the internal `go/vt/vterrors` package ([PR #18565](https://github.com/vitessio/vitess/pull/18565)).
**Impact**: External automation relying on google-gRPC error codes must be updated to use `vterrors.Code(err)` to inspect error codes, which returns `vtrpcpb.Code`s defined in [proto/vtrpc.proto](https://github.com/vitessio/vitess/blob/main/proto/vtrpc.proto#L60).
**Migration**:
```go
// Before:
if status.Code(err) == codes.NotFound { ... }
// After:
if vterrors.Code(err) == vtrpcpb.Code_NOT_FOUND { ... }
```
#### <a id="grpctmclient-err-changes"/>gRPC `tabletmanager` client error changes</a>
The `vttablet` gRPC `tabletmanager` client now returns errors wrapped by the internal `go/vt/vterrors` package ([PR #18565](https://github.com/vitessio/vitess/pull/18565)). External automation relying on google-gRPC error codes should now use `vterrors.Code(err)` to inspect the code of an error, which returns `vtrpcpb.Code`s defined in [the `proto/vtrpc.proto` protobuf](https://github.com/vitessio/vitess/blob/main/proto/vtrpc.proto#L60).
See [Breaking Changes](#grpc-error-codes) for migration guidance.
 * `tabletmanager`/`grpctmclient`: use `vtrpcpb`/gRPC error codes [#18565](https://github.com/vitessio/vitess/pull/18565)
github.com/vitessio/vitess/releases/tag/v23.0.0

GTID parsing method adds commit and sequence values

Affectscode calling the GTID parsing APIs directly
Action requiredUpdates to direct callers of the GTID parsing APIs to accommodate the changed method signature

Previously, BinlogEvent.GTID() returned only the GTID, hasBegin, and an error; its signature now also includes lastCommitted and sequenceNumber.

Show release-note lines
Several GTID-related API signatures changed in [PR #18196](https://github.com/vitessio/vitess/pull/18196) as part of GTID performance optimizations:
**Changed**: `BinlogEvent.GTID()` method signature
**Impact**: Code directly using the GTID parsing APIs may need updates. Most users are unaffected as these are internal APIs.
github.com/vitessio/vitess/releases/tag/v23.0.0

key.GenerateShardRanges() now accepts a hex-width parameter

Affectscode that calls key.GenerateShardRanges() directly
Action requiredDirect callers must update their calls to pass the new parameter.

Previously, callers supplied only the shard count. The new hexChars value controls the hex width of generated shard names.

Show release-note lines
#### <a id="generateshardranges-api"/>GenerateShardRanges API Signature Change</a>
The `key.GenerateShardRanges()` function signature changed in [PR #18633](https://github.com/vitessio/vitess/pull/18633) to add a new `hexChars int` parameter controlling the hex width of generated shard names.
**Impact**: Code calling `GenerateShardRanges()` directly must be updated to pass the new parameter.
---
github.com/vitessio/vitess/releases/tag/v23.0.0

Vitess query buffering during eligible DDL changes

Affectseligible INSTANT DDL migrations and range partition rotation changes
Action requiredAn instant-able migration with --prefer-instant-ddl, or a range partition rotation change.

This reduces query failures while the schema change runs and is transparent to applications.

Show release-note lines
Query buffering has been implemented for `INSTANT` DDL operations ([PR #17945](https://github.com/vitessio/vitess/pull/17945)), reducing query failures during schema changes.
- Automatic buffering of queries during INSTANT DDL execution
- Transparent to applications
**Impact**: Applications experience fewer query errors during schema changes, improving availability during DDL operations.
 * Query buffering, terminating blocking transactions for `INSTANT` DDL and other "special plans" [#17945](https://github.com/vitessio/vitess/pull/17945)
github.com/vitessio/vitess/releases/tag/v23.0.0

Lock-holder termination before eligible special-operation DDL

Affectseligible instant DDL and range partition rotation operations with nonzero --force-cut-over-after

Previously, these operations ran the DDL directly. Now, queries and transactions holding locks or metadata locks on the migrated table are terminated before ALTER TABLE; the flag's value does not change whether this happens, and termination is skipped while an atomic transaction is pending for the table.

Evidence“In addition, if `--force-cut-over-duration` flag is nonzero, and irrespective of its value, we also issue a one time termination for queries and transactions holding locks or metadata locks on the migrated table, just before issuing the `ALTER TABLE` statement.” vitessio/vitess/pull/17945 ↗
Show release-note lines
- Forced termination of blocking transactions
 * Query buffering, terminating blocking transactions for `INSTANT` DDL and other "special plans" [#17945](https://github.com/vitessio/vitess/pull/17945)
github.com/vitessio/vitess/releases/tag/v23.0.0

Cgroup CPU and memory metrics now require cgroup v2

AffectsLinux installations using cgroup v1

Previously, Vitess collected CPU and memory metrics from both cgroup v1 and v2. With cgroup v1 or failed cgroup metric setup, it now warns and uses host metrics; cgroup v2 continues to use cgroup metrics.

Evidence“func getCgroup1CpuUsage() (uint64, error) {” vitessio/vitess/pull/18801 ↗
Show release-note lines
#### Observability
 * [release-23.0] Improve cgroup metric management (#18791) [#18801](https://github.com/vitessio/vitess/pull/18801) 
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VStream diagnostic logging changes

Affectsclusters using VStream(Inferred)

The added lines are intended to help localize frequent EOF errors in a cluster. One VStream error log changes from Errorf to Infof.

Show release-note lines
 * VStream API: add additional log lines for debugging frequent eof errors during catchup [#18124](https://github.com/vitessio/vitess/pull/18124)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VReplication stops indefinitely retrying MySQL error 1419

AffectsVReplication workflows

The error can occur when a workflow creates a DEFINER trigger; before this change, VReplication did not handle it and could retry the workflow indefinitely.

Evidence“name: "SQL error with ERBinlogCreateRoutineNeedSuper"” vitessio/vitess/pull/18820 ↗
Show release-note lines
 * [release-23.0] VReplication: Treat ER_BINLOG_CREATE_ROUTINE_NEED_SUPER as unrecoverable (#18784) [#18820](https://github.com/vitessio/vitess/pull/18820) 
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VTTablet reports stale replica heartbeats as errors

Affectsreplica tablets using the heartbeat reader(Inferred)

When MySQL stalls and no heartbeat has been successfully read for more than two configured heartbeat intervals, vttablet could keep reporting MySQL as healthy. Now the heartbeat status returns an error and signals VTGate that the tablet is unhealthy.

Evidence“The workaround I'm proposing is to change `*heartbeatReader.Status` func to just disregard any previously read heartbeat data if the last time the heartbeat was successfully read is older than two times the configured interval. It feels a bit hacky, but works reliably in identifying that MySQL is unhealthy and very quickly signals to `vtgate` that the tablet is unhealthy.” vitessio/vitess/pull/17883 ↗
Show release-note lines
 * Fix `vttablet` not being marked as not serving when MySQL stalls [#17883](https://github.com/vitessio/vitess/pull/17883)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

InitAuthServerClientCert now takes an explicit CA value

AffectsGo code calling go/mysql's public InitAuthServerClientCert function, including the VTGate plugin initializer(Inferred)

Previously, the function looked up mysql-server-ssl-ca, falling back to mysql_server_ssl_ca when the first flag was empty. It now takes the CA value as a second argument, which the VTGate plugin initializer supplies through vtgate.GetMysqlServerSSLCA().

Evidence“func InitAuthServerClientCert(clientcertAuthMethod string, caValue string) {” vitessio/vitess/pull/18508 ↗
Show release-note lines
 * Set up better dependency checks [#18508](https://github.com/vitessio/vitess/pull/18508)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Added lite:mysql80 Docker image build

Affectsbuilds selecting the lite:mysql80 image(Inferred)

Previously, the lite image build matrix included latest, mysql84, and percona80, but not mysql80.

Show release-note lines
 * build `lite:mysql80` docker image [#18692](https://github.com/vitessio/vitess/pull/18692)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Forced cut-over now terminates table lock holders during RENAME

AffectsOnline DDL migrations using forced cut-over

Previously, a long-running query could start between the pre-cut-over termination and the RENAME, leaving it holding a lock on the migrated table. The additional termination pass excludes the lock and rename connections.

Evidence“With forced cut-over, we now kill queries and transactions holding onto locks on migrated table, not only _before_ the cut-over, but also while the `RENAME` is being applied. Without this, there's a race condition where a long running query could start running just after queries are killed and right before the `RENAME` starts running.” vitessio/vitess/pull/18423 ↗
Show release-note lines
 * Online DDL cutover enhancements [#18423](https://github.com/vitessio/vitess/pull/18423)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Online DDL cut-over lock-wait timeouts shortened

AffectsOnline DDL cut-over migrations(Inferred)

The locking connection's timeout changes from five times onlineDDL.CutOverThreshold to three times the threshold. The rename connection's timeout changes from five times the threshold times four to twice the threshold.

Evidence“- Sanitized and reduced query and lock timeouts during the cut-over. There were some excessive timeouts, notably an overlooked `5*onlineDDL.CutOverThreshold*4` value which evaluates to `5min` on a `15s` timeout.” vitessio/vitess/pull/18423 ↗
Show release-note lines
 * Online DDL cutover enhancements [#18423](https://github.com/vitessio/vitess/pull/18423)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VTOrc database_instance location fields replaced by informational cell

AffectsVTOrc installations using the database_instance table(Inferred)

The removed fields were not used in logic; physical_environment and region were always undefined or empty, while data_center matched the tablet cell. The new cell field is not used in logic yet.

Evidence“The 3 x fields are replaced by the new `cell` field. It isn't used in any logic yet - for now it is informational” vitessio/vitess/pull/18339 ↗
Show release-note lines
 * `vtorc`: cleanup `database_instance` location fields [#18339](https://github.com/vitessio/vitess/pull/18339)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VTOrc database_instance schema replaces location fields with cell

AffectsVTOrc installations using the database_instance table(Inferred)

Previously, the table had data_center, physical_environment, and region fields, which the pull request says were not used in logic. The replacement cell field is informational and is not used in logic yet.

Evidence“The 3 x fields are replaced by the new `cell` field. It isn't used in any logic yet - for now it is informational” vitessio/vitess/pull/18339 ↗
Show release-note lines
 * `vtorc`: cleanup `database_instance` location fields [#18339](https://github.com/vitessio/vitess/pull/18339)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

VTOrc's aggregated discovery metrics API removed

AffectsIntegrations using VTOrc's /api/aggregated-discovery-metrics endpoint(Inferred)

The endpoint previously returned JSON of aggregated discovery samples over a 120-second period.

Evidence“This PR drops the undocumented VTOrc API endpoint `/api/aggregated-discovery-metrics`” vitessio/vitess/pull/18672 ↗
Show release-note lines
 * `vtorc`: remove aggregated discovery metrics HTTP API, cleanup code [#18672](https://github.com/vitessio/vitess/pull/18672)
#### <a id="aggregated-discovery-metrics-api-removed"/>Aggregated Discovery Metrics HTTP API removed</a>
VTOrc's undocumented `/api/aggregated-discovery-metrics` HTTP API endpoint was removed ([PR #18672](https://github.com/vitessio/vitess/pull/18672)). The list of documented VTOrc APIs can be found [here](https://vitess.io/docs/current/reference/vtorc/ui_api_metrics/#apis).
We recommend using the standard VTOrc metrics to gather the same metrics. If you find that a metric is missing in standard metrics, please open an issue or PR to address this.
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Deprecations15

Underscore-form CLI flags deprecated

Affectsunderscore-form names of the 989 migrated CLI flags
Removed inv25.0.0

Previously, a flag spelling that did not match the form bound to Viper could break or do nothing. In v23.0.0 and v24.0.0, both forms are accepted and normalized to dashed names; underscore forms are hidden from help and produce a deprecation message.

Show release-note lines
### <a id="flag-naming-convention-migration"/>Flag Naming Convention Migration</a>
Vitess v23.0.0 includes a major standardization of CLI flag naming conventions across all binaries. **989 flags** have been migrated from underscore notation (`flag_name`) to dash notation (`flag-name`) in [PR #18280](https://github.com/vitessio/vitess/pull/18280) and related PRs.
#### Backward Compatibility
- **v23.0.0 and v24.0.0**: Both underscore and dash formats are supported. Underscore format is **deprecated** but functional.
- **v25.0.0**: Underscore format will be **removed**. Only dash format will be accepted.
#### Automatic Normalization
Flag normalization happens automatically at the `pflag` level ([PR #18642](https://github.com/vitessio/vitess/pull/18642)), so both formats are accepted without requiring code changes in v23/v24.
#### Example Flag Renames
Common flags affected (full list of 989 flags available in PR #18280):
**Backup flags**:
- `--azblob_backup_account_name` → `--azblob-backup-account-name`
- `--s3_backup_storage_bucket` → `--s3-backup-storage-bucket`
- `--xtrabackup_root_path` → `--xtrabackup-root-path`
**Replication flags**:
- `--heartbeat_enable` → `--heartbeat-enable`
- `--replication_connect_retry` → `--replication-connect-retry`
**gRPC flags** ([PR #18009](https://github.com/vitessio/vitess/pull/18009)):
- All gRPC-related flags standardized (30+ flags)
#### Action Required
Users should update configuration files, scripts, and automation to use dash-based flag names before upgrading to v25.0.0. The migration is backward compatible in v23 and v24, allowing gradual updates.
github.com/vitessio/vitess/releases/tag/v23.0.0

VTOrc adds the DiscoveryInstanceTimings metric

AffectsVTOrc deployments consuming instance-discovery timing metrics(Inferred)
Removed inv24+

Both metrics receive instance-discovery action timings in this release. The old DiscoverInstanceTimings metric is planned for deprecation in v24 and deletion in v24+.

Show release-note lines
| `vtorc`   | `DiscoverInstanceTimings` | Replaced by `DiscoveryInstanceTimings` | [#18406](https://github.com/vitessio/vitess/pull/18406) |
 * `vtorc`: update metrics in e2e test `TestAPIEndpoints` [#18406](https://github.com/vitessio/vitess/pull/18406)
github.com/vitessio/vitess/releases/tag/v23.0.0

/api/replication-analysis deprecated in favor of /api/detection-analysis

AffectsVTOrc API clients using either analysis endpoint
Removed inv24+

Both endpoints use the same handler in this release and return the same response format. The old endpoint remains available until its planned removal in v24+.

Show release-note lines
#### <a id="replication-analysis-api-deprecation"/>`/api/replication-analysis` HTTP API deprecation</a>
The `/api/replication-analysis` HTTP API endpoint is now deprecated and is replaced with `/api/detection-analysis` ([PR #18615](https://github.com/vitessio/vitess/pull/18615)), which currently returns the same response format.
**Timeline**: The `/api/replication-analysis` endpoint will be removed in a future version. Users should migrate to `/api/detection-analysis`.
github.com/vitessio/vitess/releases/tag/v23.0.0

Managed MySQL authentication defaults to caching_sha2_password

AffectsManaged MySQL instances on MySQL 8.0.26 or later
Removed innot stated

Previously, the default was mysql_native_password, which remains enabled for backwards compatibility. The note recommends caching_sha2_password for replication users configured with an explicit password after upgrading to v23.

Show release-note lines
#### <a id="mysql-caching-sha2-password"/>Managed MySQL configuration defaults to caching-sha2-password</a>
The default authentication plugin for MySQL 8.0.26 and later is now `caching_sha2_password` instead of `mysql_native_password` ([PR #18010](https://github.com/vitessio/vitess/pull/18010)). This change is made because `mysql_native_password` is deprecated and removed in future MySQL versions. `mysql_native_password` is still enabled for backwards compatibility.
This change specifically affects the replication user. If you have a user configured with an explicit password, it is recommended to make sure to upgrade this user after upgrading to v23 with a statement like the following:
```sql
ALTER USER 'vt_repl'@'%' IDENTIFIED WITH caching_sha2_password BY 'your-existing-password';
```
In future Vitess versions, the `mysql_native_password` authentication plugin will be disabled for managed MySQL instances.
 * Switch to using the default caching sha2 password [#18010](https://github.com/vitessio/vitess/pull/18010)
github.com/vitessio/vitess/releases/tag/v23.0.0

Migrated gRPC flags use dashed names

Affectssetups using gRPC flags such as --grpc-auth-mode and --grpc-bind-address
Removed inv25

These flags previously used underscores; their dashed names are now available, while the underscore variants remain supported but are deprecated and hidden.

Show release-note lines
 * Refactor grpc flags for standardized naming  [#18009](https://github.com/vitessio/vitess/pull/18009)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Underscore flag names deprecated

Affectssetups using the migrated logging, database, tablet-manager gRPC, or statistics flags
Removed inv25

These flags used underscore names before the refactor. Dashed names are available now; underscore variants still work but are deprecated and hidden.

Show release-note lines
 * Refactor flags - Part 3 [#18064](https://github.com/vitessio/vitess/pull/18064)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Commonly reused Vitess flags migrate to dashed names

Affectssetups using migrated backup-storage, MySQL, topology, or tablet flags
Removed inv25

These flags previously used underscore names. Their dashed names are now available, while the underscore variants remain supported but are deprecated and hidden.

Show release-note lines
 * Refactor flags - Part 4 [#18095](https://github.com/vitessio/vitess/pull/18095)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Dashed names added for vtctld flags

Affectssetups using vtctld flags such as --disable-active-reparents and --opentsdb-uri
Removed innot stated

The flags previously used underscore naming. Their dashed forms are now available; the underscore forms remain supported but are deprecated and hidden.

Show release-note lines
 * Refactor `vtctld` flags to follow standard naming convention [#18294](https://github.com/vitessio/vitess/pull/18294)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Vitess flags migrated to dashed names

Affectssetups using the migrated DBA pool, VTGate/Vtctld gRPC, client protocol, query logging, external-topology, or Ceph backup-storage flags
Removed innot stated

The underscore-named variants remain supported, but are now deprecated and hidden.

Show release-note lines
 * Flags Refactor - Part 5 [#18296](https://github.com/vitessio/vitess/pull/18296)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Migrated vtcombo flags use dashed names

Affectssetups using the migrated flags in the vtcombo binary
Removed innot stated

Their underscore-named forms remain supported, but are deprecated and hidden.

Show release-note lines
 * Refactor `vtcombo` flags - Part 2 [#18297](https://github.com/vitessio/vitess/pull/18297)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

vtcombo flags move to dashed names

Affectsmigrated flags in the vtcombo binary
Removed innot stated

Before the refactor, these flags used underscores. Their dashed names are now available; underscore variants remain supported but are deprecated and hidden.

Show release-note lines
 * Refactor `vtcombo` flags - Part 3 [#18298](https://github.com/vitessio/vitess/pull/18298)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Affected command-line flags standardized to dashed names

AffectsVitess deployments invoking mysqlctld, mysqlctl, or vtbackup commands with the affected flags
Removed inv25

The corresponding flags previously used underscore spellings, including init_db_sql_file, socket_file, and wait_time.

Show release-note lines
 * Refactor `mysqlctld` flags to follow standardized naming [#18432](https://github.com/vitessio/vitess/pull/18432)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

47 vtcombo flags gain dashed names

Affectsvtcombo configurations using the migrated flags
Removed inv25

The affected flags previously used underscores; the PR lists --relay-log-max-items and --restore-from-backup among the dashed spellings.

Show release-note lines
 * Refactor `vtcombo` flags - Part 4 [#18422](https://github.com/vitessio/vitess/pull/18422) 
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

/api/replication-analysis deprecated in favor of /api/detection-analysis

AffectsVTOrc clients using /api/replication-analysis(Inferred)
Removed innot stated

The replacement endpoint returns the same response format.

Show release-note lines
 * `vtorc`: rename `ReplicationAnalysis` -> `DetectionAnalysis` [#18615](https://github.com/vitessio/vitess/pull/18615)
github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Important fixes49Silent failure3

  • mysqlctl environment variables propagated to mysqld
    Affectsmysqlctl deployments with environment variables such as a non-UTC TZ setting

    Previously, TZ set for mysqlctl was ignored by mysqld, so timezone settings from the environment did not affect DATETIME interpretation. mysqld now inherits those variables, and deployments relying on the old behavior may see DATETIME values interpreted differently.

    Fixed a bug where environment variables like `TZ` were not propagated from mysqlctl to the mysqld process ([PR #18561](https://github.com/vitessio/vitess/pull/18561)).
    As a result, timezone settings from the environment were previously ignored. Now mysqld correctly inherits environment variables.
    ⚠️ **Deployment Impact**: Deployments that relied on the old behavior and explicitly set a non-UTC timezone may see changes in how DATETIME values are interpreted. To preserve compatibility, set `TZ=UTC` explicitly in MySQL pods.
     * Pass envs to mysqld process [#18561](https://github.com/vitessio/vitess/pull/18561) 
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Underscored CLI flag handling fixed
    AffectsCLI flags spelled with underscores, especially those bound to Viper

    When an underscored flag was passed, Viper could miss its value because it was bound to a different flag object, so the setting could break or have no effect. Underscored names are now normalized to dashed names during parsing, so Viper receives the supplied value; they still produce a deprecation message.

     * Normalize flag names at the `pflag` level. [#18642](https://github.com/vitessio/vitess/pull/18642) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Evalengine tuple simplification preserves multi-column results
    Affectsevalengine tuple simplification for multi-column results, including CASE expressions in join conditions(Inferred)

    Before this fix, the simplifier wrapped multi-column results in a single Literal; a CASE expression in a join condition is a demonstrated scenario.

     * fix: Preserve multi-column TupleExpr in tuple simplifier [#18216](https://github.com/vitessio/vitess/pull/18216)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Evalengine comparison crashes fixed
    Affectsevalengine comparisons involving NULLs or JSON, ENUM, SET, or geometry values(Inferred)

    Comparisons involving NULLs or types evalengine did not handle properly, including JSON, ENUM, and SET, could cause a panic. The affected NULL checks and type-handling cases are fixed, so the described unexpected-type crashes no longer occur.

     * Fix evalengine crashes on unexpected types [#18254](https://github.com/vitessio/vitess/pull/18254) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • vtgate base-table insertion fixed for ignored vindex rows
    AffectsINSERT IGNORE statements using vindexes

    Previously, when a vindex reported an ignored row during INSERT IGNORE, a NULL vindex column could keep the row out of the lookup table and cause the base-table insertion to be skipped. Now vtgate can insert the row into the base table despite the vindex reporting it ignored.

     * bugfix: INSERT IGNORE not inserting rows [#18151](https://github.com/vitessio/vitess/pull/18151)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • LIMIT/OFFSET preserved when merging UNION queries
    AffectsUNION queries Vitess merges that use LIMIT or OFFSET(Inferred)

    Before this fix, merged UNION queries could miss their LIMIT/OFFSET.

     * fix: keep LIMIT/OFFSET even when merging UNION queries [#18361](https://github.com/vitessio/vitess/pull/18361)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Empty-input scalar aggregation literal results fixed
    Affectsqueries using scalar aggregations with literal values(Inferred)

    When the input was empty—for example, because a subquery's WHERE condition returned no rows—the literal was treated like a column reference and the example returned (NULL, 0) instead of (1, 0). The literal is now evaluated, producing the MySQL-compatible result (1, 0).

     * Fix scalar aggregation with literals in empty result sets [#18477](https://github.com/vitessio/vitess/pull/18477)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Prepared-statement field list fix for simple projections
    Affectsprepared statements with simple projections using the names-only optimization(Inferred)

    When GetFields called buildFields directly for a prepared statement with a simple projection, the names-only case produced an empty fields list.

     * Fix for simple projection showing no fields [#18489](https://github.com/vitessio/vitess/pull/18489)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Vitess planner fixes column counts for derived-table GROUP BY plans
    Affectsqueries with GROUP BY only on top of derived tables

    For these queries, the planner could report an incorrect projection width, allowing extraneous columns to leak into the result.

     * bugfix: Plan group by only on top of derived tables correctly [#18505](https://github.com/vitessio/vitess/pull/18505)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Throttler metric aggregation recognizes gRPC dial errorsSilent failure
    Affectssetups using throttler metric aggregation

    When a metric probe’s gRPC connection failed with Unavailable or DeadlineExceeded, aggregation treated it as an unhealthy state, causing throttler users such as VReplication to throttle.

     * Properly handle grpc dial errors in the throttler metric aggregation [#18073](https://github.com/vitessio/vitess/pull/18073)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Tablet throttler keeps its SrvKeyspace watch after errors
    Affectssetups using the tablet throttler's SrvKeyspace watch

    When the watch callback received an error, its listener was removed, so the throttler stopped reading SevKeyspace changes until it called Open() again, normally when the tablet type changed. The watch now stays active after an error.

     * Throttler: keep watching topo even on error [#18223](https://github.com/vitessio/vitess/pull/18223) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Atomic Copy post-copy action execution fixed
    Affectsworkflows using Atomic Copy with post-copy actions for copied tables

    copyAll() could miss executing post-copy actions for a table. Executed action records are now removed from _vt.post_copy_action along with the corresponding _vt.copy_state record.

     * Perform post copy actions in atomic copy [#18411](https://github.com/vitessio/vitess/pull/18411)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Replication tracker resets the replication-lag metric for primary tablets
    AffectsVTTablet setups using the replication tracker(Inferred)

    A previous lag value could remain after promotion to primary or when Status() ran while the tracker was primary or in Disable mode. The metric now resets to zero in those cases.

     * [release-23.0] repltracker: reset replica lag when we are primary (#18800) [#18807](https://github.com/vitessio/vitess/pull/18807)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Query consolidator waiter-cap fallback fixedSilent failure
    Affectsquery-serving setups using query consolidation(Inferred)

    When the waiter cap was exceeded, the consolidator could return an empty result without an error. Now the query runs independently and returns its result.

     * [release-23.0] Fix bug where query consolidator returns empty result without error when the waiter cap exceeded (#18782) [#18833](https://github.com/vitessio/vitess/pull/18833) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Incomplete range coverage in GenerateShardRanges fixedSilent failure
    Affectsshard-name generation with GenerateShardRanges(Inferred)

    For some shard counts, such as 49, the generated shard names did not cover the full range. They now cover the full keyspace.

     * fix: Fix `GenerateShardRanges` returning shard names that don't cover the full range [#18641](https://github.com/vitessio/vitess/pull/18641) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Online DDL progress corrected to 100% at ready_to_complete
    AffectsOnline DDL migrations that reach ready_to_complete

    At ready_to_complete, table-row estimation could leave reported progress at 87% or another value far from 100%.

     * Online DDL: set migration's progress to 100% once it's `ready_to_complete` [#18544](https://github.com/vitessio/vitess/pull/18544)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Impossible-query formatting fixed for UNION queries
    Affectsimpossible-query column metadata fetches for UNION statements

    When impossible queries fetched column names and types for a UNION without fetching data, the formatter did not reliably add the no-rows condition. It now includes where 1 != 1 in the formatted query, including its union branches.

     * bugfix: Fix impossible query for UNION [#18463](https://github.com/vitessio/vitess/pull/18463)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VStreamer filters send both images for matching non-sharded updates
    AffectsNon-sharded VStreamer workflows other than MoveTables and Reshard, with filters on row columns

    When an update changed columns used by the filter and either the Before or After image matched, only the passing image was sent, so downstream consumers could interpret the update as an insert or delete.

     * VStreamer: change in filter logic [#18319](https://github.com/vitessio/vitess/pull/18319)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VTOrc SkippedRecoveries metric gains a reason dimension
    AffectsVTOrc installations that emit or consume SkippedRecoveries metrics

    When VTOrc skips a recovery, the metric identifies reasons such as ERSDisabled, ReplicationLagHigh, and NotEnoughReplicas, and tracks previously missing skipped-recovery cases.

    |          Name                         |   Dimensions                                  |                   Description                        |                           PR                            |
    |:-------------------------------------:|:---------------------------------------------:|:----------------------------------------------------:|:-------------------------------------------------------:|
    | `SkippedRecoveries`                   | `RecoveryName`, `Keyspace`, `Shard`, `Reason` | Count of skipped recoveries with reason tracking.    | [#18644](https://github.com/vitessio/vitess/pull/18644) |
    **`SkippedRecoveries` Reasons**: The `Reason` dimension tracks why recoveries were skipped (e.g., "ERSDisabled", "ReplicationLagHigh", "NotEnoughReplicas"), providing actionable insights for operational troubleshooting.
     * `vtorc`: add `Reason` and missing cases to `SkippedRecoveries` metric [#18644](https://github.com/vitessio/vitess/pull/18644)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • CREATE PROCEDURE normalization fix for body SET statements
    Affectsstored procedures containing SET statements(Inferred)

    During planner normalization, SET y = 4 in a procedure body was changed to SET @@y = 4. Vitess now skips that normalization for CREATE PROCEDURE statements, leaving the body’s SET statement unchanged.

    - Support for `SET` statements within procedure bodies
     * Fix `SET` and `START TRANSACTION` in create procedure statements [#18279](https://github.com/vitessio/vitess/pull/18279)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Vitess fixes MEMBER OF precedence with AND
    AffectsJSON queries using MEMBER OF

    When these queries combined MEMBER OF with AND or other boolean logic, incorrect precedence could cause Vitess to send incorrect queries to the underlying MySQL instances. They are now evaluated using the corrected precedence.

    - Fixed `MEMBER OF` operator precedence with `AND` ([PR #18237](https://github.com/vitessio/vitess/pull/18237))
    - Ensures correct query evaluation when combining JSON operations with boolean logic
     * make sure to give MEMBER OF the correct precedence [#18237](https://github.com/vitessio/vitess/pull/18237)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Orphaned serving records cleared for deleted keyspaces
    Affectskeyspace rebuilding with RebuildKeyspace(Inferred)

    Previously, residual serving records left after deleting a keyspace caused vtgate to crash when RebuildKeyspace encountered the deleted keyspace. It now clears those records instead.

     * Add code to clear orphaned files for a deleted keyspace [#18098](https://github.com/vitessio/vitess/pull/18098) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Vreplication restart on failed Online DDL table rename
    AffectsOnline DDL cut-overs that stop vreplication before renaming tables(Inferred)

    If the remaining RENAME fails after vreplication has been stopped, the cut-over attempts to restart vreplication for that workflow.

    #### Online DDL
     * Online DDL: resume vreplication after cut-over/RENAME failure [#18428](https://github.com/vitessio/vitess/pull/18428) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • vtgate plan keys now distinguish tablet types
    Affectsvtgate workloads that plan and cache queries for different tablet types, such as primary and replica(Inferred)

    When vtgate reused a plan whose key did not distinguish tablet types, it could reuse an incorrect plan.

     * Fix: Add tablet type to the plan key [#18155](https://github.com/vitessio/vitess/pull/18155)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Repeated refresh notifications from resilient topology watchers fixed
    Affectssetups using resilient topology watchers(Inferred)

    During topology outages with cached data available, the watcher notified listeners on every refresh even while serving cached data. Now listeners remain silent, and Get operations continue working from the cache.

     * Fix watcher storm during topo outages [#18434](https://github.com/vitessio/vitess/pull/18434)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Traffic mirroring support for dual tables
    Affectssetups using traffic mirroring for queries involving dual tables(Inferred)

    Previously, a mirrored query involving a dual table with no mirror-rule entry could panic. The query is now processed without mirroring the dual table.

     * go/vt/vtgate: handle dual tables in traffic mirroring [#18458](https://github.com/vitessio/vitess/pull/18458)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Vitess fixes column alias handling in UNION planning
    Affectsqueries using column aliases in UNIONs(Inferred)

    When planning a UNION, Vitess had difficulty handling column aliases; the example uses aliases in both branches of a UNION ALL.

     * fix: handle aliases in UNIONs better [#18484](https://github.com/vitessio/vitess/pull/18484)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Vitess routed-table foreign key handling fixed
    Affectssetups with foreign-key relations and routed tables

    After MoveTables with SwitchWrites, a child table in the source keyspace could find its routed parent in the target keyspace, causing the parent to include a source-keyspace child and creating broken foreign key references. Now, foreign key relationships are added only for routed tables in the target keyspace, not for source-keyspace tables.

     *  Fix foreign key relation with routed tables [#18537](https://github.com/vitessio/vitess/pull/18537)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Invalid srvtopo cache entries now refresh
    Affectssrvtopo lookups

    Within the cache interval, a cached error could be returned immediately instead of querying the source again, causing calls such as show vitess_shards to fail with context cancellation or timeouts. Now an invalid cache entry or cached error triggers a refresh and waits for fresh results; a still-valid cached value is returned without another query.

     * `srvtopo/query.go`: Do not query errors, fall back and refresh [#18589](https://github.com/vitessio/vitess/pull/18589)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Vitess adds aliases to self-referential foreign-key verification queries
    Affectsself-referential foreign keys using the RESTRICT action

    When Vitess plans verification queries for these foreign keys, the queries self-joined the table without an alias for the joined table and failed on MySQL. They now include aliases for joined tables, avoiding that execution failure.

     * Introduce aliases for foreign keys verify operations [#18601](https://github.com/vitessio/vitess/pull/18601)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Connection-pool wait hang during close fixed
    Affectssetups using the connection pool(Inferred)

    When a connection is requested as the pool closes, the wait could hang and prevent normal operations such as PRS/ERS from succeeding.

     * CONNPOOL: Fix race condition when waiting for connection [#18713](https://github.com/vitessio/vitess/pull/18713)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VDiff extra-row reconciliation panic fixed
    AffectsVDiff runs that reconcile extra rows

    VDiff could panic when extra source or target rows exceeded --max-extra-rows-to-compare, or when the source and target returned different numbers of rows. Reconciliation now uses the lengths of the extra-row difference slices, avoiding the out-of-bounds access in these cases.

    #### VDiff
     * Fix a panic in VDiff when reconciling extra rows. [#18585](https://github.com/vitessio/vitess/pull/18585) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VStream catchup early EOF fixed
    AffectsVStream API catchup

    With multiple tables, catchup could return EOF before processing updates or deletes for tables or rows already copied during the copy phase. Resetting the fastforward-set stopPos prevents this early exit so catchup can process those transactions.

     * VStream API: Reset stopPos in catchup [#18119](https://github.com/vitessio/vitess/pull/18119)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • vcopier closed-channel panic no longer crashes tablets
    Affectstablet workloads using vcopier copy tasks

    If a copyAll callback sent a result to resultCh after it was closed—possibly when the context exceeded its deadline—the panic could crash the tablet. The panic is now recovered and logged instead.

     * Recover panic in vcopier due to closed channel [#18228](https://github.com/vitessio/vitess/pull/18228)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Atomic Copy table-streaming errors now propagated
    AffectsWorkflows using Atomic Copy while streaming tables

    When a stream error such as a connection timeout was ignored, the workflow could restart, re-enter the copy phase, and encounter duplicate-key errors. Now the error is propagated, and logs identify the failing table and configured net read and write timeouts.

     * Atomic Copy: Handle error that was ignored while streaming tables and log it [#18313](https://github.com/vitessio/vitess/pull/18313)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Atomic Copy workflows no longer terminate on replication errors
    AffectsVReplication workflows in Atomic Copy sub-mode that have completed the copy phase and entered the running state

    After the copy phase, a replication-phase error could terminate the workflow. Such errors are now handled normally instead.

     * Avoid terminating atomic copy workflows on error if they are out of copy phase [#18475](https://github.com/vitessio/vitess/pull/18475)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • MariaDB rejection of reverse-workflow VReplication reads fixed
    AffectsVReplication imports from MariaDB using a reverse workflow

    Reading VReplication workflows in these imports could fail because MariaDB rejected the query under stricter SQL grouping rules. The query no longer includes the GROUP BY clause that triggered the rejection.

     * VReplication: Fix bug while reading _vt.vreplication record [#18478](https://github.com/vitessio/vitess/pull/18478)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VStreamer concurrent-map crash fixed
    AffectsVStreamer event parsing in vttablet(Inferred)

    Concurrent map access during in-place GTID computation could crash vttablet with fatal error: concurrent map read and map write. VStreamer now uses replication.AppendGTID instead of the in-place operation.

     * Vstreamer: idempotent gtid set (bugfix) [#18611](https://github.com/vitessio/vitess/pull/18611)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VStream retries after purged-binlog errors
    AffectsVStream requests

    When a tablet lacks the requested GTID because the source purged the required binary logs, VStream previously did not ignore that tablet and therefore did not try another on that basis. It now retries with a different tablet, which may still have the requested binlog history.

     * VStream: Try new tablet on purged binlog error [#18710](https://github.com/vitessio/vitess/pull/18710)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VReplication handling of dashed identifiers fixed
    AffectsVReplication-related operations using keyspace, database, table, or sequence names that contain dashes

    These operations now escape identifiers such as the table keyspace, table name, database, and sequence before using them in SQL.

     * [release-23.0] VReplication: Ensure proper handling of keyspace/database names with dashes (#18762) [#18773](https://github.com/vitessio/vitess/pull/18773)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • etcd2topo shutdown panic fixed
    Affectssetups using the etcd2topo server implementation

    During VTGate shutdown, concurrent coroutines could access s.cli after Close() set it to nil, causing a nil pointer dereference panic. Such operations now return a shutdown signal (context.Canceled, converted to topo.Interrupted) instead of panicking.

     * Make sure to check if the server is closed in etcd2topo [#18352](https://github.com/vitessio/vitess/pull/18352)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Semi-sync monitor timer shutdown deadlock fixed
    Affectssetups running the VTTablet semi-sync monitor(Inferred)

    Closing the timer while holding mu could deadlock when checkAndFixSemiSyncBlocked also acquired it. The monitor now serializes timer Open and Close with a separate timer mutex and closes its ticks before acquiring mu.

     * Fix deadlock in semi-sync monitor [#18276](https://github.com/vitessio/vitess/pull/18276)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VTTablet semi-sync monitor deadlock fixed
    Affectssetups running the VTTablet semi-sync monitor(Inferred)

    When semi-sync was blocked and the monitor closed after a heartbeat write started but before setIsBlocked changed monitor state, appPool shutdown could deadlock: it waited for the write's connection to be recycled while the write thread waited for the mutex. The monitor now recycles the connection before waiting for the mutex, so shutdown no longer waits on a connection held by a blocked write.

     * Fix: Deadlock in `Close` and `write` in semi-sync monitor. [#18359](https://github.com/vitessio/vitess/pull/18359)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Recurring VStreamRows heartbeats during copy phases
    Affectslong-running VStreamRows operations

    Previously, the heartbeat mechanism sent one heartbeat and then exited during long-running table copies, including OnlineDDL copy phases and table copying during MoveTables/Reshard.

     * [Bugfix] Broken Heartbeat system in Row Streamer [#18390](https://github.com/vitessio/vitess/pull/18390)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • ValidateKeyspace deadlock fixed
    Affectssetups using ValidateKeyspace through vtctldclient(Inferred)

    Result writers could block indefinitely if they started writing before a reader was active. Now, results are processed and consumed before writing begins, so writers have an active reader.

    #### vtctldclient
     * Fix deadlock in `ValidateKeyspace` [#18114](https://github.com/vitessio/vitess/pull/18114)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • vttablet external MySQL connectivity check passes SSL configuration
    Affectsvttablet connections to external MySQL instances that require secure connections

    When vttablet checked connectivity to an external MySQL instance requiring secure connections, the check failed to pass SSL configuration, and MySQL's error prevented vttablet from starting. The check now passes SSL configuration to the connection logic, avoiding that startup error.

     * Pass SSL config when checking connection to external mysql instance [#18481](https://github.com/vitessio/vitess/pull/18481) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VTOrc prioritizes primary recovery over secondary mitigations
    AffectsVTOrc setups handling non-cluster-wide recovery analyses

    When a non-cluster-wide issue such as ReplicationStopped was caused by a dead primary, VTOrc could lock the shard to mitigate the secondary issue before recognizing the primary failure, delaying primary recovery. VTOrc now refreshes primary information before proceeding and aborts the stale analysis if primary mitigation is needed.

     * Vtorc: Recheck primary health before attempting a failure mitigation [#18234](https://github.com/vitessio/vitess/pull/18234)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Vitess Java JDBC driver isolation-variable lookup fixed
    AffectsVitess Java JDBC driver with MySQL 8.0 or MySQL 5.7.20 and later

    On MySQL 8.0, initialization previously queried tx_isolation, which was deprecated or deleted. The replacement, transaction_isolation, is backwards compatible with MySQL 5.7.20 and later.

     * Use transaction_isolation vs tx_isolation [#17845](https://github.com/vitessio/vitess/pull/17845)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VDiff sidecar schema updated to improve query performance
    Affectssetups running VDiff with its internal sidecar database(Inferred)

    When VDiff ran, poorly performing queries against the internal sidecar database could cause serious issues, including crashes of primary vttablets. The schema now uses bigint(20) for vdiff_log.id, vdiff_log.vdiff_id, and vdiff_table.vdiff_id, and adds the vdiff_id_idx index to improve some VDiff queries.

     * Fix: Improve VDiff internal query performance [#18579](https://github.com/vitessio/vitess/pull/18579) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Enhancements47

  • ExecuteMulti and StreamExecuteMulti APIs for VTGate

    To use Enable --mysql-server-multi-query-protocol on VTGate to use the feature.

    Vitess v23.0.0 introduces native support for executing multiple queries in a single RPC call through new `ExecuteMulti` and `StreamExecuteMulti` APIs ([PR #18059](https://github.com/vitessio/vitess/pull/18059)).
    This feature provides more efficient batch query execution without requiring manual query splitting or multiple round trips.
    **Usage Example**:
    ```go
    queries := []string{
        "SELECT * FROM users WHERE id = 1",
        "SELECT * FROM orders WHERE user_id = 1",
        "SELECT * FROM payments WHERE user_id = 1",
    }
    results, err := vtgateConn.ExecuteMulti(ctx, queries)
    ```
    **Configuration**: Enable with the `--mysql-server-multi-query-protocol` flag on VTGate.
     * Add a new implementation for handling multiple queries without needing to split them [#18059](https://github.com/vitessio/vitess/pull/18059)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Per-session transaction timeout control
    #### <a id="transaction-timeout-session-variable"/>Transaction Timeout Session Variable</a>
    A new `transaction_timeout` session variable has been added ([PR #18560](https://github.com/vitessio/vitess/pull/18560)), allowing per-session control over transaction timeout duration.
    **Usage**:
    ```sql
    -- Set transaction timeout to 30 seconds for this session
    SET transaction_timeout = 30;
    -- Begin a transaction that will automatically rollback if not committed within 30s
    BEGIN;
    -- ... perform operations ...
    COMMIT;
    ```
    This provides more granular timeout control compared to global server settings, useful for:
    - Long-running batch operations that need extended timeouts
    - Interactive sessions that should fail fast
    - Different timeout requirements per application workload
     * Add `transaction_timeout` session variable [#18560](https://github.com/vitessio/vitess/pull/18560) 
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Experimental incoming query throttling framework
    Vitess v23.0.0 introduces a new, experimental Query Throttler framework for rate-limiting incoming queries ([RFC issue #18412](https://github.com/vitessio/vitess/issues/18412), [PR #18449](https://github.com/vitessio/vitess/pull/18449), [PR #18657](https://github.com/vitessio/vitess/pull/18657)). Work on this new throttler is ongoing with the potential for breaking changes in the future.
    - File-based configuration for throttling rules
    - Dynamic rule reloading
    - `--query-throttler-config-refresh-interval` - How often to reload throttler configuration
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Multiple lookup vindexes in one vtctldclient workflow

    To use Use --params-file with a JSON file containing lookup vindex parameters; it is mutually exclusive with --type, --table-owner, and --table-owner-columns.

    #### <a id="multiple-lookup-vindexes-support"/>Multiple Lookup Vindexes Support</a>
    Creating multiple lookup vindexes in a single workflow is now supported through the `--params-file` flag ([PR #17566](https://github.com/vitessio/vitess/pull/17566)).
    **Usage**:
    ```bash
    # Create multiple lookup vindexes from JSON configuration
    vtctldclient LookupVindexCreate \
      --workflow my_lookup_workflow \
      --params-file /path/to/params.json \
      commerce
    **params.json example**:
    ```json
    {
      "vindexes": [
        {
          "name": "user_email_lookup",
          "type": "consistent_lookup_unique",
          "table_owner": "users",
          "table_owner_columns": ["email"]
        },
        {
          "name": "user_name_lookup",
          "type": "consistent_lookup",
          "table_owner": "users",
          "table_owner_columns": ["name"]
        }
      ]
    }
    ```
    This significantly improves workflow efficiency when setting up multiple vindexes, reducing the number of separate operations required.
    ```
    | `--params-file` | vtctldclient | JSON file containing lookup vindex parameters for creating multiple lookup vindexes in a single workflow. Mutually exclusive with `--type`, `--table-owner`, and `--table-owner-columns`. | [#17566](https://github.com/vitessio/vitess/pull/17566) |
     * LookupVindex: Multiple lookup tables support for `LookupVindexCreate` [#17566](https://github.com/vitessio/vitess/pull/17566)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Adding reference tables to existing materialize workflows

    To use Materialize ... update with --add-reference-tables and a target keyspace

    #### <a id="reference-tables-in-materialize-workflows"/>Reference Tables in Materialize Workflows</a>
    Reference tables can now be added to existing materialize workflows using the new `Materialize ... update` sub-command ([PR #17804](https://github.com/vitessio/vitess/pull/17804)).
    **Usage**:
    ```bash
    # Add reference tables to an existing workflow
    vtctldclient Materialize --workflow my_workflow update \
      --add-reference-tables ref_table1,ref_table2 \
      --target-keyspace my_keyspace
    **Use Case**: Incrementally add reference tables to running materialize workflows without recreating the entire workflow, improving operational flexibility.
    ```
    | `--add-reference-tables` | vtctldclient | Comma-separated list of reference tables to add to an existing materialize workflow using the `update` sub-command. | [#17804](https://github.com/vitessio/vitess/pull/17804) |
     * VReplication: Add reference-tables to existing materialize workflow [#17804](https://github.com/vitessio/vitess/pull/17804)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Recursive CTE support in Vitess
    Vitess now supports `WITH RECURSIVE` common table expressions ([PR #18590](https://github.com/vitessio/vitess/pull/18590)), enabling recursive queries for hierarchical data.
    **Example**:
    ```sql
    -- Find all employees in a management hierarchy
    WITH RECURSIVE employee_hierarchy AS (
        SELECT id, name, manager_id, 1 as level
        FROM employees
        WHERE manager_id IS NULL
        UNION ALL
        SELECT e.id, e.name, e.manager_id, eh.level + 1
        FROM employees e
        INNER JOIN employee_hierarchy eh ON e.manager_id = eh.id
    )
    SELECT * FROM employee_hierarchy ORDER BY level, name;
    ```
    This is a major SQL compatibility enhancement for applications with hierarchical or graph-like data structures.
    | `WITH RECURSIVE` | Recursive common table expressions for hierarchical queries | [#18590](https://github.com/vitessio/vitess/pull/18590) |
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Vitess SQL parser support for CREATE TABLE ... SELECT
    #### <a id="create-table-select-support"/>CREATE TABLE ... SELECT Support</a>
    The SQL parser now supports `CREATE TABLE ... SELECT` statements ([PR #18443](https://github.com/vitessio/vitess/pull/18443)), improving MySQL compatibility.
    **Example**:
    ```sql
    -- Create a table from a query result
    CREATE TABLE recent_orders
    SELECT * FROM orders
    WHERE order_date > DATE_SUB(NOW(), INTERVAL 30 DAY);
    ---
    ```
    | `CREATE TABLE ... SELECT` | Full support for creating tables from SELECT query results | [#18443](https://github.com/vitessio/vitess/pull/18443) |
     * Parser: Support CREATE TABLE ... SELECT Statement (#17983) [#18443](https://github.com/vitessio/vitess/pull/18443)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • VTGate adds a transaction counter by shard and type
    | `TransactionsProcessed`          | `Shard`, `Type` | Counts transactions processed at VTGate by shard distribution and transaction type. | [#18171](https://github.com/vitessio/vitess/pull/18171) |
    **Transaction Types in `TransactionsProcessed`**:
    - `Single` - Single-shard transactions
    - `Multi` - Multi-shard transactions
    - `TwoPC` - Two-phase commit transactions
    **Use Case**: The `TransactionsProcessed` metric helps identify transaction patterns and shard distribution, useful for:
    - Monitoring transaction types across your deployment
    - Identifying queries that could be optimized to single-shard
    - Tracking two-phase commit usage and potential bottlenecks
     * Add TransactionsProcessed metric to track transactions at VTGate [#18171](https://github.com/vitessio/vitess/pull/18171)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • VTGate adds a deferred-optimization query counter
    | `OptimizedQueryExecutions`       | N/A             | Counter tracking queries that used deferred optimization execution path.            | [#18067](https://github.com/vitessio/vitess/pull/18067) |
     * Add Deferred Optimization Execution Metric [#18067](https://github.com/vitessio/vitess/pull/18067)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Online DDL stale-migration age gauge added
    | `OnlineDDLStaleMigrationMinutes` | N/A                                | Minutes since the oldest pending/ready migration was submitted.                      | [#18417](https://github.com/vitessio/vitess/pull/18417) |
    **Use Case for `OnlineDDLStaleMigrationMinutes`**: Alert on stalled Online DDL migrations that haven't progressed for an extended period, helping identify migrations that may need intervention.
     * Online DDL metrics: `OnlineDDLStaleMigrationMinutes` [#18417](https://github.com/vitessio/vitess/pull/18417)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • VTOrc adds the EmergencyReparentShardDisabled gauge
    | `EmergencyReparentShardDisabled`      | `Keyspace`, `Shard`                           | Gauge indicating if ERS is disabled per keyspace/shard. | [#17985](https://github.com/vitessio/vitess/pull/17985) |
    **Use Case for `EmergencyReparentShardDisabled`**: Create alerts to ensure EmergencyReparentShard-based recoveries are not disabled for an undesired period, maintaining high availability posture.
    To provide observability of keyspaces/shards with EmergencyReparentShard-based VTOrc recoveries disabled, the `EmergencyReparentShardDisabled` metric was added. This metric label can be used to create alerting to ensure EmergencyReparentShard-based recoveries are not disabled for an undesired period of time.
     * `vtorc`: add support for dynamic enable/disable of ERS by keyspace/shard [#17985](https://github.com/vitessio/vitess/pull/17985)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Any-condition query logging in vtgate, vttablet, and vtcombo

    To use --querylog-emit-on-any-condition-met enabled (false by default)

    | `--querylog-emit-on-any-condition-met` | vtgate, vttablet, vtcombo | Changes query log emission to emit when ANY logging condition is met (row-threshold, time-threshold, filter-tag, or error) rather than requiring ALL conditions. Default: false. | [#18546](https://github.com/vitessio/vitess/pull/18546) |
     * Add support for querylog-emit-on-any-condition-met flag [#18546](https://github.com/vitessio/vitess/pull/18546)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • VTOrc startup recovery control

    To use --allow-recovery=false

    | `--allow-recovery` | vtorc | Boolean flag to disable all VTOrc recovery operations from startup. When false, VTOrc runs in monitoring-only mode. Default: true. | [#18005](https://github.com/vitessio/vitess/pull/18005) |
    **Use Case**: The `--allow-recovery=false` flag is useful for:
    - Testing VTOrc capacity/discovery performance ahead of a rollout, for example: migrating to VTOrc from another solution.
    - Maintenance windows where automatic failovers should be prevented
    - Debugging VTOrc behavior without triggering recoveries
    - Running VTOrc in observation-only mode
     * `vtorc`: allow recoveries to be disabled from startup [#18005](https://github.com/vitessio/vitess/pull/18005)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Configurable hex width for GenerateShardRanges shard labels

    To use --chars flag

    | `--chars` | vtctldclient | Specifies the hex width (number of hex characters) to use when generating shard ranges with `GenerateShardRanges` command. Allows fine-grained control over shard naming. | [#18633](https://github.com/vitessio/vitess/pull/18633) |
    **Example**:
    ```bash
    # Generate shard ranges with 4 hex characters
    vtctldclient GenerateShardRanges --shards 16 --chars 4
    # Output: -1000,1000-2000,2000-3000,...,f000-
    The corresponding vtctldclient command gained a new `--chars` flag to control this behavior.
     * feat: Allow specifying the hex width to use when generating shard ranges. [#18633](https://github.com/vitessio/vitess/pull/18633) 
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Support for ALTER VITESS_MIGRATION ... POSTPONE COMPLETE commands
    | `ALTER VITESS_MIGRATION ... POSTPONE COMPLETE` | Syntax for postponing Online DDL migration completion | [#18118](https://github.com/vitessio/vitess/pull/18118) |
     * Online DDL: support `alter vitess_migration ... postpone complete` syntax [#18118](https://github.com/vitessio/vitess/pull/18118)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Parser support for singular VALUE in INSERT and REPLACE
    | `VALUE` keyword in INSERT/REPLACE | Support for `VALUE` (singular) in addition to `VALUES` | [#18116](https://github.com/vitessio/vitess/pull/18116) |
     * Fix parsing to allow `VALUE` in insert and replace statements [#18116](https://github.com/vitessio/vitess/pull/18116)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • Per-keyspace and per-shard control for VTOrc emergency reparenting

    To use the vtctldclient SetVtorcEmergencyReparent command with --keyspace, optionally --shard, and --enabled=true or --enabled=false

    #### <a id="vtorc-dynamic-ers-disabled"/>Dynamic control of `EmergencyReparentShard`-based recoveries</a>
    **Note: disabling `EmergencyReparentShard`-based recoveries introduces availability risks; please use with extreme caution! If you rely on this functionality often, for example in automation, this may be signs of an anti-pattern. If so, please open an issue to discuss supporting your use case natively in VTOrc.**
    The new `vtctldclient` RPC `SetVtorcEmergencyReparent` was introduced ([PR #17985](https://github.com/vitessio/vitess/pull/17985)) to allow VTOrc recoveries involving `EmergencyReparentShard` actions to be disabled on a per-keyspace and/or per-shard basis. Previous to this version, disabling EmergencyReparentShard-based recoveries was only possible globally/per-VTOrc-instance. VTOrc will now consider this keyspace/shard-level setting that is refreshed from the topo on each recovery. The disabled state is determined by first checking if the keyspace, and then the shard state. Removing a keyspace-level override does not remove per-shard overrides.
    **Example**:
    ```bash
    # Disable ERS recoveries for a keyspace
    vtctldclient SetVtorcEmergencyReparent --keyspace commerce --enabled=false
    # Disable ERS recoveries for a specific shard
    vtctldclient SetVtorcEmergencyReparent --keyspace commerce --shard 80- --enabled=false
    # Re-enable ERS recoveries
    vtctldclient SetVtorcEmergencyReparent --keyspace commerce --enabled=true
    ```
     * `vtorc`: add support for dynamic enable/disable of ERS by keyspace/shard [#17985](https://github.com/vitessio/vitess/pull/17985)
    github.com/vitessio/vitess/releases/tag/v23.0.0
  • VTGate support for tuple bind variables in IN filters
     * [release-23.0] Fix handling of tuple bind variables in filtering operations. (#18736) [#18747](https://github.com/vitessio/vitess/pull/18747) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Resharding journal val column widened to longblob
     * VReplication: Fix some switch writes related issues and logging [#18608](https://github.com/vitessio/vitess/pull/18608)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Empty-password credentials accepted for unmanaged tablets
     * Allow empty passwords for unmanaged tablet configuration [#18448](https://github.com/vitessio/vitess/pull/18448)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Configurable tablet draining for the xtrabackup backup engine

    To use --xtrabackup-should-drain set to true

     * make xtrabackup ShouldDrainForBackup configurable [#18431](https://github.com/vitessio/vitess/pull/18431) 
    | `--xtrabackup-should-drain` | vttablet | Makes the ShouldDrainForBackup behavior configurable for xtrabackup engine. When true, tablet drains traffic before backup. Default: true. | [#18431](https://github.com/vitessio/vitess/pull/18431) |
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Parsed MySQL connection attributes retained for server use
     * support mysql protocol connection attributes [#18548](https://github.com/vitessio/vitess/pull/18548)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • MySQL client support for handshake connection attributes

    To use Use ConnectWithAttributes with a ConnectionAttributes map.

     * support mysql protocol connection attributes [#18548](https://github.com/vitessio/vitess/pull/18548)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Custom logger support for discovery

    To use WithLogger option

     * go/vt/discovery: configurable logger [#17846](https://github.com/vitessio/vitess/pull/17846)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VTTablet logs primary-serving binlog watcher closures
     * Add logging to binlog watcher actions [#18264](https://github.com/vitessio/vitess/pull/18264)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • gRPC servers now report ORCA backend metrics

    To use Enable --grpc-enable-orca-metrics (default: false).

     * Add support for sending grpc server backend metrics via ORCA [#18282](https://github.com/vitessio/vitess/pull/18282)
    | `--grpc-enable-orca-metrics` | vtgate, vttablet | Enable ORCA (Open Request Cost Aggregation) backend metrics reporting via gRPC for load balancing decisions. Default: false. | [#18282](https://github.com/vitessio/vitess/pull/18282) |
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Query logging gains an execution-time threshold

    To use A --querylog-time-threshold duration in time.ParseDuration format; it is not useful for streaming queries.

     * Add support for querylog-time-threshold duration flag for query logging [#18520](https://github.com/vitessio/vitess/pull/18520)
    | `--querylog-time-threshold` | vtgate, vttablet | Duration threshold for query logging. Queries exceeding this duration will be logged. Works with `--querylog-emit-on-any-condition-met`. | [#18520](https://github.com/vitessio/vitess/pull/18520) |
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Online DDL readiness-change logging
     * OnlineDDL: log changes to `ready_to_complete` [#18557](https://github.com/vitessio/vitess/pull/18557) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Example Vitess Operator CRD schema adds fetchCredentials
     * Add fetchCredentials to operator.yaml [#18460](https://github.com/vitessio/vitess/pull/18460) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Query planner optimization-reason debug logs

    To use DebugOperatorTree = true

     * Planner: Add comprehensive debug logging for query planner NoRewrite cases [#18476](https://github.com/vitessio/vitess/pull/18476)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • SQL parser support for SET NAMES binary
     * Fix sqlparser cannot parse 'set names binary' [#18582](https://github.com/vitessio/vitess/pull/18582) 
    | `SET NAMES binary` | Support for binary character set specification | [#18582](https://github.com/vitessio/vitess/pull/18582) |
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Incoming query throttling for tablets

    To use Throttler enabled flag in /config/throttler-config.json

     * [QueryThrottler] Implement Query Throttler [#18449](https://github.com/vitessio/vitess/pull/18449)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Query throttler dry-run mode
     * [Query Throttler] Add dry-run mode [#18657](https://github.com/vitessio/vitess/pull/18657) 
    - Dry-run mode for testing throttling without enforcement
    **Dry-run Mode**: Test throttling rules without actually blocking queries, useful for validating configuration before enforcement.
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • New TMC RPCs batch sequence handling in switchwrites
     * Add TMC RPCs for updating sequences for `switchwrites` [#18172](https://github.com/vitessio/vitess/pull/18172)
    - **Added** `GetMaxValueForSequences` and `UpdateSequenceTables` gRPC RPCs ([PR #18172](https://github.com/vitessio/vitess/pull/18172)) for VReplication sequence management during `SwitchWrites` operations.
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VStream table names without the keyspace

    To use Set the ExcludeKeyspaceFromTableName VStream flag

     * Add a flag to vstream to exclude keyspace from table name [#18274](https://github.com/vitessio/vitess/pull/18274)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • VStreamer uses schema for compatible DDL changes
     * [release-23.0] VReplication: Handle compatible DDL changes (#18739) [#18749](https://github.com/vitessio/vitess/pull/18749) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Session closing exposed through vtgateconn gRPC
    #### VTGate
     * vtgateconn minor enhancements [#18551](https://github.com/vitessio/vitess/pull/18551) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Configurable gRPC fail-fast for vtgate connections

    To use Set vtgate-grpc-fail-fast to true to enable gRPC fail-fast; it defaults to false.

    #### VTGate
     * vtgateconn minor enhancements [#18551](https://github.com/vitessio/vitess/pull/18551) 
    | `--vtgate-grpc-fail-fast` | vtgate | Enable gRPC fail-fast mode for faster error responses when backends are unavailable. Default: false. | [#18551](https://github.com/vitessio/vitess/pull/18551) |
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • vtgateconn gRPC flag registration exposed to external callers
    #### VTGate
     * vtgateconn minor enhancements [#18551](https://github.com/vitessio/vitess/pull/18551) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Single-call MySQL replication restart

    To use A client that calls the added RestartReplication method

     * `RestartReplication` RPC [#18628](https://github.com/vitessio/vitess/pull/18628)
    - **Added** `RestartReplication` method to `TabletManagerClient` interface ([PR #18628](https://github.com/vitessio/vitess/pull/18628)). This new RPC allows stopping and restarting MySQL replication with semi-sync configuration in a single call, providing a convenient alternative to separate `StopReplication` and `StartReplication` calls.
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • SchemaDiff adds a foreign-key impact listing
     * `schemadiff`: `RelatedForeignKeyTables()` [#18195](https://github.com/vitessio/vitess/pull/18195) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Per-shard completion for Online DDL migrations
    #### Online DDL
     * Feature(onlineddl): Add shard-specific completion to online ddl [#18331](https://github.com/vitessio/vitess/pull/18331) 
    #### <a id="online-ddl-shard-specific-completion"/>Online DDL Shard-Specific Completion</a>
    Online DDL migrations can now be completed on a per-shard basis using the new `COMPLETE VITESS_SHARDS` syntax ([PR #18331](https://github.com/vitessio/vitess/pull/18331)).
    **Usage**:
    ```sql
    -- Complete migration on specific shards only
    ALTER VITESS_MIGRATION '9e8a9249_3976_11ed_9442_0a43f95f28a3'
      COMPLETE VITESS_SHARDS '-80,80-';
    
    -- Complete migration on all remaining shards
    ALTER VITESS_MIGRATION '9e8a9249_3976_11ed_9442_0a43f95f28a3'
      COMPLETE;
    **Benefits**:
    - Gradual rollout of schema changes across shards
    - Ability to validate changes on subset of shards before full rollout
    - Better control over migration timing and impact
    ```
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • Selective table copying in VStream

    To use Set TablesToCopy in VStreamOptions or VStreamFlag

     * VStream: Add flag to support copying only specific tables [#18184](https://github.com/vitessio/vitess/pull/18184)
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • vstreamer emits PREVIOUS_GTIDS VEvents
     * GTID and other `go/mysql` and `vstreamer` optimizations [#18196](https://github.com/vitessio/vitess/pull/18196) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • GTID metadata added to vstreamer events
     * GTID and other `go/mysql` and `vstreamer` optimizations [#18196](https://github.com/vitessio/vitess/pull/18196) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • operator.yaml schema support for mysqldExporter.extraFlags

    To use mysqldExporter.extraFlags in operator.yaml, defined as an object with string-valued additional properties

     * Update `operator.yaml` [#18364](https://github.com/vitessio/vitess/pull/18364) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md
  • mysqldExporter no longer requires resources
     * Update `operator.yaml` [#18364](https://github.com/vitessio/vitess/pull/18364) 
    github.com/vitessio/vitess/blob/main/changelog/23.0/23.0.0/changelog.md

Dependency updates17

    17 more, none mentioning security
    • * Build mysql80 Dockerfile with go1.25.1 [#18694](https://github.com/vitessio/vitess/pull/18694)
    • * [main] Upgrade the Golang version to `go1.24.2` [#18093](https://github.com/vitessio/vitess/pull/18093)
    • * [main] Upgrade the Golang version to `go1.24.3` [#18241](https://github.com/vitessio/vitess/pull/18241)
    • * [main] Upgrade the Golang version to `go1.24.4` [#18327](https://github.com/vitessio/vitess/pull/18327)
    • * [main] Upgrade the Golang version to `go1.25.0` [#18573](https://github.com/vitessio/vitess/pull/18573)
    • * [main] Upgrade the Golang version to `go1.25.1` [#18622](https://github.com/vitessio/vitess/pull/18622)
    • * Bump subset of Go dependencies [#18577](https://github.com/vitessio/vitess/pull/18577)
    • * Upgrade the Golang Dependencies [#18082](https://github.com/vitessio/vitess/pull/18082)
    • * Bump golang.org/x/net from 0.37.0 to 0.38.0 [#18177](https://github.com/vitessio/vitess/pull/18177)
    • * Upgrade the Golang Dependencies [#18266](https://github.com/vitessio/vitess/pull/18266)
    • * Bump github.com/go-viper/mapstructure/v2 from 2.2.1 to 2.3.0 [#18404](https://github.com/vitessio/vitess/pull/18404)
    • * Main: Bump Go Dependencies [#18686](https://github.com/vitessio/vitess/pull/18686)
    • * Upgrade the Golang Dependencies [#18711](https://github.com/vitessio/vitess/pull/18711)
    • * Bump @babel/runtime from 7.26.0 to 7.27.6 in /web/vtadmin [#18467](https://github.com/vitessio/vitess/pull/18467)
    • * Bump form-data from 4.0.1 to 4.0.4 in /web/vtadmin [#18473](https://github.com/vitessio/vitess/pull/18473)
    • * Bump vite from 4.5.9 to 4.5.14 in /web/vtadmin [#18485](https://github.com/vitessio/vitess/pull/18485)
    • * Deprecate `github.com/mitchellh/mapstructure` library [#18687](https://github.com/vitessio/vitess/pull/18687)
    Other changes110

    Summaries are produced by AI, so they can be wrong, and they are provided without warranty.