From: Tom Lane <tgl@sss.pgh.pa.us>
To: kaegoorn48@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq
Date: Wed, 08 Sep 2021 09:35:31 -0400
Message-ID: <3261758.1631108131@sss.pgh.pa.us> (raw)
In-Reply-To: <17184-8819e0faad281a1d@postgresql.org>
References: <17184-8819e0faad281a1d@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, kaegoorn48@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17184: When using openssl, the memory of a static variable is not freed in libpq
In-Reply-To: <3261758.1631108131@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox