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 D73E33A43AD for ; Thu, 11 Nov 2004 21:42:06 +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 58118-01 for ; Thu, 11 Nov 2004 21:41:55 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 766B53A425F for ; Thu, 11 Nov 2004 21:41:56 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iABLfp5j011885; Thu, 11 Nov 2004 16:41:51 -0500 (EST) To: Allen Landsidel Cc: pgsql-performance@postgresql.org Subject: Re: Strange (?) Index behavior? In-reply-to: <88f1825a04111113125a0fc443@mail.gmail.com> References: <88f1825a041105095631064cb0@mail.gmail.com> <008401c4c366$127d5260$8300a8c0@solent> <88f1825a04110513028759dd3@mail.gmail.com> <418C1757.70909@ymogen.net> <25492.1099713863@sss.pgh.pa.us> <88f1825a04110523276f83653b@mail.gmail.com> <88f1825a041111082176f13033@mail.gmail.com> <873bzgdsb9.fsf@stark.xeocode.com> <88f1825a04111113125a0fc443@mail.gmail.com> Comments: In-reply-to Allen Landsidel message dated "Thu, 11 Nov 2004 16:12:51 -0500" Date: Thu, 11 Nov 2004 16:41:51 -0500 Message-ID: <11884.1100209311@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200411/189 X-Sequence-Number: 9143 Allen Landsidel writes: > Clustering is really unworkable in this situation. Nonetheless, please do it in your test scenario, so we can see if it has any effect or not. The speed you're getting works out to about 7.2 msec/row, which would be about right if every single row fetch caused a disk seek, which seems improbable unless the table is just huge compared to your available RAM. regards, tom lane