Re: BUG #17793: Query with large number of joins crashes PostgreSQL

Поиск
Список
Период
Сортировка
Искать
От
Francisco Olarte
Тема
Re: BUG #17793: Query with large number of joins crashes PostgreSQL
Дата
Msg-id
CA+bJJbzUKMzkYjGxbQpaRo_evErh+XsnMUUJC+q+edGCM3un8A@mail.gmail.com
Ответ на
Список
Дерево обсуждения
BUG #17793: Query with large number of joins crashes PostgreSQL PG Bug reporting form <noreply@postgresql.org>
Re: BUG #17793: Query with large number of joins crashes PostgreSQL Francisco Olarte <folarte@peoplecall.com>
Re: BUG #17793: Query with large number of joins crashes PostgreSQL Tom Lane <tgl@sss.pgh.pa.us>
Re: BUG #17793: Query with large number of joins crashes PostgreSQL Joe Conway <mail@joeconway.com>
Re: BUG #17793: Query with large number of joins crashes PostgreSQL Stephen Frost <sfrost@snowman.net>
Re: BUG #17793: Query with large number of joins crashes PostgreSQL Francisco Olarte <folarte@peoplecall.com>
Tom:

On Tue, 14 Feb 2023 at 11:29, PG Bug reporting form
 wrote:
...
> These are the server logs when the crash happens:
> 2023-02-14 09:17:31.440 UTC [1] LOG:  server process (PID 35) was terminated
> by signal 9: Killed
...
> It looks like the OS is killing the process due to running OOM, which is not
> very surprising when looking at the query. Is this expected, or should PG
> have guards in place to prevent this from happening?

When you run postgres in an environment where someone ( OOM killer )
can K9 it, protection is hard. IIRC OOM can kill you because ANOTHER
process touches memory, among other things.

( I do run DBs in machines w/ overcommit disabled, this prevents it
from happening, but it is not Pg who prevents it ).

FOS.


В списке pgsql-bugs по дате отправления
От: Alvaro Herrera
Дата:
От: Alexander Lakhin
Дата:
FAQ