Re: Postgres resources not released after call PQclear

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Souheila Hechaichi <Souheila(dot)Hechaichi(at)asg(dot)com>
Cc: "'pgsql-bugs(at)postgresql(dot)org'" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Postgres resources not released after call PQclear
Date: 2014-04-07 16:34:36
Message-ID: 21547.1396888476@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Souheila Hechaichi <Souheila(dot)Hechaichi(at)asg(dot)com> writes:
> I observe that when the row number about a SELECT SQL request is equal to zero, the function PQclear does not release the allocated resources and a memory leak are detected into my application.

This claim is, to be frank, pretty astonishing. Can you produce a
self-contained test case to demonstrate that there's a leak?

> And I call the function _CrtDumpMemoryLeaks() at the end of my application, to display all the memory leak.

I doubt that that proves anything at all. Such a function can't tell
whether libpq is holding onto memory internally. If you see growth in
memory usage over repeated query cycles, then it would be interesting.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message David Johnston 2014-04-07 17:43:17 Re: BUG #9896: Bug in FULL OUTER JOIN
Previous Message Souheila Hechaichi 2014-04-07 16:03:42 Postgres resources not released after call PQclear