Re: libpq3 + ssl memory leak

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Olaf Hartmann <hao(at)telemedsys(dot)de>, pgsql-bugs(at)postgresql(dot)org, Sean Chittenden <sean(at)chittenden(dot)org>
Subject: Re: libpq3 + ssl memory leak
Date: 2003-12-18 22:51:12
Message-ID: 4865.1071787872@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Neil Conway <neilc(at)samurai(dot)com> 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.

Applied to 7.4 and HEAD.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PostgreSQL Bugs List 2003-12-18 23:01:35 BUG #1015: Got a signal 11 while trying to create a temp table
Previous Message Lewis Foti 2003-12-18 19:17:12 Jdbc connection pooling and PG 7.4 consistently fails