FAQs on Vchord

General FAQ

Mon, 01 Jan 0001 00:00:00 +0000

Warning

We strongly suggest you explore our new VectorChord implementation, offering enhanced stability and performance. Users are advised to transition to VectorChord. Refer to the migration guide for assistance.

The vector type or operator class is not found

In most cases, this is due to a missing schema search path or a lack of permissions.

Please go through this checklist:

Run \dx with psql or SELECT * FROM pg_extension; and check if the extension exists.

postgres=# \dx
                                                    List of installed extensions
  Name   |    Version    |   Schema   |                                         Description                                          
---------+---------------+------------+----------------------------------------------------------------------------------------------
 vectors | 0.3.0         | vectors    | vectors: Vector database plugin for Postgres, written in Rust, specifically designed for LLM

If not, install it with CREATE EXTENSION vectors;

Comparison with pgvector

Mon, 01 Jan 0001 00:00:00 +0000

Original post: pgvector vs. pgvecto.rs in 2024: A Comprehensive Comparison for Vector Search in PostgreSQL

TL; DR: Please navigate directly to the final section that contains a table showcasing the main distinctions.

Search

Search is essential for a database. It plays a pivotal role in facilitating efficient data retrieval, enabling users to quickly find and access the information they need. We will demonstrate their performance and highlight the various features pgvecto.rs and pgvector offer.

Why not a specialty vector database?

Mon, 01 Jan 0001 00:00:00 +0000

Read our complete blog at Do we really need a specialized vector database? (2023) | vchord.pgsty.com.

Imagine this, your existing data is stored in a Postgres database, and you want to use a vector database to do some vector similarity search. You have to move your data from Postgres to the vector database, and you have to maintain two databases at the same time. This is not a good idea.

Why not just use Postgres to do the vector similarity search? This is the reason why we build pgvecto.rs. The user journey is like this:

Benchmarks

Mon, 01 Jan 0001 00:00:00 +0000

pgvecto.rs has been focused on performance from the beginning. We have continuously monitored the performance of pgvecto.rs and compared it with other vector search libraries. The following benchmark results are from January 2024.

The test is done on Google Cloud n2-standard-8 (8 vCPUs, 32 GB RAM) with the laion-768-5m-ip dataset.

`pgvecto.rs` v.s. `pgvector`

With the HNSW index, pgvecto.rs can achieve 2.5x responses per second as pgvector can do with a slightly better precision of around 97%. This advantage increases when higher precision is required.

FAQs on Vchord

General FAQ

The vector type or operator class is not found

Comparison with pgvector

Search

Why not a specialty vector database?

Benchmarks

pgvecto.rs v.s. pgvector

`pgvecto.rs` v.s. `pgvector`