From: Terry Lee Tucker <terry@esc1.com>
To: Postgres-Interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: Memory Usage and libpq
Date: Tue, 4 Apr 2006 13:23:19 -0500
Message-ID: <200604041423.19119.terry@esc1.com> (raw)
In-Reply-To: <C05813BC.27D74%hierophant@pcisys.net>
References: <C05813BC.27D74%hierophant@pcisys.net>
On Tuesday 04 April 2006 03:14 pm, Keary Suska saith:
> I am investigating a memory usage issue and I noticed something with libpq.
> It appears that libpq doesn't actually free memory allocated to store
> results, even after PQclear() is called. In a debug program I can inspect
> the buffer so I know it exists. I haven't verified whether the buffer is
> resized with subsequent calls, but when dealing with large result sets it
> creates a significant memory overhead.
>
> Am I on to something here or do I need to keep looking? If so, is there any
> way that I can force libpq to free or in some way drastically reduce this
> biffer?
>
> Thanks,
>
> Keary Suska
> (719) 473-6431
> (719) 440-9952 (cell)
>
Keary,
I may be wrong about this, but just because you can access the memory after
the call to PQclear, doesn't mean that the memory wasn't freed; it just means
it hasn't been reused yet. The address still exists and freeing the memory
doesn't "clear" it out.
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-interfaces@postgresql.org
Cc: terry@esc1.com
Subject: Re: Memory Usage and libpq
In-Reply-To: <200604041423.19119.terry@esc1.com>
* 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