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 09310D1BA71 for ; Thu, 4 Sep 2003 08:25:01 +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 15290-01 for ; Thu, 4 Sep 2003 05:24:52 -0300 (ADT) Received: from news.hub.org (unknown [64.117.224.194]) by svr1.postgresql.org (Postfix) with ESMTP id 651CDD1B8E9 for ; Thu, 4 Sep 2003 05:24:50 -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 h848OoDf062957 for ; Thu, 4 Sep 2003 08:24:50 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id h848GWA7060859 for pgsql-performance@postgresql.org; Thu, 4 Sep 2003 08:16:32 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 01:16:47 -0700 Organization: Hub.Org Networking Services Lines: 35 Message-ID: References: <3F573E8B.31916.A1063F8@localhost> 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/56 X-Sequence-Number: 3422 All rows are required. ""Shridhar Daithankar"" wrote in message news:3F573E8B.31916.A1063F8@localhost... > On 4 Sep 2003 at 0:48, Relaxin wrote: > > 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? > > You can use a cursor and get only required rows. > > > Bye > Shridhar > > -- > Nick the Greek's Law of Life: All things considered, life is 9 to 5 against. > > > ---------------------------(end of broadcast)--------------------------- > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org >