Tom Lane wrote:
> Neil Conway <[EMAIL PROTECTED]> writes:
> > Okay, I've attached a patch that fixes the problem for me. The problem
> > turned out to be pretty simple: the PostgreSQL code (both backend and
> > frontend SSL support) was calling SSL_get_peer_certificate() without
> > properly free'i
Neil Conway <[EMAIL PROTECTED]> writes:
> Okay, I've attached a patch that fixes the problem for me. The problem
> turned out to be pretty simple: the PostgreSQL code (both backend and
> frontend SSL support) was calling SSL_get_peer_certificate() without
> properly free'ing its return value.
Appl
Neil Conway <[EMAIL PROTECTED]> writes:
> This fix needs to be in 7.4.1, so if anyone wants to review this
> patch, that would be great.
Looks reasonable from here, but confirmation from the complainant that
it fixes his problem would be real good ...
> P.S. I added an assertion in the backend co
Okay, I've attached a patch that fixes the problem for me. The problem
turned out to be pretty simple: the PostgreSQL code (both backend and
frontend SSL support) was calling SSL_get_peer_certificate() without
properly free'ing its return value.
I haven't actually confirmed the backend memory leak
Neil Conway <[EMAIL PROTECTED]> writes:
> I can verify this locally. Unfortunately, my copy of valgrind doesn't
> seem to be picking up the debugging symbols for OpenSSL
Ok, some progress. I installed a development snapshot of OpenSSL, and
confirmed that the problem still occurs there. The full va
Olaf Hartmann <[EMAIL PROTECTED]> writes:
> We expirience a memory leak with every connection when using an SSL
> encrypted TCP connection to connect a postgres database.
I can verify this locally. Unfortunately, my copy of valgrind doesn't
seem to be picking up the debugging symbols for OpenSSL,
POSTGRESQL BUG REPORT TEMPLATE
Your name : Olaf Hartmann
Your email address : [EMAIL PROTECTED]
System
