An Index Scan Is Only Half the Story
Comments on “An Index Scan Is Only Half the Story”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
In a Microsoft Tech Community post, Microsoft's Azure PostgreSQL team describes a migrated query that was slow only after cache eviction, despite using the same index.
Why it ranked
No. 24 of 62 with a score of 0.61. The panel rated it highest on new information (0.89) and technical depth (0.86), lowest on audience breadth (0.45). Placed No. 24, No. 32 by score alone: the fourth Data story of the day (−0.020). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Practical, well-evidenced PostgreSQL migration debugging write-up with specific diagnostics (ctid page counts, correlation, pg_repack). Narrow audience of database engineers; moderate significance and no new-stories overlap.
- AI judgeJudge 3gpt-5.6-luna
- A well-supported PostgreSQL performance investigation with concrete measurements, diagnostic SQL, physical-layout explanation, and operational remediation. It is highly actionable for database and infrastructure practitioners, though its audience is narrower than general tech.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.61total under rubric v2.3
- Significance0.46
- Reader interest0.69
- Audience breadth0.45
- Practical relevance0.77
- Substantiated0.80
- Technical depth0.86
- New information0.89
- Counts against: Promotional0.11
- Counts against: Overclaim0.15
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.51 | 0.30 | 0.58 | 0.46 | 0.28 | +0.24 | +0.111 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.66 | 0.60 | 0.82 | 0.69 | 0.22 | +0.26 | +0.180 |
| Audience breadthHow many people who build technology does it concern? | 0.52 | 0.40 | 0.42 | 0.45 | 0.12 | +0.13 | +0.058 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.78 | 0.70 | 0.83 | 0.77 | 0.13 | +0.22 | +0.169 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.90 | 0.60 | 0.90 | 0.80 | 0.30 | +0.05 | +0.040 |
| Technical depthHow technically substantive is it? | 0.99 | 0.80 | 0.78 | 0.86 | 0.21 | +0.05 | +0.043 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.84 | 0.90 | 0.93 | 0.89 | 0.09 | +0.05 | +0.045 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.06 | 0.25 | 0.03 | 0.11 | 0.22 | −0.19 | −0.022 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.13 | 0.25 | 0.06 | 0.15 | 0.19 | −0.11 | −0.016 |
| Sum of contributions | +0.608 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.608 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-15/24/"><img src="https://rubric.hrih.si/badge/2026-11-15/24.svg" alt="Ranked #24 on Rubric, 15 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 8 no source given. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
A query that completed in tens of milliseconds on the customer's on-premises PostgreSQL took 1-2 seconds in the Azure environment being evaluated.
The article gives no link or citation for it.
The article says “a query that completed in tens of milliseconds would now take 1-2 seconds in the Azure environment being evaluated”
The source says No source to compare with.
No source givenNumber
The to-be-production server had 10-20% more IOPS consumption than the comparison server.
The article gives no link or citation for it.
The article says “the to-be-production server having 10-20% more IOPS consumption than a server they stood up for comparison purposes”
The source says No source to compare with.
No source givenNumber
A cold-cache single Index Scan pulled over 100 heap pages on the slower server versus 60 on the other server.
The article gives no link or citation for it.
The article says “A cold-cache query execution that performed a single Index Scan pulled over 100 pages from heap, whereas the other server only pulled 60 pages”
The source says No source to compare with.
No source givenNumber
The slower environment had a column correlation of about 0.037, while the faster environment had about 0.571.
The article gives no link or citation for it.
The article says “the slower environment had a correlation around 0.037, while the faster performance-test environment was around 0.571”
The source says No source to compare with.
No source givenNumber
For lookup B (200 rows), the slower environment's matching rows occupied 101 heap pages versus 5 in the faster environment, about 20 times as many.
The article gives no link or citation for it.
The article says “For lookup B, the slower environment’s matching rows occupied about 20 times as many heap pages”
The source says No source to compare with.
No source givenCausal conclusion
The customer's parallel data loading into Azure interleaved rows of different lookup values, scattering related rows across the heap, which explained the layout difference.
The article gives no link or citation for it.
The article says “the concurrent loading interleaved rows belonging to different lookup values”
The source says No source to compare with.
No source givenCausal conclusion
VACUUM FULL does not sort surviving rows by the lookup key, so it does not fix a layout problem of interleaved rows.
The article gives no link or citation for it.
The article says “it doesn’t sort the surviving rows by the lookup key”
The source says No source to compare with.
No source givenNumber
The customer used pg_repack with --order-by to reorganize the data and reported improved performance on a restored test instance.
The article gives no link or citation for it.
The article says “The customer used pg_repack with --order-by to reorganize the data and reported improved performance on a restored test instance”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 4 pts, not on front page
Recorded for context only, checked 15 Nov 2026, 20:46 UTC. It played no part in the ranking.