Re: Memory leak on subquery as scalar operand

Поиск
Список
Период
Сортировка
От Lauri Laanmets
Тема Re: Memory leak on subquery as scalar operand
Дата
Msg-id CAPH-tTyEgUTKJceVKbv-7LxNG4b9DYQRgxzmpUfBDbY7TN4rKw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Memory leak on subquery as scalar operand  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Дерево обсуждения
> Does it still OOM if you do:
> SET jit TO off; ?

Indeed, it doesn't leak if JIT is OFF. Thank you for a workaround hint!

Regards
Lauri



Kontakt Tom Lane (<tgl@sss.pgh.pa.us>) kirjutas kuupäeval T, 1. november 2022 kell 02:44:
David Rowley <dgrowleyml@gmail.com> writes:
> Does it still OOM if you do:
> SET jit TO off; ?

Ah, bingo --- I can reproduce the behavior if I use a JIT-enabled
build.  So this is related to the known problems with leakage of
compiled objects.  It's pretty odd though that it requires two
sub-selects to cause the problem.

                        regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Mike Burgener
Дата:
Сообщение: AW: BUG #17672: Wrong logic of Postgresql Resporitory Naming and mirroring incompatibility
Следующее
От: PG Bug reporting form
Дата:
Сообщение: BUG #17675: pg_dump v15: Comments on constraints missing?