From: David Brain <dbrain@bandwidth.com>
To: Bill Moran <wmoran@collaborativefusion.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Potential memory usage issue
Date: Thu, 22 Mar 2007 12:30:22 -0400
Message-ID: <4602AF1E.8000601@bandwidth.com> (raw)
In-Reply-To: <20070322091700.9d1553e6.wmoran@collaborativefusion.com>
References: <460271B9.8050600@bandwidth.com>
<20070322085037.54780906.wmoran@collaborativefusion.com>
<46027F65.9080909@bandwidth.com>
<20070322091700.9d1553e6.wmoran@collaborativefusion.com>
Bill Moran wrote:
>
> Install the pg_bufferstats contrib module and take a look at how shared
> memory is being use. I like to use MRTG to graph shared buffer usage
> over time, but you can just do a SELECT count(*) WHERE NOT NULL to see
> how many buffers are actually in use.
>
Can you explain what you'd use as a diagnostic on this - I just
installed the module - but I'm not entirely clear as to what the output
is actually showing me and/or what would be considered good or bad.
Thanks,
David.
--
David Brain - bandwidth.com
dbrain@bandwidth.com
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: dbrain@bandwidth.com, wmoran@collaborativefusion.com
Subject: Re: Potential memory usage issue
In-Reply-To: <4602AF1E.8000601@bandwidth.com>
* 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