supavisor
wal-g
| supavisor | wal-g | |
|---|---|---|
| 15 | 13 | |
| 1,591 | 3,053 | |
| 1.8% | 1.2% | |
| 8.9 | 9.0 | |
| 3 days ago | 2 days ago | |
| Elixir | Go | |
| Apache License 2.0 | GNU General Public License v3.0 or later |
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
wal-g
- WAL-G 3.0.0 – fast disaster recovery for Postgres
-
Introducing Read Replicas
Streaming replication minimizes replication lag, while file-based log shipping provides a fallback. For file-based log shipping, we use our existing Point In Time Recovery (PITR) infrastructure. We regularly archive files from the primary using WAL-G, an open source archival and restoration tool, and ship the WAL files to S3.
- WAL-G 2.0: backup and restore for database in the cloud
- Script to take PostgreSQL backups
-
Go 1.18 (Go with generics) no blocking issues left
While everyone fears some new spiral of complexity, it's nice
https://github.com/wal-g/wal-g/pull/1186
Add a few type constraints, throw out a few type casts along with the error handling
- Optimizing Postgres Queries at Scale
-
A rough proposal for sum types in Go, from a Rust compiler engineer
When it's occasionally useful return (type, err), but generally the two results are distinct so there's no need to return two results in the general case when one suffices
Indeed, I recently updated some code to return a relevant value in the error case: https://github.com/wal-g/wal-g/pull/1143/files#diff-d896e5d5...
- WAL-G 1.1 released: better disaster recovery for PG, MySQL, MongoDB, MS SQL
-
Automate pg_basebackup in linux
Have a look at barman, pgBackrest or for maybe WAL-G or WAL-E
- WAL-G 1.0: unified backup tool for PostgreSQL, MySQL, SQL Server, MongoDB, Redis
What are some alternatives?
pgcat - PostgreSQL pooler with sharding, load balancing and failover support.
pgBackRest - Reliable PostgreSQL Backup & Restore
pg_tle - Framework for building trusted language extensions for PostgreSQL
wal-e - Continuous Archiving for Postgres
mssql-changefeed
docker-postgres-wale - Postgres docker container with WALE-E installed
debezium - Change data capture for a variety of databases. Please log issues at https://issues.redhat.com/browse/DBZ.
citus-failover - Worker failover support for PostgreSQL Citus extension using pg_auto_failover.
sql-examples - Curated list of SQL to help you find useful script easily 🚀
gobackup - 🗄 CLI tool for backup your databases, files to cloud storages in schedully.
walex - Postgres change events (CDC) in Elixir
spilo - Highly available elephant herd: HA PostgreSQL cluster using Docker