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
阅读原始来源来源记录
指标快照
points · 2 votes
2026-11-16 04:57:56.390Z
cumulative since publication
研究分析
项目记录
仓库:janbjorge/straum。 来源描述: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
采用记录与比较对象
来源票数: 2 votes (2026年11月16日 UTC; cumulative since publication);前次同口径记录为 2(2026年11月15日 UTC),两个观测值不等于需求增长。
采用判断
应与它要替代的工具或人工流程比较。现有记录支持发现项目,尚不能确认可靠性、运行成本优势或商业采用。
尚未核验的门槛
尚未核验:许可证权限、硬件要求、安装步骤、维护状态,以及包含失败样例的代表性任务。
下一步试验
选择一个真实任务和现有替代方案,记录 commit、环境、输入、输出、耗时与失败行为;保留结果后再给出采用建议。