DEV Community

Discussion on: Breaking Postgres with Too Many Tables

Collapse
 
darkain profile image
Vincent Milum Jr

It sounds like you may have hit the file system inode limit instead of storage limit. Both usually give the same error message. I've seen this error on badly configured PHP instances that store session data to disk, then never run the garbage collection script. TONS of nearly empty files, but hundreds of GB left on disk. Failed due to overwhelming the inode table in the file system.