Running count(*) is a bajillion times faster in the pgrust columnar layout than in…
This is a dev post classified by Jev as Databases (a tool drop), kept by the Dev Radar because it carries real work, not commentary.
Running count(*) is a bajillion times faster in the pgrust columnar layout than in Postgres count(*) in Postgres is frustratingly slow. Why doesn't it store the exact row count? Well column stores do exactly that. In pgrust's columnar format, the row count lives in the metadata, so count(*) is instantaneous
Posted by Michael Malis (997 followers) 2 days ago · 49 likes · 4.7k views · view the original post on X. Kept by the Dev Radar as Databases.
More dev work like this
- Construct a bitemporal knowledge graph with Utopia that evolves as material arrives and… — @tom_doerr
- We’re bringing Databricks Unity Gateway to developers on Neon (@neondatabase), and it’s… — @Yuchenj_UW
- Docs changes shouldn’t need a mystery deployment process. — @DanKornas
- Our new short course with @DeepLearningAI covers continual and adaptive learning: the… — @OracleDevs
- The workshop you were looking for: 2 hours, virtual, and for free. — @neo4j
- Warehouse data shouldn’t wait for someone to ask the right question. — @DanKornas
- Context. That's the difference between an AI demo and a reliable production agent. The… — @Redisinc
- When #DuckDB-Wasm was launched in 2021, databases could not be persisted: everything… — @duckdb
Every post is read and classified by Jev (TypeSafe): what it is, which market it belongs to, and whether the link is a real tool. 12.2k posts from 4.7k X accounts over the last 21 days, 1.4k tools, 12 markets. Collected every 5 minutes, fully re-ranked every hour — last update 2026-09-19 18:06 UTC. Full method.