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 52F993CC0D8 for ; Fri, 17 Dec 2004 21:57:33 +0000 (GMT) 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 81815-08 for ; Fri, 17 Dec 2004 21:57:21 +0000 (GMT) Received: from cassarossa.samfundet.no (cassarossa.samfundet.no [129.241.93.19]) by svr1.postgresql.org (Postfix) with ESMTP id E4C083B4CC4 for ; Fri, 17 Dec 2004 21:57:20 +0000 (GMT) Received: from [2001:700:300:dc03:20e:cff:fe36:a766] (helo=trofast.sesse.net) by cassarossa.samfundet.no with esmtp (Exim 4.34) id 1CfQ5d-00032h-Tr for pgsql-performance@postgresql.org; Fri, 17 Dec 2004 22:57:18 +0100 Received: from sesse by trofast.sesse.net with local (Exim 3.36 #1 (Debian)) id 1CfQ5L-0002Yl-00 for ; Fri, 17 Dec 2004 22:56:27 +0100 Date: Fri, 17 Dec 2004 22:56:27 +0100 From: "Steinar H. Gunderson" To: pgsql-performance@postgresql.org Subject: Re: Seqscan rather than Index Message-ID: <20041217215627.GC8281@uio.no> Mail-Followup-To: pgsql-performance@postgresql.org References: <20041217011853.9E8FF3CADB0@svr1.postgresql.org> <41C2D936.3060901@archonet.com> <87acsdkjte.fsf@stark.xeocode.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87acsdkjte.fsf@stark.xeocode.com> X-Operating-System: Linux 2.6.8.1 on a i686 User-Agent: Mutt/1.5.6+20040907i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200412/229 X-Sequence-Number: 9604 On Fri, Dec 17, 2004 at 10:47:57AM -0500, Greg Stark wrote: >> Must admit this puzzles me. Are you saying you can't saturate your disk I/O? Or >> are you saying other DBMS store records in 0.5 to 0.2 times less space than PG? > I don't know what he's talking about either. Perhaps he's thinking of people > who haven't been running vacuum enough? I'm a bit unsure -- should counting ~3 million rows (no OIDs, PG 7.4, everything in cache, 32-byte rows) take ~3500ms on an Athlon 64 2800+? /* Steinar */ -- Homepage: http://www.sesse.net/