| From: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | "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:25:31 |
| Message-ID: | CADX_1aY1KtOYZaOB8F4KdHgDh7E1bbMkmNciOHc8xt2Y3=hYWg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Le sam. 6 mai 2023 à 06:18, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> a
écrit :
> On 5/5/23 18: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.
>
> The result of EXPLAIN <the query> would be helpful.
> Sure!
>
But. One of the table looks "inaccessible" since.
Ie. Even explain select * from the_table didnt answer and must be killed by
control c
> >
> > What are the cases where postgres may grow without caring about
> > temp_file_limit ?
> >
> > thanks,
> >
> >
> >
> >
> > Marc MILLAS
> > Senior Architect
> > +33607850334
> > www.mokadb.com <http://www.mokadb.com>
> >
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Evgeny Morozov | 2023-05-06 12:29:36 | Re: "PANIC: could not open critical system index 2662" - twice |
| Previous Message | Marc Millas | 2023-05-06 12:19:49 | Re: Death postgres |