| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Orphan files filling root partition after crash |
| Date: | 2024-03-04 04:07:34 |
| Message-ID: | 11bd4c047eb93a208a76a93f2601f231c2ed437e.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2024-03-04 at 00:04 +0100, Peter J. Holzer wrote:
> On 2024-02-28 20:30:35 +0100, Dimitrios Apostolou wrote:
> > On Wed, 28 Feb 2024, Laurenz Albe wrote:
> > > On Wed, 2024-02-28 at 12:16 +0100, Dimitrios Apostolou wrote:
> > > > So what is the moral of the story? How to guard against this?
> > >
> > > Monitor disk usage ...
> >
> > It happened *fast*. And it was quite a big suprise coming
> > from "just" a disk-full situation.
>
> Been there.
>
> To prevent this in the future I wrote a small script to monitor disk
> space (on multiple hosts and multiple file systems) every few seconds
> and invoke another script (which just terminates all database
> connections - a bit drastic but effective) if free space runs low:
> https://github.com/hjp/platzangst
And I maintain that "temp_file_limit" is the best solution.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-03-04 04:12:09 | Re: When manual analyze is needed |
| Previous Message | Peter J. Holzer | 2024-03-03 23:04:28 | Re: Orphan files filling root partition after crash |