[Positioning] VECTOR_DISTANCE() for self-managed MySQL, Tech Preview (8.4.11 / 9.7.2 est.)

[brianamarie]

What needs positioning

• Market gap: Vector distance in MySQL today is available on Oracle-managed offerings (HeatWave, MySQL AI), not on self-managed MySQL estates teams install and run themselves.
• Tech Preview (8.4.11 / 9.7.2 est.): VECTOR_DISTANCE() on Percona Server for MySQL, early preview builds for evaluation.
• Later (MVP): Full MySQL Vector Support (search, indexing, broader product scope).
• Percona role: We are building native distance capability for self-managed PS customers. This is not shipping upstream/community MySQL vector and not repackaging what Oracle already ships on managed paths.

---

What is shipping and when

Phase	Scope	Release (est.)
Tech Preview	VECTOR_DISTANCE() only	8.4.11 / 9.7.2 (est.)
GA (MVP)	Full MySQL Vector Support (indexing, ANN/search workflows, broader scope)	TBD

• Product: Percona Server for MySQL (self-managed builds).
• Release note: moved from the earlier "August" framing to versions 8.4.11 / 9.7.2 (Vector Distance was sequenced after the PGO releases). Prefer referencing versions over hard dates, since timing can shift.
• PXC: VECTOR_DISTANCE() is confirmed compatible with Percona XtraDB Cluster. It is a non-deterministic function (approximate vector results plus SIMD floating-point variation), but that is not a replication concern because results can already differ between calls on the same node. It ships in PXC at the same version as Percona Server (PXC engineering).
• Tech Preview means: Early-access builds for evaluation and feedback, not production GA; support and comms terms TBD.

---

Why it matters

Tech Preview inclusion (8.4.11 / 9.7.2)

• Lets self-managed PS teams work with vector distance in SQL without HeatWave or MySQL AI.
• First concrete step on Percona's MySQL vector roadmap on estates customers already run.
• Product to confirm: exact customer-visible outcome for the Tech Preview (workloads enabled, limits, install path).

Full search for the future (later, do not fold into Tech Preview copy)

• Single-system path vs MySQL + separate vector DB ("Two-System Problem").
• Indexing, ANN search, and broader MySQL Vector Support scope (per v0.5 prototype / PRD).
• Stronger TCO / consolidation story lands here, not at distance-only Tech Preview.

---

Target audience

Tech Preview

1. Early adopters / platform engineers on self-managed PS evaluating AI/RAG pipelines before full search ships.
2. Teams blocked from Oracle managed vector paths (HeatWave / MySQL AI) who need distance-in-SQL on PS they control.

MVP (later)

• Existing Percona Server for MySQL customers planning production RAG on PS.
• Architects comparing single-DB vs two-system (MySQL + standalone vector DB) designs.

---

Pillar alignment

Phase	Primary	Supporting
Tech Preview	Future readiness (AI on self-managed MySQL)	Credibility / roadmap signal for self-managed estates
MVP	Future readiness	Performance and reliability, Optimized TCO (consolidation)

Intended to align with pillar work and sit alongside PostgreSQL pgvector and Mongo vector narratives, not a unified "Percona AI DB" launch.

---

Deliverables (this issue)

• Pre-GA copy in products/mysql/ (Tech Preview = distance function; MVP = separate subsection)
• Short FAQ: what the Tech Preview includes / excludes
• Pillar hooks for Future readiness (Tech Preview vs MVP clearly labeled)

Out of scope for this issue:

• HeatWave / MySQL AI battle card
• pgvector comparison page
• Full vector search launch kit, TCO calculator, field battlecard (MVP)

---

Related positioning issues

• GH #199 PS PGO (separate release; Performance pillar)
• GH #188 Mongo vector (separate engine; later GA window)

[brianamarie]

@thefactremains Thanks for the chat clarification. Updated notes below. Please confirm, correct, or fill gaps.

My understanding:

• ~Aug 2026: VECTOR_DISTANCE() Tech Preview on self-managed Percona Server for MySQL (PS first; PXC TBD). Narrow scope: distance-in-SQL without HeatWave or MySQL AI. Small first step, not full vector search. Not GA until Milestone Log + Jira fix_versions.
• Later (MVP): Full MySQL Vector Support (indexing, ANN/search, consolidation story). GA date TBD.
• Issue body table: Aug row should read Tech Preview, not GA (correcting in issue description).

What I still need:

• PS release/version for full search GA (version/build)?
• PXC: in or out for first ship?
• Full vector search: target window, and any beta/TP before GA?
• Comms: Is August release notes / light roadmap comms only, with press and launch kit at full vector search GA? (That is my assumption from [Positioning] VECTOR_DISTANCE() for self-managed MySQL, Tech Preview (8.4.11 / 9.7.2 est.) #202 scope; want product/GTM alignment.)

[thefactremains]

Hi @brianamarie answers below. Thank you!

1. It is better to use the version (9.7.2) not august/hard dates as these can shift.
2. On whether PXC is going to ship Vector Distance function along with PS - answer will come in a few days. I need time to confirm.
3. On full vector GA (or even MVP) target window, I would prefer not to publish any dates as there are many unknowns. There will be an early access program of some kind and we are actively seeking design partners to discuss early decisions with.
4. Correct

[thefactremains]

Follow-up on item 2 (PXC): confirmed, PXC is in. VECTOR_DISTANCE() works in Percona XtraDB Cluster and is not a replication concern.

Detail: the function is non-deterministic by design (approximate vector-index results, plus SIMD floating-point variation across hardware and compiler optimization), so it can already return slightly different values between calls on the same node. Cross-node differences in a cluster are therefore equally acceptable, and the function does not change replication behavior. PXC eng team has confirmed no blocker.

Suggest updating the issue wording from "PXC in or out TBD" to PXC included, with the exact PXC version to confirm alongside the PS 9.7.2 target.