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/limits

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

Client connections vs backend connections

Client connections refer to how many clients can connect to a pooler at the same time. This number is capped by your compute tier's "max pooler clients" limit and applies independently to Supavisor and PgBouncer. Backend connections is the number of active connections a pooler opens to Postgres, which is set by the pool size for that pooler. Total backend load on Postgres = Direct connections + Supavisor backend connections (≤ supavisor_pool_size) + PgBouncer backend connections (≤ pgbouncer_pool_size) ≤ Postgres max connections for your compute instance.

Max pooler clients limit behavior

The "max pooler clients" limit for your compute tier applies separately to Supavisor and PgBouncer. One pooler reaching its client limit does not affect the other. When a pooler reaches this limit, it stops accepting new client connections until existing ones are closed, but the other pooler remains unaffected.

Give your agent this brain