X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx2.hub.org [200.46.204.254]) by postgresql.org (Postfix) with ESMTP id 5E41511F6913 for ; Tue, 18 Apr 2006 19:26:55 -0300 (ADT) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Score: -2.303 X-Spam-Level: X-Spam-Status: No, score=-2.303 required=5 tests=[AWL=0.298, BAYES_00=-2.599, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] Received: from postgresql.org ([200.46.204.71]) by localhost (mx2.hub.org [200.46.204.254]) (amavisd-new, port 10024) with ESMTP id nJahHAdn4M3k for ; Tue, 18 Apr 2006 19:26:54 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id DFB7211F6B6D for ; Tue, 18 Apr 2006 19:26:50 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id k3IMQmcQ019434; Tue, 18 Apr 2006 18:26:49 -0400 (EDT) To: Markus Schaber cc: pgsql-performance@postgresql.org Subject: Re: merge>hash>loop In-reply-to: <4444C4CF.2000106@logix-tt.com> References: <1145029009.3422.31.camel@spectre.intellivid.com> <10000.1145031205@sss.pgh.pa.us> <1145033149.3422.41.camel@spectre.intellivid.com> <11035.1145033929@sss.pgh.pa.us> <4444C4CF.2000106@logix-tt.com> Comments: In-reply-to Markus Schaber message dated "Tue, 18 Apr 2006 12:51:59 +0200" Date: Tue, 18 Apr 2006 18:26:48 -0400 Message-ID: <19433.1145399208@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200604/402 X-Sequence-Number: 18486 Markus Schaber writes: > Hmm, how does effective_cach_size correspond with it? Shouldn't a high > effective_cache_size have a similar effect? It seems reasonable to suppose that effective_cache_size ought to be used as a number indicating how much "stuff" would hang around from query to query. Right now it's not used that way... regards, tom lane