supavisor
supavisor copied to clipboard
supabase
A cloud-native, multi-tenant Postgres connection pooler.
Blocked by [logflare_logger_backend which is blocked by etso](https://github.com/Logflare/logflare_logger_backend/issues/106).
Should be able to throttle the network throughput on some dimension such that one tenant cannot consume all network bandwidth.
For draining transactions to a tenant database. See: https://www.pgbouncer.org/usage.html#admin-console - optional timeout argument which disconnects database on timeout and prevents new connections from being established
- With [burrito](https://github.com/burrito-elixir/burrito) - (optional) apply config from command line args and/or config file
this is a separate discussion (apologies, I don't think we had one about it!) but while mocking is pretty convenient here I think it provides less confidence and more fragile...
We get a lot of log messages about `function_clause` errors etc that are actually just a result of bots sending packets to Supavisor. This change filters out the noise from...
Can tenant.users ever be a very large number? Because if yes, then this operation can take quite some time and it may be worth discussing if this is a problem...
- [Postgrex.ReplicationConnection behavior](https://hexdocs.pm/postgrex/Postgrex.ReplicationConnection.html) - Configurable: should be able to setup the replication connection however a tenant would want - Verify configuration on connection and error if tenant publication does not...
# Bug report ## Describe the bug When using port "5432" things work with the obvious limits. AppSheet (a no-code platform owned by Google) opens a connection for each CRUD...
