AI & Agent Dev Bug Sandbox Back to Radar

Intermittent SQLSTATE 57P01 Admin-Command Terminations After ACTIVE_HEALTHY In Hosted Preview Branches Via Session Pooler

Newly created hosted preview branches intermittently terminate active database sessions with FATAL SQLSTATE 57P01 after the branch reports ACTIVE_HEALTHY and after initial migrations/smoke queries succeed. The issue appears tied to preview-branch provisioning or the shared session pooler rather than application code.

highConfidence 65%Supabase

Origin Analysis

The most likely root cause is a race in Supabase's preview-branch provisioning: ACTIVE_HEALTHY is reported before all administrative operations (e.g., backend restarts, pooler reconfiguration, or schema synchronization) have fully quiesced, so the shared session pooler may hand out connections that a delayed administrator command later terminates.

1. Create a disposable, non-persistent hosted preview branch.\n2. Wait until branch status reports ACTIVE_HEALTHY.\n3. Connect through the shared session pooler on port 5432 using Postgres.js with { prepare: false, max: 2, idle_timeout: 20 }.\n4. Apply migrations and run a basic read query; both succeed.\n5. Execute an integration workload with reads/transactions and observe intermittent FATAL: terminating connection due to administrator command (SQLSTATE 57P01).

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

Retrying after 57P01 can duplicate non-idempotent writes; apply this wrapper only to idempotent reads or add application-level idempotency keys for writes. Bounded retries prevent infinite loops, but persistent 57P01 may indicate an ongoing platform issue. Rollback: remove the wrapper or set maxRetries to 0 if it masks real failures. If terminations persist, collect backend PIDs from server logs and open a support ticket.