X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 85685D1B8E9 for ; Thu, 4 Sep 2003 07:55:09 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 08914-10 for ; Thu, 4 Sep 2003 04:55:00 -0300 (ADT) Received: from news.hub.org (unknown [64.117.224.194]) by svr1.postgresql.org (Postfix) with ESMTP id 8B45FD1B8BC for ; Thu, 4 Sep 2003 04:54:58 -0300 (ADT) Received: from news.hub.org (host-64-117-224-194.altec1.com [64.117.224.194] (may be forged)) by news.hub.org (8.12.9/8.12.9) with ESMTP id h847soDh054310 for ; Thu, 4 Sep 2003 07:54:58 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id h847mRSV052921 for pgsql-performance@postgresql.org; Thu, 4 Sep 2003 07:48:27 GMT From: "Relaxin" X-Newsgroups: comp.databases.postgresql.performance Subject: Re: SELECT's take a long time compared to other DBMS Date: Thu, 4 Sep 2003 00:48:42 -0700 Organization: Hub.Org Networking Services Lines: 23 Message-ID: References: <3F569012.3090209@oasis.net.au> X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/54 X-Sequence-Number: 3420 > Can you tell us what you were *actually* doing? Somehow it sounds as > though the other databases were throwing away the data whereas > PostgreSQL was returning it all "kawhump!" in one batch. All of the databases that I tested the query against gave me immediate access to ANY row of the resultset once the data had been returned. Ex. If I'm currently at the first row and then wanted to goto the 100,000 row, I would be there immediately, and if I wanted to then goto the 5 row...same thing, I have the record immediately! The other databases I tested against stored the entire resultset on the Server, I'm not sure what PG does...It seems that brings the entire resultset client side. If that is the case, how can I have PG store the resultset on the Server AND still allow me immediate access to ANY row in the resultset? > What programs were you using to submit the queries? I used the same program for all of the database. I was using ODBC as connectivity.