7 people reported
All time, since May 14.
Disk-full WAL crash loop
“My free-tier project is down and stuck in a crash-recovery loop.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/supabase/issues/8784/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Database stuck in crash loop after disk fills with WAL. Startup fails writing "pg_wal/xlogtemp" with "No space left on device"; project shows "Unhealthy" and pause or resize does not recover it.
Is this your bug?
File my report- Where
- Postgres database
- Error text
FATAL: could not write to file "pg_wal/xlogtemp.NNNN": No space left on devicePasted in 2 reportsFATAL: 57P03: the database system is not accepting connectionsPasted in 2 reports- How bad
- Stops work: a core feature can't be used. Most reports say it blocks them completely.
Not quite your bug?
- Database unreachable after restart2 people
- Project stuck in "Coming up"5 people
- Project stuck restarting2 people
Original reports7, newest first
- Project unhealthy, disk full, FATAL 57P03 "not accepting connections" (Free plan, eu-west-3)#50989
- Free Plan Project Stuck in "Unhealthy" State - Database Crashed Due to "No space left on device" (pg_wal) - Cannot Restart or Pause#50815
- Production DB down 24h+ — disk full, Postgres PANIC crash loop (Free plan, ticket SU-481720)#50787
- Free project stuck in recovery after disk full — is Pause/Resume safe?#50084
- My free project's disk filled up with WAL, database won't start, and pause won't stick — ticket SU-442291#48904
- Free-tier project stuck in disk-full WAL crash loop, database won't start (57P03)#48507
- Project Unhealthy - Disk 92% - 57P03 Hot standby mode disabled (Free tier)#45958