4 ms·
Specifically with PostgreSQL, number of connections is still the killer (if you don’t have smart proxies). So you can’t be cavalier about putting as many use ca
by didip 3y ago
Specifically with PostgreSQL, number of connections is still the killer (if you don’t have smart proxies). So you can’t be cavalier about putting as many use cases as possible.
For example, when using PG pub/sub, you will run out of connections quick.
Generally, all DBMS needs a smart self adjusting query killer. Without it, one bad query will ruin it for everyone.
- cpursley 3y agoWalEx instead of pub/sub (listen/subscribe): https://github.com/cpursley/walex https://github.com/cpursley/walex Supavisor connection pooler: https://github.com/supabase/supavisor https://github.com/supabase/supavisor