Supabase PostgreSQL Max Client Connections Reached with Prisma

VERIFIED WAYPOINT ⚡ Saves ~52,000 tokens ($0.18) Category: Databases & Cloud

🎯 Target Goal & Friction

Goal: Configure Supabase PgBouncer / Supavisor connection pooling for serverless

Error Signature: FATAL: remaining connection slots are reserved for non-replication superuser connections

⚡ Direct Teleport Deep Link (0ms Navigation)

https://supabase.com/dashboard/project/{ref}/settings/database →

Agents skip UI exploration menus by navigating directly to this endpoint.

Verified Code / Configuration Diff

@@ prisma/schema.prisma @@
  datasource db {
    provider  = "postgresql"
-   url       = env("DATABASE_URL")
+   url       = env("POSTGRES_PRISMA_URL") // Port 6543 (Transaction mode)
+   directUrl = env("POSTGRES_URL_NON_POOLING") // Port 5432 (Session mode for migrations)
  }

1-Line Instant CLI Fix

npx prisma generate

Root Cause & Explanation

Serverless functions spawn hundreds of concurrent PostgreSQL connections. Use Supabase pooler on port 6543 with separate `directUrl` for migrations.