| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Timo Sirainen <timo(at)sirainen(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: libpq leaks memory for SSL connections |
| Date: | 2021-10-01 19:46:39 |
| Message-ID: | 3632212.1633117599@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Timo Sirainen <timo(at)sirainen(dot)com> writes:
> I noticed with valgrind how libpq is leaking memory:
> at 0x483577F: malloc (in /usr/lib/x86_64-linux-gnu/valgrind/vgpreload_memcheck-amd64-linux.so)
> by 0x5F645C8: CRYPTO_zalloc (in /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1)
> by 0x5E94EEF: BIO_meth_new (in /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1)
> by 0x65181EB: ??? (in /usr/lib/x86_64-linux-gnu/libpq.so.5.11)
> by 0x651950C: ??? (in /usr/lib/x86_64-linux-gnu/libpq.so.5.11)
> by 0x650140F: PQconnectPoll (in /usr/lib/x86_64-linux-gnu/libpq.so.5.11)
I see no leak here. The struct is allocated once and kept for possible
re-use by future connections. valgrind concurs, saying it's "still
reachable".
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Timo Sirainen | 2021-10-01 20:06:36 | Re: libpq leaks memory for SSL connections |
| Previous Message | Jeremy Schneider | 2021-10-01 19:37:31 | Re: BUG #16583: merge join on tables with different DB collation behind postgres_fdw fails |