CommSync Runs Text, Vector, and Hybrid Search on Postgres with Lakebase Search

T1Covered by 1 source · first reported by Databricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale at 30 Jul, 12:00 UTC

"We're running lakebase_text and lakebase_vector across three different parts of our product. Query latency improved 1,000x and we don't need a separate search stack sitting next to our Postgres."

Sources

• T1CommSync Runs Text, Vector, and Hybrid Search on Postgres with Lakebase SearchDatabricks / ClickHouse / DuckDB / Supabase / Neon / PlanetScale30 Jul, 12:00