From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
---|---|
To: | "Michiel Holtkamp" <michiel(dot)holtkamp(at)soundintel(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: How to cope with low disk space |
Date: | 2008-02-14 21:46:58 |
Message-ID: | 1feaea11-43af-4507-87a3-6f7c9bb2f8cc@mm |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Klein Balazs | 2008-02-14 21:49:35 | Re: dynamic crosstab |
Previous Message | Brent Friedman | 2008-02-14 21:18:00 | JDBC and Postgresql 8.0 - cpu usage question |