Re: NO DATA error message in Frontend when querying large datasets
От | Jens Kapp |
---|---|
Тема | Re: NO DATA error message in Frontend when querying large datasets |
Дата | |
Msg-id | 4D40A29D.40806@gmx.de обсуждение исходный текст |
Ответ на | Re: NO DATA error message in Frontend when querying large datasets (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: NO DATA error message in Frontend when querying large datasets
|
Список | pgsql-bugs |
hi tom, thanks a lot for your response. the frontend we are trying to use is a well known and spread laboratory system. our consultant has experience with other databases (oracle, sql) that are a lot bigger - with no problems. however i'm wondering that postgres is not working with the lab system AND other common DB frontends using ODBC. i guess there is no setting for: "use cursor instead" ? thanks jk Am 26.01.2011 20:16, schrieb Tom Lane: > Jens Kapp<jens-kapp@gmx.de> writes: >> we have postgres 9.0.1 installed on a windows 2008 r2 server. >> odbc is psqlodbc_09_00_0200.zip. >> the database has currently a size of around 800mb. >> it works as expected on the server (pgadmin), but if we try queries for >> large datasets we get the error message: "No data" from our frontend or >> any other database tools thats using the ODBC connection (e.g. anysql >> maestro). >> 1.) first we will make a query with only 1 column. we get data. >> 2.) then make the same query but with all columns: it says "No data". >> 3.) Afterwards we try the query from before again, but still getting "No >> data". > I wonder whether you're running out of memory for the query result in > the client side, and this "no data" is coming from some code that is not > written to cope with that happening. > > You might consider using a cursor to fetch large results a few rows at a > time. > > regards, tom lane >
В списке pgsql-bugs по дате отправления: