Loading…
Topic
pgvector
7 posts about pgvector. Every summary links to the original.
- 7 posts
- 3 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
Managed Postgres: What Lakebase Actually Takes Off Your Plate
Managed Postgres varies from OS patching alone to operating scaling, failover, backups, recovery, and related database tooling. Lakebase Postgres applies this model to serverless infrastructure, offering automatic scaling, scale-to-zero, PostgreSQL compatibility, automatic snapshots, point-in-time recovery, branching, built-in PgBouncer, and support for extensions including pgvector and PostGIS. Within a region, patching, scaling, failover, and backups run automatically, while encryption, access control, audit visibility, connection pooling, and lakehouse integrations are also addressed. The discussion also stresses checking PostgreSQL versions, configuration, extensions, and migration methods before moving an existing database. Cross-region disaster recovery remains the main exception: it is in Private Preview for AWS, with periodic replication, manual failover, and customer-managed recovery procedures.
Three principles for building a vector platform at Thumbtack
Thumbtack describes a vector platform that lets ML engineers stand up production vector search without separately negotiating database access, building ETL, or writing a query service. The design uses an existing Aurora Postgres cluster with pgvector, while Airflow jobs generate embeddings into BigQuery and managed reverse-ETL syncs them into vector tables; a query API validates inputs and returns ranked results. Three principles guide the layers: reuse trusted infrastructure, treat embeddings as ordinary data flowing through established pipelines, and lower adoption costs for subsequent teams. Production examples include semantic customer-support escalation using cosine similarity and an internal knowledge assistant combining vector retrieval, often with keyword search, before a language model responds; planned directions include self-serve provisioning, vector-backed feature retrieval, and framework-neutral agent memory.
How leading tech companies are killing the builder's tax with Lakebase
The post argues that AI-native applications face a “builder’s tax” because operational databases and lakehouse analytics are separated by CDC, ETL/ELT, and reverse ETL pipelines. This architecture can leave AI systems with stale data while duplicating governance and shifting engineering effort toward orchestration and failure management. It presents Lakebase, a fully managed serverless Postgres engine integrated with the Databricks Data + AI Platform, as a shared operational foundation where applications, agents, analytics, and governance use the same data. The proposed pattern combines a lakehouse intelligence layer, a low-latency Lakebase execution layer, and a continuous learning loop, with pgvector supporting agent memory and semantic search. Reported customer examples include faster feature onboarding, reduced on-call disruption, higher agent throughput, and consolidated data estates, though the results vary by organization.
What is pgvector?
pgvector is an open-source PostgreSQL extension that adds vector storage, indexing, and similarity search for embeddings alongside relational application data. It supports semantic search, recommendations, retrieval-augmented generation (RAG), image similarity, anomaly detection, and deduplication without requiring a separate vector database for many workloads. The extension uses the vector data type and distance metrics including L2, cosine similarity, and inner product, with HNSW and IVFFlat indexes offering different speed and memory trade-offs. Vector queries can also combine relational filters with Postgres full-text search for hybrid retrieval. pgvector is positioned as a practical choice for existing Postgres deployments, while pgvectorscale can extend its usefulness as data and query demands grow; dedicated vector databases become more relevant at larger scales, and Databricks AI Search serves complementary lakehouse workloads.
Building AI Search on Heroku
The reference architecture addresses a common RAG failure: vector search can return semantically similar documentation that does not answer the user's question. Its query pipeline retrieves the top 20 chunks with cosine similarity in Heroku Postgres and pgvector, then sends those candidates to Cohere Rerank 3.5, a cross-encoder reranker, before Claude 3.5 Sonnet generates an answer. The indexing pipeline crawls URLs, filters likely boilerplate, splits documents into 1,000-character chunks with 200-character overlap at natural boundaries, embeds them with Cohere Embed Multilingual, and batch-inserts them. Server-Sent Events stream embedding, search, reranking, sources, and generated text to avoid a blank screen during the multi-step request. The reranking stage can be made optional when lower latency matters more than precision.
Building Data-Aware AI Applications with Heroku AI and LlamaIndex
Organizations building AI applications over private data must connect large language models with proprietary datasets without managing every infrastructure component. The post presents Heroku Managed Inference and Agents with LlamaIndex as a stack for retrieval-augmented generation (RAG), combining LlamaHub connectors, indexing, retrieval, and managed model services. The implementation provisions Heroku Postgres with pgvector, Claude 4 Sonnet for inference, and Cohere Embed Multilingual embeddings, then uses Python and LlamaIndex to load documents, store 1,024-dimensional vectors, and query them through an OpenAI-compatible embedding endpoint. PGVectorStore supplies the vector store, while Heroku environment variables provide service credentials and connection details. The result is a deployable pattern for querying private documents, with examples spanning financial analysis, insurance claims, customer support, and internal knowledge.
How to Use pgvector for Similarity Search on Heroku Postgres
Heroku Postgres now supports pgvector on all Standard-tier or higher databases running Postgres 15, adding vector storage and functions for similarity search and machine-learning applications. Older Postgres versions require an upgrade to Postgres 15. The workflow generates embeddings, adds a VECTOR(100) column, and stores values using SQL or Python with psycopg, pgvector-python, and Wikipedia2Vec’s pretrained 100-dimensional model. Queries can rank vectors with Euclidean, cosine, or inner-product distance; the example uses <-> to return five animals nearest to shark, producing crocodile, dolphin, whale, turtle, and alligator. Results depend on the embedding model and corpus, while indexes introduce approximate nearest-neighbor search; pgvector supports IVFFlat and HNSW, with IVFFlat requiring table data for better recall.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.