This is a discussion on .NET ODBC Provider w/ PostgreSQL 8.1.4 on Win XP SP2 within the pgsql Interfaces odbc forums, part of the PostgreSQL category; --> Hi All, I'm a little unsure quite where to post this, so suggestions for other groups are most welcome. ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi All, I'm a little unsure quite where to post this, so suggestions for other groups are most welcome. I'm hoping though, it's a general ODBC interface query (not something the .NET ODBC does that's causing this; although, if someone knows otherwise, please let me know). I'm running a "SELECT * from MyTable", which happens to contain 9 million rows, which equates to about 3gb worth of data. Using any ODBC connection to PostgreSQL seems to swallow 3gb of RAM, before returning results. Basically, I just want to retrieve a-row-at-a-time from a table; can I do this via ODBC (possibly a configuration option), or should I use another interface?; do I need to implement it server side via cursors? Am I completely barking up the wrong tree? Regards, Jon. |
| Thread Tools | |
| Display Modes | |
|
|