From: Thomas Guyot <tguyot@gmail.com>
To: Marc Millas <marc.millas@mokadb.com>
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Death postgres
Date: Sat, 6 May 2023 10:48:18 -0400
Message-ID: <f79f99a6-7a60-37a5-e9ca-b173316c2398@gmail.com> (raw)
In-Reply-To: <CADX_1aa=7vXKhsiHQA97yT1+WBcKM4PSfzvxrszC7xqnujZVVQ@mail.gmail.com>
References: <CADX_1aa=7vXKhsiHQA97yT1+WBcKM4PSfzvxrszC7xqnujZVVQ@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tguyot@gmail.com, marc.millas@mokadb.com
Subject: Re: Death postgres
In-Reply-To: <f79f99a6-7a60-37a5-e9ca-b173316c2398@gmail.com>
References: <CADX_1aa=7vXKhsiHQA97yT1+WBcKM4PSfzvxrszC7xqnujZVVQ@mail.gmail.com> <f79f99a6-7a60-37a5-e9ca-b173316c2398@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox