column store
Database architecture storing data by column rather than by row; enables efficient compression and analytical queries that access subsets of columns, typically 10x+ faster than row stores for analytics
As defined in Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
Where it comes up · 1
Most important claims · 4 of 4Search all claims for “column store” →
- One-size-fits-all database systems are fundamentally suboptimal because specialized systems like column stores (Vertica), stream processors (StreamBase), and vector databases (Pinecone) achieve order-of-magnitude performance gains by architecting for specific workload patterns.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- In 2004, Stonebraker was working on an academic project that became StreamBase (a stream processing engine) and had ideas for column stores for data warehouses (popularized by Vertica), which were wildly different implementations that bore no resemblance to row stores.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- PostgreSQL is optimal for low-end use cases (small databases, modest workloads) but not competitive for large data warehouses because it lacks column store capabilities and multi-node support, which are table stakes for scaling to terabyte-scale data.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
- Clickhouse is a column store, and Pinecone is faster than user-defined types on text-based vector processing, demonstrating that specialization in database architecture continues to be true today as it was in 2004.Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker