| From: | Lauri Laanmets <pcspets(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Memory leak on subquery as scalar operand |
| Date: | 2022-11-02 08:26:49 |
| Message-ID: | CAPH-tTyEgUTKJceVKbv-7LxNG4b9DYQRgxzmpUfBDbY7TN4rKw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)sss(dot)pgh(dot)pa(dot)us>) kirjutas kuupäeval T, 1. november
2022 kell 02:44:
> David Rowley <dgrowleyml(at)gmail(dot)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
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-11-02 08:40:40 | BUG #17675: pg_dump v15: Comments on constraints missing? |
| Previous Message | Mike Burgener | 2022-11-02 08:00:49 | AW: BUG #17672: Wrong logic of Postgresql Resporitory Naming and mirroring incompatibility |