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 C7E4F3A437E for ; Mon, 1 Nov 2004 01:23:08 +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 39554-01 for ; Mon, 1 Nov 2004 01:22:57 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id E419D3A4368 for ; Mon, 1 Nov 2004 01:23:00 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id iA11MuJ7039809 for ; Mon, 1 Nov 2004 01:22:56 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id iA11C0Jf037666 for pgsql-performance@postgresql.org; Mon, 1 Nov 2004 01:12:00 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.performance Subject: Re: [PATCHES] [HACKERS] ARC Memory Usage analysis Date: Mon, 01 Nov 2004 02:11:45 +0100 Organization: Hub.Org Networking Services Lines: 27 Message-ID: References: <1098471059.20926.49.camel@localhost.localdomain> <41796115.2020501@Yahoo.com> <20041022200955.GC4382@it.is.rice.edu> <417D1D01.3090401@Yahoo.com> <20651.1098720192@sss.pgh.pa.us> <1098780555.6807.136.camel@localhost.localdomain> <74778BDA-27AC-11D9-B369-000D93AE0944@sitening.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@news.hub.org User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en In-Reply-To: <74778BDA-27AC-11D9-B369-000D93AE0944@sitening.com> X-Enigmail-Version: 0.86.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-performance@postgresql.org 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/1 X-Sequence-Number: 8955 Thomas F.O'Connell wrote: > > As a result, I was intending to inflate the value of > effective_cache_size to closer to the amount of unused RAM on some of > the machines I admin (once I've verified that they all have a unified > buffer cache). Is that correct? > Effective cache size is IMHO a "bogus" parameter on postgresql.conf, this because: 1) That parameter is not intended to instruct postgres to use that ram but is only an hint to the engine on what the "DBA" *believe* the OS cache memory for postgres 2) This parameter change only the cost evaluation of plans ( and not soo much ) so don't hope to double this parameter and push postgres to use more RAM. Regards Gaetano Mendola