supavisor
pg_tle
supavisor | pg_tle | |
---|---|---|
15 | 9 | |
1,591 | 300 | |
1.8% | 5.3% | |
8.9 | 7.5 | |
2 days ago | 13 days ago | |
Elixir | C | |
Apache License 2.0 | 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.
supavisor
-
PostgreSQL Is Enough
WalEx instead of pub/sub (listen/subscribe): https://github.com/cpursley/walex
Supavisor connection pooler: https://github.com/supabase/supavisor
-
Introducing Read Replicas
To make use of your read replicas, copy your connection string for the read replica, update your apps to use the new read replica and you are done! A unique connection pool is also provisioned for each read replica via Supavisor.
-
Supavisor 1.0: a scalable connection pooler for Postgres
[I'm on the supabase team]
You can find the code/docs here: https://github.com/supabase/supavisor
This release adds support for
- SQL Parsing
- Load balancing
- support for named prepared statement
- query cancellation
It's also now available on all new databases in Supabase. For some more background on scalability, we have some benchmarks available here:
https://supabase.com/blog/supavisor-1-million
-
PgBouncer 1.21.0 released with prepared statement support
PgBouncer maintainer here, so obviously biased. But I think currently PgBouncer should still be the default connection pooler that you choose. There's a few newer options: Odyssey, pgcat, and supavisor. But all focus on a solving 1 or 2 specific problems that PgBouncer did not solve well, while not solving many of the other problems that PgBouncer does solve. So if you have the exact same requirements as the authors of those tools, then switching might be good. But otherwise you should probably continue using PgBouncer.
Supavisor specifically is really immature. It's missing some really core functionality like query cancellations: https://github.com/supabase/supavisor/issues/174
I did a talk on this exact topic at PGConf NYC recently. My slides are here: https://github.com/JelteF/slides/raw/main/2023-10-05-future-...
-
Supavisor: Scaling Postgres to 1 Million Connections
If you are interested in exploring Supavisor's potential or want to implement its scalability in your upcoming project, check out the GitHub repository to know more.
-
How to Listen to Database Changes Using Postgres Triggers in Elixir
Phoenix.PubSub is basically a noop service. It really just works. You should try it!
If discovering nodes is difficult in your env, try using a listen/notify libcluster strategy:
https://github.com/supabase/supavisor/blob/main/lib/cluster/...
-
The Database Package Manager for PostgreSQL Trusted Language Extensions
[2] https://github.com/supabase/supavisor
-
Supabase Logs: open source logging server
Supavisor
- Supavisor - Postgres connection pooler written in Elixir
- Supavisor - a Postgres connection pooler written in Elixir
pg_tle
-
Pgcopydb: Copy a Postgres database to a target Postgres server
Have you tried this in databases with [TLE](https://github.com/aws/pg_tle)s?
-
Making PostgreSQL tick: New features in pg_cron
I dunno about other hosted Postgres providers, but not on AWS RDS no, as the Python extension is untrusted. Looks like you can use plv8 via pg_tle (Trusted Language Extensions) [1] though.
[1] https://github.com/aws/pg_tle
-
The Database Package Manager for PostgreSQL Trusted Language Extensions
Partially correct, this doesn't work with RDS as you can't install pgsql-http (a requirement for automatic install). However all the extensions listed are "Trusted Language Extensions for PostgreSQL" which was developed by AWS to enable installing extensions written in "Safe" languages. So I believe the all the extensions listed could bee installed manually.
https://github.com/aws/pg_tle
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Postg...
-
Choosing a Postgres Primary Key
>pg_idkit to their list of supported extensions
For some of these simpler extensions, we're looking at using AWS's TLE (https://github.com/aws/pg_tle), which would allow user-contributed extensions. If we can pull that off, we'll probably look again at the current set of extensions we offer and then see which ones can be ported to a TLE instead
-
postgres extension managers
This is a new thing from AWS: https://github.com/aws/pg_tle. It lets you build extensions that people can use on RDS.
-
SQL Macros in YugabyteDB
I'm taking those functions from the examples in pg_tle, an extension that helps packaging those functions. The functions calculate the Manhattan and Euclidian distance:
- Trusted Language Extensions for PostgreSQL (Pg_tle)
- GitHub - aws/pg_tle: Framework for building trusted language extensions for PostgreSQL
- AWS releases open source Trusted Language Extensions for PostgreSQL
What are some alternatives?
pgcat - PostgreSQL pooler with sharding, load balancing and failover support.
omnigres - Postgres as a Platform
mssql-changefeed
set_user - PostgreSQL extension allowing privilege escalation with enhanced logging and control
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
sequential-uuids - generator of sequential UUIDs
sql-examples - Curated list of SQL to help you find useful script easily 🚀
vasco - vasco: MIC & MINE statistics for Postgres
walex - Postgres change events (CDC) in Elixir
cainophile
hydra - Hydra: Column-oriented Postgres. Add scalable analytics to your project in minutes.