MySQL 26.7 Innovation Support Lands
September 22, 2026 · GitHub Release
MySQL just changed the rules.
With MySQL 26.7, Oracle has moved to a new calendar-based versioning model for Innovation releases. For MyVector, that means one thing:
We need to keep up.
MyVector v1.26.9 adds MySQL 26.7 Innovation support, but the more interesting story is what happened beneath the surface.
This release puts the Component architecture introduced in v1.26.5 through a much more serious test.
From architecture to reliability
When we introduced the MySQL Component architecture in v1.26.5, the goal was straightforward: build MyVector in the direction MySQL itself is taking.
Now we are testing what happens when things don’t go perfectly.
v1.26.9 adds proper Component lifecycle testing, including installation, uninstallation, failed removal, and deinitialization rollback.
Because installing something is easy.
Installing, removing, failing, restarting, and recovering correctly is the real test.
HNSW gets harder to kill
There is also some important HNSW work in this release.
A number of failure paths around HNSW index creation and persistence have been fixed, including a case where an index build could crash mysqld.
That obviously isn’t acceptable.
We also fixed configuration handling so type=hnsw is correctly honored, and persistence failures are now surfaced instead of disappearing silently.
If MyVector cannot save an index, you should know about it.
Does it survive a restart?
This became an explicit test in v1.26.9.
It is one thing to create an index and run a vector search.
It is another thing to restart MySQL and have that index come back.
The new lifecycle tests verify that persisted indexes are actually reloaded from disk.
That is an important distinction as MyVector moves from an interesting MySQL extension toward something people can consider for real workloads.
The release process got better too
v1.26.9 also expands the testing and release pipeline around:
- MySQL 26.7 compatibility
- Component lifecycle
- HNSW
- Persistent indexes
- Online updates
- Stress testing
- Stanford dataset smoke tests
- Benchmark failure detection
- Docker builds
What’s next?
The original MyVector idea hasn’t changed:
Why move your data to another database just because your application needs vector search?
The answer is becoming more interesting as MySQL evolves.
With MyVector, the goal is to bring:
SQL + transactional data + vector search + full-text search + AI workloads
into the same database environment.
MySQL 26.7 brings a new Innovation release.
MyVector 1.26.9 makes sure we’re ready to follow it.
v1.26.5 was about introducing the Component architecture.
v1.26.9 is about proving it.
Get MyVector
MyVector is open source. Feedback, issues, benchmarks, and contributions are welcome.
