pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: Death postgres
Date: Sat, 6 May 2023 08:15:04 -0500
Message-ID: <38505370-ecbd-3af3-bcff-4cf2ec4903ff@gmail.com> (raw)
In-Reply-To: <CADX_1aaS211DDt6=OA68yWnzPLatvT1wXe9kVo0j6SVgrr-61w@mail.gmail.com>
References: <CADX_1aa=7vXKhsiHQA97yT1+WBcKM4PSfzvxrszC7xqnujZVVQ@mail.gmail.com>
	<20230506074625.ve4wbvt57cup63li@hjp.at>
	<CADX_1aaS211DDt6=OA68yWnzPLatvT1wXe9kVo0j6SVgrr-61w@mail.gmail.com>

On 5/6/23 07:19, Marc Millas wrote:
>
>
> Le sam. 6 mai 2023 à 09:46, Peter J. Holzer <hjp-pgsql@hjp.at> a écrit :
>
>     On 2023-05-06 03:14:20 +0200, Marc Millas wrote:
>     > 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.
>

"15TB" and "16TB" are pretty low-resolution.  For example, 15.4TB rounds 
*down* to 15TB, while 15.6TB rounds *up* to 16TB, while they are in fact 
only 200GB apart.

Heck, even 15.4TB and 15.6TB are low-resolution.  temp_file_limit may 
actually be working.

>
>     temp_file_limit limits the space a process may use on disk while the OOM
>     killer gets activated when the system runs out of RAM. So these seem to
>     be unrelated.
>
>             hp
>
> Its clear that oom killer is triggered by RAM and temp_file is a disk 
> thing...
> But the sudden growth of disk space usage and RAM did happen exactly at 
> the very same time, with only one user connected, and only one query 
> running...

If your question is about temp_file_limit, don't distract us with OOM issues.

-- 
Born in Arizona, moved to Babylonia.

view thread (26+ messages)  latest in thread

Message-ID: <38505370-ecbd-3af3-bcff-4cf2ec4903ff@gmail.com>
Permalink:  ../38505370-ecbd-3af3-bcff-4cf2ec4903ff@gmail.com/
Also on:    postgresql.org/message-id/38505370-ecbd-3af3-bcff-4cf2ec4903ff@gmail.com

 · 

reply

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: ronljohnsonjr@gmail.com
  Subject: Re: Death postgres
  In-Reply-To: <38505370-ecbd-3af3-bcff-4cf2ec4903ff@gmail.com>
  References: <CADX_1aa=7vXKhsiHQA97yT1+WBcKM4PSfzvxrszC7xqnujZVVQ@mail.gmail.com> <20230506074625.ve4wbvt57cup63li@hjp.at> <CADX_1aaS211DDt6=OA68yWnzPLatvT1wXe9kVo0j6SVgrr-61w@mail.gmail.com> <38505370-ecbd-3af3-bcff-4cf2ec4903ff@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