It seems that when you perform a large query against the postgresql ODBC driver
it sucks it all in to memory. If the query returns more data than you have
memory, it fails. To change this behavior, you set UseDeclareFetch to yes.
It seems that in QR_read_tuple, a buffer is allocated but never freed. Has
anyone ever seen this before?
I traced this in the unixODBC Postgre7.1 driver by replacing free/malloc with
debug versions, and it looks like the PostgreSQL version has the same issue.
Could this buffer be freed else where?