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 1198F3CCE4C for ; Fri, 17 Dec 2004 18:37:21 +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 08007-03 for ; Fri, 17 Dec 2004 18:37:10 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id DECDA3CCDF0 for ; Fri, 17 Dec 2004 18:37:10 +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 iBHIarjX021611; Fri, 17 Dec 2004 13:36:53 -0500 (EST) To: Greg Stark Cc: Richard Huxton , David Brown , pgsql-performance@postgresql.org Subject: Re: Seqscan rather than Index In-reply-to: <87zn0cixzy.fsf@stark.xeocode.com> References: <20041217011853.9E8FF3CADB0@svr1.postgresql.org> <41C2D936.3060901@archonet.com> <87acsdkjte.fsf@stark.xeocode.com> <21110.1103305481@sss.pgh.pa.us> <87zn0cixzy.fsf@stark.xeocode.com> Comments: In-reply-to Greg Stark message dated "17 Dec 2004 13:24:33 -0500" Date: Fri, 17 Dec 2004 13:36:52 -0500 Message-ID: <21610.1103308612@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200412/220 X-Sequence-Number: 9595 Greg Stark writes: > Tom Lane writes: >> I think the one effect that's not being modeled is amortization of index >> fetches across successive queries. > And across multiple fetches in a single query, such as with a nested loop. Right, that's effectively the same problem. You could imagine making a special-purpose solution for nestloop queries but I think the issue is more general than that. > It seems like the effective_cache_size parameter should be having some > influence here. But it doesn't :-(. e_c_s is currently only used to estimate amortization of repeated heap-page fetches within a single indexscan. regards, tom lane