| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephan Knauss <pgsql(at)stephans-server(dot)de> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Debugging leaking memory in Postgresql 13.2/Postgis 3.1 |
| Date: | 2021-04-06 02:11:18 |
| Message-ID: | 940509.1617675078@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Stephan Knauss <pgsql(at)stephans-server(dot)de> writes:
> On 31.03.2021 20:24, Tom Lane wrote:
>> Based on nearby threads, it occurs to me to ask whether you have JIT
>> enabled, and if so whether turning it off helps. There seems to be
>> a known leak of the code fragments generated by that in some cases.
> That's it!
> You mentioned that this seems to be known. Do you have pointers to the
> relevant bug-tracker/thread? I would like to follow up on this.
According to the v14 open issues page [1], there are a couple of older
threads. I just added this one.
regards, tom lane
[1] https://wiki.postgresql.org/wiki/PostgreSQL_14_Open_Items
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2021-04-06 02:17:14 | Re: Primary keys and composite unique keys(basic question) |
| Previous Message | Merlin Moncure | 2021-04-06 02:10:26 | Re: Primary keys and composite unique keys(basic question) |