| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Euler Taveira <euler(dot)taveira(at)2ndquadrant(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, murali(dot)natti(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #16427: pgsql_tmp - temp files not released |
| Date: | 2020-05-11 06:10:34 |
| Message-ID: | 20200511061034.GB88791@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sun, May 10, 2020 at 10:48:58AM -0300, Euler Taveira wrote:
> I wonder if a GUC (cleanup_temp_files_after_crash) is useful for an
> environment that has storage restrictions. This is the second time this
> month that I stumbled on this issue. Of course, I don't expect a postgres
> crash once a while but we know that, due to extensibility, some extensions
> could crash and the only workaround to this issue is to restart service
> (which means a human intervention and an additional downtime).
Sounds like a fair concern to me. It is annoying to have to do some
manual intervention for some environments under disk pressure.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2020-05-11 10:48:39 | BUG #16429: PgAdmin4 is installed but not able to connect to the Azure Database for Postgres |
| Previous Message | Fahar Abbas | 2020-05-11 05:37:41 | Re: BUG #16420: problem running into post install step while installation. |