X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8B2EA53B20 for ; Fri, 22 Apr 2005 06:47:36 -0300 (ADT) 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 68904-07 for ; Fri, 22 Apr 2005 09:47:34 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.177]) by svr1.postgresql.org (Postfix) with ESMTP id B4E2C53B0C for ; Fri, 22 Apr 2005 06:47:32 -0300 (ADT) Received: from p50818B9C.dip0.t-ipconnect.de[80.129.139.156] (helo=pse.dyndns.org) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0MKxQS-1DOul310z7-0000NS; Fri, 22 Apr 2005 11:47:33 +0200 Received: from pse1 ([192.168.0.3]) by pse.dyndns.org with esmtp (Exim 4.44) id 1DOul2-0007ci-1Z; Fri, 22 Apr 2005 11:47:32 +0200 Message-ID: <4268C833.8080302@pse-consulting.de> Date: Fri, 22 Apr 2005 09:47: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: pgsql-performance@postgresql.org Subject: Re: Joel's Performance Issues WAS : Opteron vs Xeon 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, hits=0.03 tagged_above=0 required=5 tests=AWL, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200504/610 X-Sequence-Number: 12007 Dave Page wrote: > > > >>-----Original Message----- >>From: pgsql-performance-owner@postgresql.org >>[mailto:pgsql-performance-owner@postgresql.org] On Behalf Of >>Andreas Pflug >>Sent: 21 April 2005 14:06 >>To: Joel Fradkin >>Cc: 'John A Meinel'; josh@agliodbs.com; >>pgsql-performance@postgresql.org >>Subject: Re: [PERFORM] Joel's Performance Issues WAS : Opteron vs Xeon >> >>Beware! >> From the data, I can see that you're probably using pgAdmin3. >>The time to execute your query including transfer of all data to the >>client is 17s in this example, while displaying it (i.e. pure GUI and >>memory alloc stuff) takes 72s. Execute to a file to avoid this. > > > Perhaps we should add a guruhint there for longer runtimes? Yup, easily done as replacement for the "max rows exceeded" message box. Added to TODO.txt. Regards, Andreas