| From: | Michael Lewis <mlewis(at)entrata(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Willy-Bas Loos <willybas(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: temporary data after diskspace error |
| Date: | 2020-01-27 17:59:25 |
| Message-ID: | CAHOFxGqpYO1TQfNJuJVOtUAGkN+B-Y8Js7B1SpicfXZoBSkXiA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
In terms of preventing this happening again, you might consider setting
some reasonable temp_file_limit as default. Alternatively or additionally,
you can set up another volume and direct temp files to use that to avoid
the server crashing if excessive temp files are used in a moment's time.
Then only that one query fails that used too much space.
It always bears mentioning that 9.4 is very old and upgrading is
recommended to at least v11 that has been out for more than a year.
"PostgreSQL 9.4 will stop receiving fixes on February 13, 2020, which is
the next planned cumulative update release."
--https://www.postgresql.org/about/news/1994/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Willy-Bas Loos | 2020-01-27 19:11:13 | Re: temporary data after diskspace error |
| Previous Message | Tanja Savic | 2020-01-27 16:37:18 | RE: PostgresSQL 10 on remote server - Socket is not connected (0x00002749/10057) |