Task #883
Updated by Aaron Marcuse-Kubitza about 10 years ago
* running into the disk space hard limit causes crashes, and should be avoided if at all possible * Postgres itself does not have a mechanism to do this[1], but our scripts could do this instead * @lib/sql.py@ should trap @"OperationalError: could not extend file "...": No space left on device"@ and handle it by pausing until the disk space goes back down, and then retrying the last SQL command ** the last SQL command does not need to be idempotent, because the error means that it was rolled back fn1. the @temp_file_limit@ config param seems to be intended to do this, but "throws an error":http://www.postgresql.org/docs/9.3/static/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-DISK error":http://postgresql.1045698.n5.nabble.com/Documentation-for-temp-file-limit-td5687245.html instead of handling the problem by pausing (self-throttling)