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 217D1D1B53A for ; Thu, 4 Sep 2003 03: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 87003-04 for ; Thu, 4 Sep 2003 00:24:50 -0300 (ADT) Received: from news.hub.org (unknown [64.117.224.194]) by svr1.postgresql.org (Postfix) with ESMTP id 532BAD1B94F for ; Thu, 4 Sep 2003 00: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 h843OnDh097774 for ; Thu, 4 Sep 2003 03: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 h843Ok1B097760 for pgsql-performance@postgresql.org; Thu, 4 Sep 2003 03:24:46 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: SELECT's take a long time compared to other DBMS Date: Wed, 03 Sep 2003 23:24:19 -0400 Organization: cbbrowne Computing Inc Lines: 26 Message-ID: References: <1062637505.84923.7.camel@jester> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Rational FORTRAN, linux) Cancel-Lock: sha1:WA5ip0o6AX0QZkWBvQgeyHH+AEE= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/47 X-Sequence-Number: 3413 In the last exciting episode, "Relaxin" wrote: > All queries were ran on the SERVER for all of the databases I tested. Queries obviously run "on the server." That's kind of the point of the database system being a "client/server" system. The question is what client program(s) you used to process the result sets. I'd be surprised to see any client process 100K records in any meaningful way in much less than 30 seconds. Rendering that much data into a console will take some time. Drawing it into cells on a GUI window will take a lot more time. Supposing you were using a graphical client, it would be unsurprising for it to have submitted something equivalent to "limit 30 rows" (or whatever you can display on screen), and defer further processing 'til later. If that were the case, then 26s to process the whole thing would be a lot more efficient than 5-6s to process a mere 30 rows... > This is all resulting data for all of the databases that I tested. You seem to have omitted "all resulting data." -- If this was helpful, rate me http://www.ntlug.org/~cbbrowne/sap.html "Women who seek to be equal to men lack ambition. " -- Timothy Leary