X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4A39CD78C4 for ; Mon, 7 Nov 2005 13:45:40 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 83267-10 for ; Mon, 7 Nov 2005 17:45:38 +0000 (GMT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by svr1.postgresql.org (Postfix) with ESMTP id 9BCA6D72B6 for ; Mon, 7 Nov 2005 13:45:37 -0400 (AST) Received: from p548F3CD6.dip0.t-ipconnect.de [84.143.60.214] (helo=pse.dyndns.org) by mrelayeu.kundenserver.de (node=mrelayeu2) with ESMTP (Nemesis), id 0MKwtQ-1EZB3l2Ckn-0007fY; Mon, 07 Nov 2005 18:45:33 +0100 Received: from pse1 ([192.168.0.3]) by pse.dyndns.org with esmtp (Exim 4.44) id 1EZB3j-0002Uf-MT; Mon, 07 Nov 2005 18:45:31 +0100 Message-ID: <436F92BB.7040807@pse-consulting.de> Date: Mon, 07 Nov 2005 17:45:31 +0000 From: Andreas Pflug User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dave Page Cc: Joost Kraaijeveld , Tom Lane , Pgsql-Performance Subject: Re: Performance PG 8.0 on dual opteron / 4GB / 3ware References: In-Reply-To: X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: kundenserver.de abuse@kundenserver.de login:0ce7ee5c3478b8d72edd8e05ccd40b70 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.125 required=5 tests=[AWL=0.125] X-Spam-Score: 0.125 X-Spam-Level: X-Archive-Number: 200511/121 X-Sequence-Number: 15378 Dave Page wrote: >> >> >>Now *I* am confused. What does PgAdmin do more than giving >>the query to >>the database? > > > Nothing - it just uses libpq's pqexec function. The speed issue in > pgAdmin is rendering the results in the grid which can be slow on some > OS's due to inefficiencies in some grid controls with large data sets. > That's why we give 2 times - the first is the query runtime on the > server, the second is data retrieval and rendering (iirc, it's been a > while). yrnc. Query runtime includes data transfer to the client, i.e. until libpq returns the set, second time is retrieving data from libpq and rendering. Regards,