Home/Compare/pgvector vs VectorChord

Comparison

pgvector vs VectorChord

Verdict

Pick pgvector if pgvector is an extension for PostgreSQL that enables efficient vector similarity search using various distance metrics, including L2, inner product, cosine distance, and L1 distance; pick VectorChord if vectorChord is a vector database extension for PostgreSQL, offering scalable and efficient vector search capabilities. It supports vector indexing and retrieval, making it suitable for applications requiring fast and.

Markdown twin · pgvector alternatives · VectorChord alternatives

GraphCanon updated Sep 20, 2026

16views this month

pgvector logo

pgvector

pgvector/pgvector

★ 23kpushed Sep 10, 2026
vs
VectorChord logo

VectorChord

supervc-stack/VectorChord

★ 1.8kpushed Aug 6, 2026

Trust & integrity

SignalpgvectorVectorChord
Maintenance
Active (7d since push)
As of Sep 18, 2026 · github_public_v1
Steady (43d since push)
As of Sep 18, 2026 · github_public_v1
Provenance
Not a fork · Organization account
As of Sep 18, 2026 · github_public_v1
Not a fork · Personal account
As of Sep 18, 2026 · github_public_v1
OSV dependency advisories
No lockfile (source not queried)
As of Sep 18, 2026 · osv@v1
No lockfile (source not queried)
As of Sep 18, 2026 · osv@v1
deps.dev advisories
Not queried
deps.dev@v1
Not queried
deps.dev@v1
OpenSSF Scorecard
Not queried
openssf-scorecard@v1
Not queried
openssf-scorecard@v1

Tagline

pgvector
Open-source vector similarity search for Postgres
VectorChord
Scalable, fast, and disk-friendly vector search in Postgres

Stars

pgvector
23k
VectorChord
1.8k

Forks

pgvector
1.3k
VectorChord
72

Open issues

pgvector
16
VectorChord
19

Language

pgvector
C
VectorChord
Rust

Adopt for

pgvector
pgvector is an extension for PostgreSQL that enables efficient vector similarity search using various distance metrics, including L2, inner product, cosine distance, and L1 distance.
VectorChord
VectorChord is a vector database extension for PostgreSQL, offering scalable and efficient vector search capabilities. It supports vector indexing and retrieval, making it suitable for applications requiring fast and low

Persona

pgvector
-
VectorChord
-

Runtime

pgvector
-
VectorChord
-

License

pgvector
Other
VectorChord
Other

Last pushed

pgvector
Sep 10, 2026
VectorChord
Aug 6, 2026

Categories

pgvector
Vector Databases
VectorChord
Vector Databases

Trust and health

Maintenance

pgvector
Active (82%)
VectorChord
Steady (60%)

Days since push

pgvector
7d
VectorChord
43d

Open issues (now)

pgvector
16
VectorChord
19

Stars delta

pgvector
+674 (30d)
VectorChord
+37 (30d)

Owner type

pgvector
Organization
VectorChord
User

Full report

pgvector
Trust report
VectorChord
Trust report

Typed relationship

pgvector alternative VectorChordVectorChord and pgvector both offer scalable, low-latency vector search solutions integrated with PostgreSQL databases, providing similar capabilities but through different implementations.

Choose pgvector if…

  • pgvector is primarily C; VectorChord is Rust.
  • VectorChord and pgvector both offer scalable, low-latency vector search solutions integrated with PostgreSQL databases, providing similar capabilities but through different implementations.
  • Tags unique to pgvector: approximate-nearest-neighbor-search, c-language, docker-support, l2-distance.
  • pgvector ships Docker support for self-hosted deployment.
  • When you need to perform vector similarity searches within a PostgreSQL database and require support for multiple distance metrics.

When NOT to use pgvector

  • If your application does not require the full feature set of PostgreSQL and you are looking for a lightweight solution specifically designed for vector similarity searches.
  • When you need real-time, low-latency vector similarity searches that might be better served by specialized vector databases or in-memory solutions.
  • If you are working in an environment where PostgreSQL is not supported or where you need to integrate with a different database system.
  • When you require a solution that supports more advanced indexing techniques or approximate nearest neighbor search algorithms that are not natively supported by pgvector.

Choose VectorChord if…

  • VectorChord is primarily Rust; pgvector is C.
  • VectorChord and pgvector both offer scalable, low-latency vector search solutions integrated with PostgreSQL databases, providing similar capabilities but through different implementations.
  • Tags unique to VectorChord: artificial-intelligence, llmops, postgresql, vector-database.
  • When you need a vector database extension that is compatible with PostgreSQL and requires minimal setup, as VectorChord can be easily integrated using Docker or other installation methods.

When NOT to use VectorChord

  • If your application does not require PostgreSQL as the underlying database, as VectorChord is specifically designed as an extension for PostgreSQL.
  • When you need a standalone vector database solution that does not depend on PostgreSQL, as VectorChord is tightly integrated with PostgreSQL and may not be suitable for environments without it.
  • If your project does not benefit from the specific indexing and retrieval capabilities provided by VectorChord, such as `vchordrq` indexes, and you require a more generalized vector database solution.
  • When you are looking for a tool that supports a wider range of database systems beyond PostgreSQL, as VectorChord is limited to PostgreSQL environments.

Explore

Sources

Every stat on this page traces to a dated GitHub sync, license file, enrichment field, or trust scan.

GitHub stars on cards: pgvector 23k · VectorChord 1.8k (synced Sep 20, 2026).

Common questions

What is the difference between pgvector and VectorChord?
pgvector: Open-source vector similarity search for Postgres. VectorChord: Scalable, fast, and disk-friendly vector search in Postgres. See the comparison table for live GitHub stats and shared categories.
When should I choose pgvector over VectorChord?
Choose pgvector over VectorChord when pgvector is primarily C; VectorChord is Rust; VectorChord and pgvector both offer scalable, low-latency vector search solutions integrated with PostgreSQL databases, providing similar capabilities but through different implementations; Tags unique to pgvector: approximate-nearest-neighbor-search, c-language, docker-support, l2-distance; pgvector ships Docker support for self-hosted deployment; When you need to perform vector similarity searches within a PostgreSQL database and require support for multiple distance metrics.
When should I choose VectorChord over pgvector?
Choose VectorChord over pgvector when VectorChord is primarily Rust; pgvector is C; VectorChord and pgvector both offer scalable, low-latency vector search solutions integrated with PostgreSQL databases, providing similar capabilities but through different implementations; Tags unique to VectorChord: artificial-intelligence, llmops, postgresql, vector-database; When you need a vector database extension that is compatible with PostgreSQL and requires minimal setup, as VectorChord can be easily integrated using Docker or other installation methods.
When should I avoid pgvector?
If your application does not require the full feature set of PostgreSQL and you are looking for a lightweight solution specifically designed for vector similarity searches. When you need real-time, low-latency vector similarity searches that might be better served by specialized vector databases or in-memory solutions. If you are working in an environment where PostgreSQL is not supported or where you need to integrate with a different database system. When you require a solution that supports more advanced indexing techniques or approximate nearest neighbor search algorithms that are not natively supported by pgvector.
When should I avoid VectorChord?
If your application does not require PostgreSQL as the underlying database, as VectorChord is specifically designed as an extension for PostgreSQL. When you need a standalone vector database solution that does not depend on PostgreSQL, as VectorChord is tightly integrated with PostgreSQL and may not be suitable for environments without it. If your project does not benefit from the specific indexing and retrieval capabilities provided by VectorChord, such as vchordrq indexes, and you require a more generalized vector database solution. When you are looking for a tool that supports a wider range of database systems beyond PostgreSQL, as VectorChord is limited to PostgreSQL environments.
Is pgvector or VectorChord more popular on GitHub?
pgvector has more GitHub stars (23,049 vs 1,795). Stars measure visibility, not whether either tool fits your constraints.
Are pgvector and VectorChord open source?
Yes - both are open-source projects on GitHub (pgvector: Other, VectorChord: Other).
Where can I find alternatives to pgvector or VectorChord?
GraphCanon lists graph-backed alternatives at pgvector alternatives and VectorChord alternatives (pgvector markdown twin, VectorChord markdown twin), ranked by typed relationship edges rather than popularity votes.
Is there a machine-readable version of this comparison?
Yes. The markdown twin at this comparison mirrors this page for agents and LLM crawlers, with the same stats table and FAQ answers.
Which is better maintained, pgvector or VectorChord?
pgvector: Active. VectorChord: Steady. Compare maintenance labels, days since push, and release cadence in the trust section below - stars alone do not measure maintenance.
Where are the full trust reports for pgvector and VectorChord?
GraphCanon publishes per-repo trust reports with dated maintenance, provenance, and scan summaries: pgvector trust report; VectorChord trust report.

Was this helpful?

Anonymous feedback helps us improve pages and translations.