TL;DR: Features that assume "my session" break in ways that look like app bugs: search_path resets, LISTEN never fires, temp tables vanish. ## The rule: the unsupported list (from Neon's docs) Not supported with pooled connections: - SET / RESET (session variables) - LISTEN / NOTIFY - WITH HOLD cursors - PREPARE / DEALLOCATE - Temporary tables with ON COMMIT PRESERVE ROWS / DELETE ROWS quirks - LOAD - Session-level advisory locks ## Limits to know -

## Fix
1. Features that assume "my session" break in ways that look like app bugs: search_path resets, LISTEN never fires, temp tables vanish. ## The rule: the unsupported list (from Neon's docs) Not supported with pooled connections: - SET / RESET (session variables) - LISTEN / NOTIFY - WITH HOLD cursors - PREPARE / DEALLOCATE - Temporary tables with ON COMMIT PRESERVE ROWS / DELETE ROWS quirks - LOAD - Session-level advisory locks ## Limits to know -.
   Expected: this specific failure stops.
2. : direct-to-Postgres limit by compute size; beyond it "too many clients already". ## Checklist - Hitting any item on the unsupported list: switch that workload to the direct connection string. - Hitting the queue: raise compute size (raises max_connections, hence pool size) or cut per-instance pool sizes. - Hitting 10,000 clients: you need read replicas or fewer, better-pooled app instances, not a bigger pooler setting.
   Expected: the request routes instead of erroring.

## Details
`pool_mode=transaction` `max_client_conn` : 10,000 client connections to PgBouncer; beyond that clients get "no more connections allowed". - `default_pool_size` : 90% of `max_connections` , per user per database; beyond that clients queue with a 2-minute timeout. - `max_connections`

## When to use
You hit exactly this: Neon PgBouncer runs transaction mode: know the unsupported list in Neon PgBouncer runs transaction mode.

## When not to use
A different error, or the same symptom in a different tool. This page only covers the failure above.

## Compatibility
Neon PgBouncer runs transaction mode.

## Root cause
means the server-side connection is reassigned after every transaction.

## Edge cases
- # The pooler's transaction mode and what it forbids ## The trap.