3 ms·
I'm excited to switch to this - I've been building Booklet on Fly.io and their Postgres to make the app distributed [1]. The biggest problem for me has been the
by philip1209 3y ago
I'm excited to switch to this - I've been building Booklet on Fly.io and their Postgres to make the app distributed [1]. The biggest problem for me has been the Fly postgres configuration. Specifically, Fly puts HAProxy in front of Postgres with a 30m connection timeout [2], which keeps killing connections. This should be manageable, but I'm seeing quirks in the connection terminations that don't seem to align with their docs and keep causing instability.
Question for the team members here - will the new PG still have the same HAProxy in front?
[1] https://www.contraption.co/essays/booklet-architecture/ https://www.contraption.co/essays/booklet-architecture/
[2] https://community.fly.io/t/postgresql-connection-issues-have-returned/6424 https://community.fly.io/t/postgresql-connection-issues-have...
- kiwicopple 3y agoit will have our own connection pooler[0] for Postgres connections instead of HAProxy, as well as PostgREST[1] for REST [0] https://supabase.com/blog/supavisor-postgres-connection-pooler https://supabase.com/blog/supavisor-postgres-connection-pool... [1] https://postgrest.org/ https://postgrest.org/