Skip to content

ADD-backfill can produce phantom index entries (F-192, split from #1946) #2099

Open

Description

@kriszyp

Summary

Adding an indexed attribute triggers a backfill of the new index over existing records, and that backfill has been observed producing phantom index entries — index entries that don't correspond to a live record.

Split out of #1946, which was filed as a single dispatch finding covering two separate defects. #1946 keeps the drop_attribute half (F-193); this issue is F-192.

What is established

  • The finding reproduced under a measured 4-way worker spread (dispatch task qa-wave-2026072509), not an assumed one — the same run that re-confirmed drop_attribute never reclaims Table.indices #1946.
  • It is one of the two findings underpinning P-472's RED anchor.

What is not established

Being explicit, because the original finding was a one-line dispatch note and the underlying QA evidence wasn't captured anywhere I can find:

  • The exact shape of the phantom entries — stale values, entries for records that were concurrently written, or entries for records that never existed.
  • Whether they are reachable by a query (a phantom index entry that returns a row is a correctness bug; one that is skipped on lookup is a space leak).
  • Whether the multi-worker precondition is causal or incidental. The backfill racing concurrent writes across workers is the obvious hypothesis, but it is a hypothesis.
  • Whether it survives a restart, and whether a reindex clears it.

Suggested next step

Reproduce with the 4-way worker spread from the original run, then answer the reachability question first — it decides whether this is a correctness issue or a hygiene one, and therefore what priority it should carry. The current P2 assumes hygiene; if a phantom entry can be returned from a query, it should be re-tiered.

Related


Filed during backlog triage to split #1946's two findings. No new investigation: everything above the "next step" section comes from the original dispatch note.

Activity

  1. added this to the v5.2 milestone on Aug 6, 2026
  2. added theissue type on Aug 6, 2026
  3. modified the milestones: v5.2, v5.4 on Oct 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    Fields

    Priority

    P2

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions