Postgres Pro
Downloads
Home   >   mailing lists

Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq - Mailing list pgsql-bugs

From Alexander Dzuba
Subject Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq
Date
Msg-id CAHqoriwH5uurwC1tUqUCv=M-wQohHEw5bCEJaGQDkb3-1ntugQ@mail.gmail.com
Whole thread Raw
In response to Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Tree view
I know that this is not the real leak, but memcheck analysis shows that the memory was not released. Because of this, CI tests fail and deploy is blocked.

ср, 8 сент. 2021 г. в 16:35, Tom Lane <tgl@sss.pgh.pa.us>:
PG Bug reporting form <noreply@postgresql.org> writes:
> Valgrind shows static variable memory is not freed when using openssl
> libpq/fe-secure-openssl.c:1571
> static BIO_METHOD *my_bio_methods;

> Please add a method that will free memory after use

Why?  It's not leaked: the struct is still available for use
in future connection attempts.

                        regards, tom lane

pgsql-bugs by date:

Previous
From: Semab Tariq
Date:
Subject: Re: Technical Support
Next
From: Tomas Barton
Date:
Subject: Segmentation fault on postgresql 13.4, 12.8 with function call in a cursor