AffectedPagesFinder should ignore stale usage entries. To that end, SqlUsageTracker needs to join the usage entries against the page table and compare page_touched to eu_touched.
|· · ·|
|Resolved||daniel||T96373 Usage tracking update / purging on edit and re-parse (tracking)|
|Invalid||daniel||T99509 [Task] Ignore stale usage entries when processing changes|
|· · ·|
This may not be necessary. If we prune stale usage info not only on ArticleEditUpdates, but also on LinksUpdate, we should not have stale usage tracking entries in the database for long. So it would not be necessary to filter them out when looking up usages.
Given pruning on LinksUpdate, filtering stale entries on lookup would be purely defensive. I'm not sure that is worth the additional cost of joining against the page table.