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 169EF5352C for ; Wed, 11 May 2005 01:10:54 -0300 (ADT) 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 31976-03 for ; Wed, 11 May 2005 04:10:44 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 08341531C6 for ; Wed, 11 May 2005 01:10:43 -0300 (ADT) 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 j4B4Aaal029858; Wed, 11 May 2005 00:10:36 -0400 (EDT) To: "Jim C. Nasby" Cc: Joel Fradkin , PostgreSQL Perform Subject: Re: Configing 8 gig box. In-reply-to: <20050510214531.GP31103@decibel.org> References: <006c01c554d9$7d701120$797ba8c0@jfradkin> <20050510214531.GP31103@decibel.org> Comments: In-reply-to "Jim C. Nasby" message dated "Tue, 10 May 2005 16:45:31 -0500" Date: Wed, 11 May 2005 00:10:36 -0400 Message-ID: <29857.1115784636@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.007 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200505/186 X-Sequence-Number: 12350 "Jim C. Nasby" writes: > On Mon, May 09, 2005 at 04:55:53PM -0400, Joel Fradkin wrote: >> Seems to be only using like 360 meg out of 7 gig free (odd thing is I did >> see some used swap 4k out of 1.9) with a bunch of users (this may be normal, >> but it is not going overly fast so thought I would ask). > This is perfectly normal. Each postgresql backend will only report > memory usage roughly equal to shared_buffers plus the size of the code > (16M or so?). If it's in the middle of a sort or vacuum, it will use > more memory. One thing to note is that depending on which Unix variant you are using, top may claim that any particular backend process is using the portion of shared memory that it's actually physically touched. This means that the claimed size of a backend process will grow as it runs (and randomly needs to touch pages that are in different slots of the shared-memory buffers) regardless of any actual objective growth in memory needs. regards, tom lane