pgrx
qdrant
pgrx | qdrant | |
---|---|---|
13 | 141 | |
3,245 | 18,036 | |
3.3% | 3.9% | |
9.5 | 9.9 | |
6 days ago | 4 days ago | |
Rust | Rust | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pgrx
-
Building a Managed Postgres Service in Rust
Consider also the companies and work behind pgrx [0] and pgzx [1]:
[0] https://github.com/pgcentralfoundation/pgrx
[1] https://github.com/xataio/pgzx
-
UUIDv7 is coming in PostgreSQL 17
If you like this (I do very much), you might also like pg_idkit[0] which is a little extension with a bunch of other kinds of IDs that you can generate inside PG, thanks to the seriously awesome pgrx[1] and Rust.
[0]: https://github.com/VADOSWARE/pg_idkit
[1]: https://github.com/pgcentralfoundation/pgrx
-
90x Faster Than Pgvector – Lantern's HNSW Index Creation Time
(disclosure, i work at supabase and have been developing TLEs with the RDS team)
Trusted Language Extensions refer to an extension written in any trusted language. In this case Rust, but it also includes: plpgsql, plv8, etc. See [0]
> PL/Rust is a more performant and more feature-rich alternative to PL/pgSQL
This is only partially true. plpgsql has bindings to low-level Postgres APIs, so in some cases it is just as fast (or faster) than Rust.
> Building a vector index (or any index for that matter) inside Postgres is a more involved process and can not be done via the UDF interface, be it Rust, C or PL/pgSQL
Most PG Rust extensions are written with the excellent pgrx framework [1]. While it doesn't have index bindings right now, I can certainly imagine a future where this is possible[2].
All that said - I think there are a lot of hoops to jump through right now and I doubt it's worth it for the Latern team. I think they are right to focus on developing a separate C extension
[0] TLE: https://supabase.com/blog/pg-tle
[1] pgrx: https://github.com/pgcentralfoundation/pgrx
[2] https://github.com/pgcentralfoundation/pgrx/issues/190#issue...
-
SQL as API
I’m currently playing with PostgreSQL, foreign data wrappers, and pgrx rust extensions. My development experience has been surprisingly smooth and enjoyable.
My main issue is that joins will be processed locally, so all the foreign data will be fetched before the join happens. But otherwise basic CRUD is easy.
https://wiki.postgresql.org/wiki/Foreign_data_wrappers
https://github.com/pgcentralfoundation/pgrx
https://github.com/supabase/wrappers
-
Postgres: The Next Generation
I think maybe what you’re really looking for are the files here: https://github.com/pgcentralfoundation/pgrx/tree/c2eac033856...
Those are the internals we currently expose as unsafe “sys” bindings.
As we/contributors identify more that are desired we add them.
pgrx’ focus is on providing safe wrappers and general interfaces to the Postgres internals, which is the bulk of our work and is what will take many years.
As unsafe bindings go, we could just expose everything, and likely eventually will. There’s just some practical management concerns around doing that without a better namespace organization —- something we’ve been working.
The Postgres sources are not small. They are very complex, inconsistent in places, and often follow patterns that are specific to Postgres and not easy to generalize.
If you’ve never built an extension with pgrx, give it a shot one afternoon. It’s very exciting to see your own code running in your database.
- Pgrx – Build Postgres Extensions with Rust
-
Pg_bm25: Elastic-Quality Full Text Search Inside Postgres
pgrx is one of the greatest enabling innovations in the PG ecosystem in a long time.
Awesome to see so many high quality extensions come out of it.
https://github.com/pgcentralfoundation/pgrx
- PGRX v0.9.7
- Let's make PostgreSQL multi-threaded (pgsql-hackers)
-
Build high-performance functions in Rust on Amazon RDS for PostgreSQL
If you're interested in what my Threadripper 3970X does with it, there's some numbers in this PR: https://github.com/tcdi/pgrx/pull/1147
qdrant
-
Hindi-Language AI Chatbot for Enterprises Using Qdrant, MLFlow, and LangChain
Great. Now that we have the embeddings, we need to store them in a vector database. We will be using Qdrant for this purpose. Qdrant is an open-source vector database that allows you to store and query high-dimensional vectors. The easiest way to get started with the Qdrant database is using the docker.
-
Boost Your Code's Efficiency: Introducing Semantic Cache with Qdrant
I took Qdrant for this project. The reason was that Qdrant stands for high-performance vector search, the best choice against use cases like finding similar function calls based on semantic similarity. Qdrant is not only powerful but also scalable to support a variety of advanced search features that are greatly useful to nuanced caching mechanisms like ours.
-
Ask HN: Has Anyone Trained a personal LLM using their personal notes?
I'm currently looking to implement locally, using QDrant [1] for instance.
I'm just playing around, but it makes sense to have a runnable example for our users at work too :) [2].
[1]. https://qdrant.tech/
-
Show HN: A fast HNSW implementation in Rust
Also compare with qdrant's Rust implementation; they tout their performance. https://github.com/qdrant/qdrant/tree/master/lib/segment/src...
-
pgvecto.rs alternatives - qdrant and Weaviate
3 projects | 13 Mar 2024
-
Open-source Rust-based RAG
There are much better known examples, such as https://qdrant.tech/ and https://github.com/lancedb/lancedb
-
Qdrant 1.8.0 - Major Performance Enhancements
For more information, see our release notes. Qdrant is an open source project. We welcome your contributions; raise issues, or contribute via pull requests!
-
Perform Image-Driven Reverse Image Search on E-Commerce Sites with ImageBind and Qdrant
Initialize the Qdrant Client with in-memory storage. The collection name will be “imagebind_data” and we will be using cosine distance.
-
7 Vector Databases Every Developer Should Know!
Qdrant is an open-source vector search engine optimized for performance and flexibility. It supports both exact and approximate nearest neighbor search, providing a balance between accuracy and speed for various AI and ML applications.
- Ask HN: Who is hiring? (February 2024)
What are some alternatives?
api - 🚀 Core REST API & Gateway for Zaun
Milvus - A cloud-native vector database, storage for next generation AI applications
plrust - A Rust procedural language handler for PostgreSQL
Weaviate - Weaviate is an open-source vector database that stores both objects and vectors, allowing for the combination of vector search with structured filtering with the fault tolerance and scalability of a cloud-native database.
readyset - Readyset is a MySQL and Postgres wire-compatible caching layer that sits in front of existing databases to speed up queries and horizontally scale read throughput. Under the hood, ReadySet caches the results of cached select statements and incrementally updates these results over time as the underlying data changes.
faiss - A library for efficient similarity search and clustering of dense vectors.
mimir - ⚡ Supercharged Flutter/Dart Database
pgvector - Open-source vector similarity search for Postgres
paradedb - Postgres for Search and Analytics
Elasticsearch - Free and Open, Distributed, RESTful Search Engine
influxdb_iox - Pronounced (influxdb eye-ox), short for iron oxide. This is the new core of InfluxDB written in Rust on top of Apache Arrow.
towhee - Towhee is a framework that is dedicated to making neural data processing pipelines simple and fast.