Re: NO DATA error message in Frontend when querying large datasets - Mailing list pgsql-bugs

From Korry Douglas
Subject Re: NO DATA error message in Frontend when querying large datasets
Date
Msg-id 4D7DB1B1-7D86-4B72-96A0-81E6DA675E58@enterprisedb.com
Whole thread Raw
In response to Re: NO DATA error message in Frontend when querying large datasets  (Jens Kapp <jens-kapp@gmx.de>)
Responses Re: NO DATA error message in Frontend when querying large datasets
List pgsql-bugs
> 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
otherdatabases (oracle, sql) that are a lot bigger - with no problems. however i'm wondering that postgres is not
workingwith the lab system AND other common DB frontends using ODBC. i guess there is no setting for: "use cursor
instead"? 

"Use Declare/Fetch" may be the setting that you want.  That's a setting in the ODBC driver and you should be able to
changethat setting through the Windows ODBC Administrator. 

You may also want to change the "Server side prepare" setting.  (Be sure to change one setting at a time and test your
applicationbetween changes). 

                    -- Korry

>
> 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
>>
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

-----------------------------------------------------------------------
Korry Douglas
Senior Database Dude
EnterpriseDB Corporation
The Enterprise Postgres Company

Phone: (804)241-4301
Mobile: (620) EDB-NERD



pgsql-bugs by date:

Previous
From: Jens Kapp
Date:
Subject: Re: NO DATA error message in Frontend when querying large datasets
Next
From: Josh Berkus
Date:
Subject: Re: Multicolun index creation never completes on 9.0.1/solaris