Show HN: Straum – PostgreSQL Group by in Microseconds
I've seen too many slow-log queries with a GROUP BY that makes Postgres blow up, so for the last two weeks or so I've been working on Straum. You declare the aggregates as a view, and Straum answers over HTTP (other transports might be added). I've been using the New York taxi dataset as a benchmark. On the heavier GROUP BYs I see about 1,000x to 5,000x. It's written in Rust (of course). It leans on Postgres replication slots, logical or physical, to get its data. Postgres stays the source of tr
Read original sourceSource record
Recorded metrics
points · 2 votes
2026-11-16 04:57:56.390Z
cumulative since publication
Research analysis
Project record
Repository: janbjorge/straum. Source account: I've seen too many slow-log queries with a GROUP BY that makes Postgres blow up, so for the last two weeks or so I've been working on Straum. You declare the aggregates as a view, and Straum answers over HTTP (other transports might be added). I've been using the New York taxi dataset as a benchmark. On the heavier GROUP BYs I see about 1,000x to 5,000x. It's written in Rust (of course). It leans on Postgres replication slots, logical or physical, to get its data. Postgres stays the source of tr
Observed adoption & comparisons
Source votes: 2 votes (Nov 16, 2026 UTC; cumulative since publication); previous same-scope observation: 2 (Nov 15, 2026 UTC). These observations do not establish demand growth.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.