Task #882
Updated by Aaron Marcuse-Kubitza about 10 years ago
* running many processes at once (as full-database import does) can cause all the available disk space to be used up, due to bugs in Postgres[1] (which does not have an internal throttle on temporary disk space, only memory) * because there is no soft limit on disk space inside Postgres (or our import scripts), the hard limit gets reached instead, causing an error which ricochets across the system, causing crashes in various processes (similar to an out-of-memory condition caused by kernel overcommit, except that Postgres already has a throttle for that problem) fn1. this is a recent problem in Postgres, because we used to need only 100 GB of free disk space for the import (in r6802/2012-12-12), r6802, 2012-12-12), but now we need 1 _TB_ (10x as much). although it only became an issue on the last import, it may have been a latent problem that just never crossed the disk space limit.