Enable Database Connection Pooler in Supabase’s Local Development

Sep 18, 2025 - 2 MIN READ

Enable Connection Pooler in Local Dev

Update supabase config.toml to enable [db.pooler] and configure the pooler as you wish.

config.toml

[db.pooler]
enabled = true
# Port to use for the local connection pooler.
port = 54329
# Specifies when a server connection can be reused by other clients.
# Configure one of the supported pooler modes: `transaction`, `session`.
pool_mode = "transaction"
# How many server connections to allow per user/database pair.
default_pool_size = 20
# Maximum number of client connections allowed.
max_client_conn = 100

Then, you can update your dabatabase connection string to use pooler-dev user, eg:

.env

postgresql://postgres.pooler-dev:postgres@localhost:54329/postgres

Faris Perwira

Fullstack Developer

Adding a Root Error Component to a shadcn/ui Form

When building a form with shadcn/ui, there are existing form error messages for form fields, but there is no component to display the root error of the form.

Extending Supabase Auth Users Table

Recently, I worked on a project that uses Supabase, and it has a Profile feature for users that required me to extend Supabase’s auth.users table.