pgrx
wrappers
pgrx | wrappers | |
---|---|---|
13 | 11 | |
3,245 | 440 | |
3.3% | 3.9% | |
9.5 | 9.5 | |
6 days ago | 18 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
wrappers
-
Should I Open Source my Company?
I used one of their open source work in a project: https://github.com/supabase/wrappers
It’s appreciated since SaaS on AWS is a no-no in my field.
-
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
-
Is anyone here interested in a general purpose guide on how to sync data between Supabase and outside resources?
However, considering the emergence of Supabase wrappers, it might be more beneficial to develop a walkthrough focused on creating Rust-based wrappers. This way, the community can start building a variety of useful wrappers (really plugins).
- Supabase Wrappers
-
Hasura Remote Schema analogue in Supabase
We're experimenting with including tables connected to external data sources using Supabase Wrappers https://github.com/supabase/wrappers as a way to link external APIs into the GraphQL schema but that work is in an early stage. That approach would be limited to the Stripe, Firebase and S3 for now though
-
Is it possible to directly connect Supabase to a MySQL database?
This would be an ideal use case for a postgresql foreign data wrapper. See more here: https://github.com/supabase/wrappers/
- Supabase Wrappers: A Framework for Postgres Foreign Data Wrappers
-
Supabase Wrappers: A Framework for Building Postgres Foreign Data Wrappers
> On a sidenote, is not the wrappers for Airtable, BigQuery and ClickHouse opensourced? Or why did they skip that column in the second table?
All of the wrappers are open source. You can see the source for the Airtable, BigQuery, and ClickHouse wrappers here https://github.com/supabase/wrappers/tree/5fac8afb62e6e8362b...
The `self-hosted` column is only missing from the "under development" wrappers in the blog post's table because those are not production ready and shouldn't be self hosted (yet).
What are some alternatives?
api - 🚀 Core REST API & Gateway for Zaun
steampipe - Zero-ETL, infinite possibilities. Live query APIs, code & more with SQL. No DB required.
plrust - A Rust procedural language handler for PostgreSQL
Multicorn - Data Access Library
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.
multicorn2
mimir - ⚡ Supercharged Flutter/Dart Database
pgsql-http - HTTP client for PostgreSQL, retrieve a web page from inside the database.
paradedb - Postgres for Search and Analytics
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
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.
wundergraph - WunderGraph is a Backend for Frontend Framework to optimize frontend, fullstack and backend developer workflows through API Composition.