| From: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
|---|---|
| To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Death postgres |
| Date: | 2023-05-06 12:19:49 |
| Message-ID: | CADX_1aaS211DDt6=OA68yWnzPLatvT1wXe9kVo0j6SVgrr-61w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le sam. 6 mai 2023 à 09:46, Peter J. Holzer <hjp-pgsql(at)hjp(dot)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.
>
> 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...
>
> --
> _ | Peter J. Holzer | Story must make more sense than reality.
> |_|_) | |
> | | | hjp(at)hjp(dot)at | -- Charles Stross, "Creative writing
> __/ | http://www.hjp.at/ | challenge!"
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Millas | 2023-05-06 12:25:31 | Re: Death postgres |
| Previous Message | Thomas Munro | 2023-05-06 10:34:26 | Re: "PANIC: could not open critical system index 2662" - twice |