X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 33E18D1B458 for ; Fri, 16 Jan 2004 00:52:24 +0000 (GMT) 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 19836-05 for ; Thu, 15 Jan 2004 20:51:56 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 038F3D1B48D for ; Thu, 15 Jan 2004 20:51:53 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i0G0pupH025928; Thu, 15 Jan 2004 19:51:56 -0500 (EST) To: "Anjan Dave" Cc: pgsql-performance@postgresql.org Subject: Re: shared_buffer value In-reply-to: <203C7FC3FF2D7A4588CE0429A87F3C9A04DE82@vt-pe2550-001.vantage.vantage.com> References: <203C7FC3FF2D7A4588CE0429A87F3C9A04DE82@vt-pe2550-001.vantage.vantage.com> Comments: In-reply-to "Anjan Dave" message dated "Thu, 15 Jan 2004 17:49:28 -0500" Date: Thu, 15 Jan 2004 19:51:55 -0500 Message-ID: <25927.1074214315@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200401/162 X-Sequence-Number: 5337 "Anjan Dave" writes: > Question is, does the 80MB buffer allocation correspond to ~87MB per > postmaster instance? (with about 100 instances of postmaster, that will > be about 100 x 80MB =3D 8GB??) Most likely, top is counting some portion of the shared memory block against each backend process. This behavior is platform-specific, however, and you did not tell us what platform you're on. > Interestingly, at one point, we vacuumed the database, and the size > reported by 'df -k' on the pgsql slice dropped very > significantly...guess, it had been using a lot of temp files? "At one point"? If your setup doesn't include *routine* vacuuming, you are going to have problems with file bloat. This isn't something you can do just when you happen to remember it --- it needs to be driven off a cron job or some such. Or use the contrib autovacuum daemon. You want to vacuum often enough to keep the database size more or less constant. regards, tom lane