| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Marc Millas <marc(dot)millas(at)mokadb(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 16:11:25 |
| Message-ID: | 00921f8b-b3a1-b67b-c15d-29c0aaef3a7d@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/6/23 05:25, Marc Millas wrote:
>
>
> Le sam. 6 mai 2023 à 06:18, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
> <mailto: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
When you restarted the server where there any warnings shown?
Using psql can you \d <the_table>?
Can you select from any other table in the database?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marc Millas | 2023-05-06 17:13:44 | Re: Death postgres |
| Previous Message | Thomas Guyot | 2023-05-06 14:48:18 | Re: Death postgres |