X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 2D857D1B285 for ; Wed, 19 May 2004 20:19:46 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 54174-04 for ; Wed, 19 May 2004 20:19:28 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 5C0C3D1B34B for ; Wed, 19 May 2004 20:19:25 -0300 (ADT) 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 i4JNJNT1034374 for ; Wed, 19 May 2004 23:19:24 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i4JMoSSe025475 for pgsql-admin@postgresql.org; Wed, 19 May 2004 22:50:28 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.admin Subject: Re: postgresql not using enough memory? Date: Wed, 19 May 2004 18:21:00 -0400 Organization: cbbrowne Computing Inc Lines: 23 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:zcXvWXR8ttDOfDrr21Zz3ksBpOk= To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/203 X-Sequence-Number: 13519 Oops! admin@usachurch.com was seen spray-painting on a wall: > Hello list, > > I know this is a complicated issue, but I'll throw it out there... > Our DB box has 3GB of ram - which is supposed to be used by > postgres. Whenever I use top, it only shows about 800MB being > used with 2.2GB free. What can I do to tell postgres to use more > of that memory - maybe 2GB ? The one change that might be appropriate would be to bump up sort memory. Not too much; 40MB is a terrifically large amount unless you're doing REALLY enormous sorts. Aside from that, it is quite likely that everything is AOK. PostgreSQL benefits from having data in the filesystem cache, and if you up the shared buffer cache, you risk having the commonly-used data stored twice, once in the buffer cache, and once in the filesystem cache, which is wasteful. -- output = ("cbbrowne" "@" "ntlug.org") http://cbbrowne.com/info/rdbms.html Let me control a planet's oxygen supply and I don't care who makes the laws.