Received: from localhost (maia-3.hub.org [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id B5F7A9FB3F3 for ; Fri, 23 Feb 2007 13:44:40 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-new, port 10024) with ESMTP id 52071-08 for ; Fri, 23 Feb 2007 13:44:35 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from vsmtp21.tin.it (vsmtp21.tin.it [212.216.176.109]) by postgresql.org (Postfix) with ESMTP id BF1BF9FB407 for ; Fri, 23 Feb 2007 13:44:36 -0400 (AST) Received: from pswm13.cp.tin.it (192.168.70.37) by vsmtp21.tin.it (7.2.072.1) id 45D4389D0016A257 for pgsql-performance@postgresql.org; Fri, 23 Feb 2007 18:44:27 +0100 Message-ID: <110efb42d61.msmbarabino@virgilio.it> Date: Fri, 23 Feb 2007 18:44:27 +0100 (GMT+01:00) From: "msmbarabino@virgilio.it" Reply-To: "msmbarabino@virgilio.it" To: pgsql-performance@postgresql.org Subject: Re: Very slow bytea data extraction Mime-Version: 1.0 Content-Type: text/plain;charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: 151.64.149.238 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.231 tagged_above=0 required=5 tests=AWL, BAYES_60, DNS_FROM_RFC_ABUSE, DNS_FROM_RFC_POST X-Spam-Level: ** X-Archive-Number: 200702/249 X-Sequence-Number: 23303 >If you look at the "actual time" it's completing very quickly indeed. So >- it must be something to do with either: >1. Fetching/formatting the data >>2. Transferring the data to the client. I do agree. >What happens if you only select half the rows? Does the time to run the >select halve? Yes, it does. Using pgAdmin, the time to get all 36 rows is about 67500ms while it's 24235ms to get only 18 rows. Massimo