SQLSTATE 53100disk_fullHTTP 503
Postgres error 53100: disk full
could not extend file: No space left on device
The disk holding the database is full.
Common causes
- Data growth, table bloat from updates and deletes, or WAL kept for a lagging replication slot.
- Temporary files from large sorts or hash joins.
How to fix it
- Check for inactive replication slots holding WAL: select slot_name, active from pg_replication_slots;
- Find the largest tables and indexes (pg_total_relation_size) and remove bloat or old data.
- Add disk, then fix the cause.
Through a REST API
PostgREST, the REST layer behind supabase-js and Scribase, answers HTTP 503 for this error and returns the SQLSTATE in the code field of the JSON error body.
Questions
What does Postgres error 53100 mean?
53100 is disk_full in class 53 (Insufficient Resources). The disk holding the database is full.
How do I fix 53100?
Check for inactive replication slots holding WAL: select slot_name, active from pg_replication_slots; Find the largest tables and indexes (pg_total_relation_size) and remove bloat or old data. Add disk, then fix the cause.
What HTTP status does a REST API return for 53100?
PostgREST, the REST layer behind supabase-js, answers 503.