Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: How to monitor resources on Linux.


  • From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
  • To: John R Allgood <jallgood(at)the-allgoods(dot)net>
  • Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org
  • Subject: Re: How to monitor resources on Linux.
  • Date: Tue, 28 Aug 2007 15:11:44 -0400
  • Message-id: <20070828191143.GE13868@alvh.no-ip.org> <text/plain>

John R Allgood wrote:
> Hey Tom
>
>    Thanks for responding. This issue came around because of a situation 
> yesterday with processes being killed off by the kernel.  I believe my co 
> worker Geof Myers sent a post yesterday and the response was to adjust the 
> vm.commit_memory=2. Several time throughout the day we see memory usage 
> peak and then it will go down. We have multiple postmasters running for 
> each of our division so that I we have a problem with a database it only 
> affects that one. It make it diffucult to tune a system with this many 
> postmasters running. Each database is tuned according to need. We allow 
> anywhere between 5-50 max connections. So what I am looking for is?  

Any of work_mem or maintenance_worm_mem set too high can cause excessive
memory usage.  What do you have these set to?

-- 
Alvaro Herrera                  http://www.amazon.com/gp/registry/5ZYLFMCVHXC
"World domination is proceeding according to plan"        (Andrew Morton)



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group