# Top SQL Other aggregate product knowledge

<!-- auto-oncall-optimization-record
{
  "schemaVersion": "auto-oncall-optimization-record-v1",
  "optimizationId": "top-sql-other-aggregation-2026-09-07",
  "problems": [
    {
      "problemId": "top-sql-other-mistaken-for-single-query",
      "summary": "The Other long-tail query aggregate was treated as one unidentified workload whose SQL identity could be retrieved.",
      "status": "candidate",
      "applicability": "TiDB Dashboard Top SQL Other/Others/Other Statements buckets and explicitly equivalent query-tail summaries.",
      "issueKeys": ["APID-29464"],
      "sourceRefs": ["https://tidb.atlassian.net/browse/APID-29464#problem:top-sql-other-mistaken-for-single-query"],
      "signalTextIncludesAny": ["Other", "4229", "42,288,762"],
      "observedThrough": "2026-09-07",
      "effectiveAt": null,
      "verifiedAt": null,
      "attemptedAction": "Add one searchable product-knowledge topic defining Other as the combined long-tail query aggregate, retaining valid aggregate interpretation and distinguishing it from a single query identity.",
      "evidenceUrl": "https://tidb.atlassian.net/browse/APID-29464?focusedCommentId=23812455"
    }
  ]
}
-->

- Owner: AOS product knowledge; source: explicit operator correction on
  2026-09-07 and the official Top SQL documentation linked in the topic.
- Base SHA: `59ab3bf045056c38cf17b4b37a499e9cd79fa5a7` from fetched `origin/main`.
- Implementation status: topic, searchable index entry, and existing topic
  inventory updated in an isolated worktree.
- Effective status: candidate; deployment and case replay are not verified.

## Bounded problem

APID-29464 feedback `23812455` belongs to run DB id `150204`, run
`00d26683-f22e-4dfe-bb3c-cc18af97714d`, answer fingerprint
`e631c00129aa968661527f57fc29a59a6143130e3d95ff6892635cc7a778d6a0`.
The historical diagnosis used 42,288,762 executions as evidence of an
unidentified high-volume workload and requested its SQL identity. The operator
clarified that Other represents the combined long tail, not one query awaiting
identification. The knowledge preserves the aggregate's useful meaning rather
than declaring all aggregate evidence unusable.

This record covers that product fact only. Unmatched lock-wait samples,
Provider readiness failures, and CPU root-cause selection remain separate
questions; this change does not claim to resolve them.

## Verification and next action

Official current and v7.5 Top SQL documentation confirm the aggregation
meaning. TypeScript build and all 1099 tests passed after updating both
existing topic inventories. A focused check also passed new-topic recall,
unrelated-label exclusion, and selected-topic materialization. These checks
do not establish a changed model answer.

After deployment, verify on APID-29464 that the selected knowledge reaches its
semantic owner and Other is described as the combined tail, with no attempt
to resolve a single SQL identity for the bucket. Preserve valid individual
query interpretation and aggregate totals. A case-specific replay and the
applicable internal-comment refresh are still required before marking this
problem optimized_verified.