Chase Granberry
Chase Granberry
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
- [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...
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? First go at docs for Realtime Authz h/t @filipecabaco
Currently if a client is connected to a Supavisor node which does not own the pool there is communication with the pool processes which happen over Erlang distribution. With Erlang...
When looking at connections in Postgres I should be able to see the application_name set by clients if connected via session mode through Supavisor. select usename, application_name from pg_stat_activity; application_name...
As a developer, if I want to ensure my private messages are sent on a private Channel I can include a `private` key with value `true`. If a message with...
Postgres [sends these messages](https://github.com/cpursley/walex/blob/master/lib/walex/replication/server.ex#L148), and then based on [the reply](https://github.com/cpursley/walex/blob/master/lib/walex/replication/server.ex#L151) discards the wal up to that position. As a developer I should be able to have my event handler update...
Would be great to have [Postgres wire protocol](https://www.postgresql.org/docs/current/protocol.html) support. It's difficult to debug slow queries across disparate clients, networks and servers with (potentially) connection poolers in between.