From: | Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> |
---|---|
To: | Laurent Chouinard <laurent(dot)chouinard(at)sem(dot)ca> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: C# w/ ODBC, 2.1 million list select gives empty DataSet |
Date: | 2010-01-13 04:41:47 |
Message-ID: | 4B4D4F0B.4000802@postnewspapers.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
On 12/01/2010 7:34 AM, Laurent Chouinard wrote:
> With the new drivers, it still climbs to 700MB or so (makes sense, 2
> million rows is quite a bit), and then after the "0 rows" returned,
> memory is cleared immediately. Makes sense as well, OBDC doesn't carry
> data anymore, dataset is almost null, garbage collector is having a
> field day.
I don't use ODBC much personally and don't work on the driver - but it
sounds to me a lot like the new driver may be running out of memory too,
but is eating the failure (or reporting it via some side-channel) rather
than throwing. If it is, that'd be pretty bad behavior in my personal
opinion, but then I don't know ODBC well. Someone who does may be able
to shed some more light.
My suggestion, though: Even if you resolve this now, as things continue
to grow you're still going to have OOM issues. Perhaps it'd be a good
idea to use a cursor for this?
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2010-01-13 05:35:34 | Re: C# w/ ODBC, 2.1 million list select gives empty DataSet |
Previous Message | the6campbells | 2010-01-12 23:48:56 | unicode vs non-unicode ODBC driver |