From: Tom Lane <tgl@sss.pgh.pa.us>
To: Anjan Dave <adave@vantage.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: shared_buffer value
Date: Thu, 15 Jan 2004 19:51:55 -0500
Message-ID: <25927.1074214315@sss.pgh.pa.us> (raw)
In-Reply-To: <203C7FC3FF2D7A4588CE0429A87F3C9A04DE82@vt-pe2550-001.vantage.vantage.com>
References: <203C7FC3FF2D7A4588CE0429A87F3C9A04DE82@vt-pe2550-001.vantage.vantage.com>
"Anjan Dave" <adave@vantage.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, adave@vantage.com
Subject: Re: shared_buffer value
In-Reply-To: <25927.1074214315@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox