new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

Supabase · Database · all subjects

connection-pooling/pool-size

1 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Pool size setting behavior with Supavisor and PgBouncer

Supavisor and PgBouncer work independently but both reference the same pool size setting. For example, if you set the pool size to 30, Supavisor can open up to 30 server-side connections to Postgres. These connections are shared between the session mode port (5432) and the transaction mode port (6543). Each mode can use up to 30 connections independently or split them, but the total combined connections across both modes cannot exceed 30. PgBouncer can also open up to 30 connections under the same limit. If both poolers are active and reach their role/mode limits simultaneously, you could have as many as 60 backend connections hitting your database in addition to any direct connections.

Give your agent this brain