Michiel Holtkamp wrote:
Running low on disk space can also happen when something goes wrong
with
the recording trigger (this can be a hardware fault). In both cases,
we
don't want to store even more data, but we will want to make a
selection
based on age (newer data is more important).
Did you think about testing pg_relation_size('pg_largeobject') against
a fixed threshold before allocating new large objects?
If it's higher than the threshold, you could either stop importing new
data, or lo_unlink-ing older entries and immediately issuing a plain
vacuum before continuing.
--
Daniel
PostgreSQL-powered mail user agent and storage:
http://www.manitou-mail.org
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
