[unixODBC-support] Memory leak in SQLFetch?

Nick Gorham nick.gorham at easysoft.com
Tue Dec 14 16:47:32 GMT 2004


Saunders, Steve wrote:

>I will see what I can do to get you a trace, will probably just take
>Cameron's code and use it to build a program against our database.  
>
>I have not set any options related to cursor myself, vanilla unixODBC and
>our interface doesn't use cursors, so whatever the default is, forward only
>I assume, we would be using.  
>
>The only difference with our application vs. Cameron's test is that we don't
>fetch a large number of rows all at once, instead we do a lot of selects and
>fetches on a very small database repeatedly in a LoadRunner based load test
>for 100-200 concurrent users for an extended period of time (hours) and this
>is where we see the leak.  To reproduce our leak I can just change his code
>to do lots of interations to DB2 and then to MyODBC. 
>
>Could you tell us to the tracing option you want turned on?  
>  
>

In your odbcinst.ini file add a [ODBC] section

[ODBC]
Trace = Yes
TraceFile = /tmp/sql.log

-- 
Nick




More information about the unixODBC-support mailing list