Remove pgrust: the entry is cheating (per-query kernels and result caching)

First reported · 22h ago · 1 source

Crest summary — written by AI from the 1 source below; every figure is checked against them · model deepseek-flash

Summary

A Hacker News submission titled "Remove pgrust: the entry is cheating" calls for removing pgrust from a comparison, alleging it uses per-query kernels and result caching.

Key facts

  • The submission appeared on Hacker News on 2026-10-23.
  • The title accuses pgrust of cheating through per-query kernels and result caching.

Why it matters

Anyone comparing database performance should check whether a benchmark entry relies on per-query kernels or cached results, since those can make results incomparable.

Technologies

  • pgrustproduct

Matched by rule, not by AI: a repository linked in the coverage, or a technology or company in this event that Crest tracks.

Repositories

Original sources (1)

The report this event was built from. Crest of Tech keeps no article bodies: the full text is at each source.

  1. Hacker NewsCommunity · Primary
    Remove pgrust: the entry is cheating (per-query kernels and result caching) · By f311a
    Read at Hacker News
Remove pgrust: the entry is cheating (per-query kernels and result caching) — Crest of Tech