From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Marc Millas <marc.millas@mokadb.com>
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: Re: Death postgres
Date: Sun, 07 May 2023 20:42:00 +0200
Message-ID: <9061fac25866f02c539ae389ace7617d9cfdca74.camel@cybertec.at> (raw)
In-Reply-To: <CADX_1aa=7vXKhsiHQA97yT1+WBcKM4PSfzvxrszC7xqnujZVVQ@mail.gmail.com>
References: <CADX_1aa=7vXKhsiHQA97yT1+WBcKM4PSfzvxrszC7xqnujZVVQ@mail.gmail.com>
On Sat, 2023-05-06 at 03:14 +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.
>
> What are the cases where postgres may grow without caring about temp_file_limit ?
That's too little information for a decent answer.
One obvious answer is: if it is not writing temporary files.
Yours,
Laurenz Albe
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: laurenz.albe@cybertec.at, marc.millas@mokadb.com
Subject: Re: Death postgres
In-Reply-To: <9061fac25866f02c539ae389ace7617d9cfdca74.camel@cybertec.at>
References: <CADX_1aa=7vXKhsiHQA97yT1+WBcKM4PSfzvxrszC7xqnujZVVQ@mail.gmail.com> <9061fac25866f02c539ae389ace7617d9cfdca74.camel@cybertec.at>
* 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