Re: BUG #6234: Memory leak from PQexec

From: Vikas Mehta <Vikas(dot)Mehta(at)roguewave(dot)com>
To: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #6234: Memory leak from PQexec
Date: 2011-10-03 18:13:27
Message-ID: 53D52D02E87FA04A948D9A74A7AE617C0B47D8FD54@Eagle.Blue.Roguewave.Com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thanks. I found posts on SSL leak reported by purify. However, I couldn't find any information on the memory leak from PQrequestCancel. Is it a known issue?

-----Original Message-----
From: Craig Ringer [mailto:ringerc(at)ringerc(dot)id(dot)au]
Sent: Friday, September 30, 2011 12:02 AM
To: Vikas Mehta
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #6234: Memory leak from PQexec

On 29/09/2011 6:22 AM, Vikas Mehta wrote:
> The following bug has been logged online:
>
> Bug reference: 6234
> Logged by: Vikas Mehta
> Email address: mehta(at)roguewave(dot)com
> PostgreSQL version: 8.4.8
> Operating system: Windows
> Description: Memory leak from PQexec
> Details:
>
> Purify shows 448 bytes of memory leaks with PQexec:
>
> [W] Summary of all memory leaks... {448 bytes, 11 blocks}
> [W] MLK: Memory leak of 128 bytes from 1 block allocated in
> ERR_load_SSL_strings [SSLEAY32.DLL]
>
It's not a leak, and it's not a bug. Please search the pgsql-general archives for "valgrind" or "SSL_config".

--
Craig Ringer

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2011-10-03 18:13:46 Re: [v9.2] make_greater_string() does not return a string in some cases
Previous Message Tom Lane 2011-10-03 16:19:41 Re: bug in dependency - there is possibility to break a system catalog