JCJunyu Cheninblog.vectorchord.ai·Feb 14 · 5 min readVectorChord 1.1: Native 4/8 Bit Vector Types and Per-Index Query DefaultsWe’re excited to announce the release of VectorChord 1.1 as we kick off the new year of horse. VectorChord 1.0 was a milestone for Postgres-native vector search: it made large-scale indexing fast enough to feel like iteration, not an outage. In 1.1, ...00
JCJunyu Cheninblog.vectorchord.ai·Jan 15 · 6 min readScaling Vector Search to 1 Billion on PostgreSQLFor teams trying to run vector search at billion scale themselves, the challenge is often not raw performance, but practicality. Many solutions designed for billion-scale, low-latency vector search come with practical constraints, requiring tradeoffs...00
JCJunyu Cheninblog.vectorchord.ai·Dec 3, 2025 · 13 min readHow We Made 100M Vector Indexing in 20 Minutes Possible on PostgreSQL1. Introduction In the past few months, we’ve heard consistent feedback from users and partners: while our goal of providing a scalable, high-performance alternative to pgvector is well-received, index build time and memory usage remain major concern...00
JCJunyu Cheninblog.vectorchord.ai·May 30, 2025 · 8 min readVectorChord: Cost-Efficient Upload & Search of 400 Million Vectors on AWSIn this article, we will describe one method for uploading, indexing, and searching a big dataset of vector data in a cost-efficient manner using the real-world LAION-400M dataset and the VectorChord extension in PostgreSQL. We're attempting to show ...00
JCJunyu Cheninblog.vectorchord.ai·Apr 3, 2025 · 11 min readVector Search Over PostgreSQL: A Comparative Analysis of Memory and Disk SolutionsIntroduction: real-world challenges Specialized vector databases aren’t always needed. With PostgreSQL extensions like pgvector, pgvectorscale, VectorChord (which evolved from pgvecto.rs), you get vector search plus relational power—no extra infras...00
