[unixODBC-support] Problem in using cursor to fetchmillionsofrows

Eric Sharkey sharkey at netrics.com
Thu Apr 7 17:26:47 BST 2005

> 166M of memory is used.
> That's hurt and the memory is never released.

Many implementations of malloc()/free() don't release memory to the OS
even when freed, because they assume the application is likely to
want to malloc() it it back very soon.  This is not a bug.

If you run the same statement twice, does the memory usage stay fixed
at 166, or does it grow to 332?


More information about the unixODBC-support mailing list