| From: | Thomas Guyot <tguyot(at)gmail(dot)com> |
|---|---|
| To: | Marc Millas <marc(dot)millas(at)mokadb(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Death postgres |
| Date: | 2023-05-06 14:48:18 |
| Message-ID: | f79f99a6-7a60-37a5-e9ca-b173316c2398@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2023-05-05 21:14, Marc Millas wrote:
> Hi,
>
> postgres 14.2 on Linux redhat
>
> temp_file_limit set around 210 GB.
>
> a select request with 2 left join have crashed the server (oom killer)
> after the postgres disk occupation did grow from 15TB to 16 TB.
>
> What are the cases where postgres may grow without caring about
> temp_file_limit ?
>
> thanks,
>
Some OSes like IIRC RHEL9 now default to tmpfs for /tmp - if your temp
files are written in a tmpfs then it may may very well trigger the OOM
because of the temp file used up all RAM.
Check the filesystem type of your temp file's location.
--
Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2023-05-06 16:11:25 | Re: Death postgres |
| Previous Message | Ron | 2023-05-06 14:19:24 | Re: Death postgres |