latent.fs / posts / db — 7 items

/feed.xml

CATEGORY

DB

2026-10 2 posts

  1. What Happens to HNSW Recall After Adding Vectors? (1M+1M)

    A 1M+1M insertion study in pgvector and Qdrant, comparing insertion order, batch boundaries, and fresh indexes. Segment telemetry and version-pinned code help explain their different behavior.

    DB

  2. What Happens to HNSW Recall After Adding Vectors? (10K+10K)

    A small pgvector and Qdrant experiment compares recall before and after vector insertion, then against fresh indexes over the same final data.

    DB

2026-05 5 posts

  1. PostgreSQL Lakehouse (2/2) — Distributed Processing and Citus Integration

    Distributed processing (Ray/Daft/Smallpond) and Citus + pg_lake FDW integration

    DB #24

  2. PostgreSQL Lakehouse (1/2) — When DuckLake Hit a Wall, pg_lake Was There

    Eight phases building a PostgreSQL-centered Lakehouse: DuckLake's libpq collision and pg_lake

    DB #23

  3. PG-Strom SSB Benchmark — Arrow FDW Comes Before GPU

    555 test cases on three servers: on heap storage PG-Strom's GPU gave 1.6x and lost to CPU on wide tables; with Arrow FDW it hit 10x at SF=100.

    DB #22

  4. Should Databases Handle AI Too?

    Oracle 23ai, EDB AIDB, PostgresML, Timescale pgai, pg_aidb — five systems and the abstraction-boundary discussion

    DB #9

  5. Replacing Elasticsearch with PostgreSQL

    Korean hybrid search on PostgreSQL alone (MeCab, BM25, pgvector, in-DB RRF) over eight phases: Elasticsearch-level quality, 2–5x faster on one node.

    DB #7

TAGS 190

All 190 tags →