Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 84C69650E8C for ; Sun, 29 Jun 2008 15:59:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 67675-09 for ; Sun, 29 Jun 2008 15:59:42 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from westnet.com (westnet.com [216.187.52.2]) by postgresql.org (Postfix) with ESMTP id 747C1650DBC for ; Sun, 29 Jun 2008 15:59:44 -0300 (ADT) Received: from westnet.com (localhost [127.0.0.1]) by westnet.com (8.14.0/8.14.0) with ESMTP id m5TIxdrt015097; Sun, 29 Jun 2008 14:59:39 -0400 (EDT) Received: from localhost (gsmith@localhost) by westnet.com (8.14.0/8.13.2/Submit) with ESMTP id m5TIxdwP015094; Sun, 29 Jun 2008 14:59:39 -0400 (EDT) X-Authentication-Warning: westnet.com: gsmith owned process doing -bs Date: Sun, 29 Jun 2008 14:59:39 -0400 (EDT) From: Greg Smith X-X-Sender: gsmith@westnet.com To: "Nikhil G. Daddikar" cc: pgsql-performance@postgresql.org Subject: Re: A guide/tutorial to performance monitoring and tuning In-Reply-To: <4864F7C7.3020901@celoxis.com> Message-ID: References: <4864F7C7.3020901@celoxis.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/211 X-Sequence-Number: 30561 On Fri, 27 Jun 2008, Nikhil G. Daddikar wrote: > I have been searching on the net on how to tune and monitor performance of my > postgresql server but not met with success. A lot of information is vague and > most often then not the answer is "it depends". That's because it does depend. I collect up the best of resources out there and keep track of them at http://wiki.postgresql.org/wiki/Performance_Optimization so if you didn't find that yet there's probably some good ones you missed. Right now I'm working with a few other people to put together a more straightforward single intro guide that should address some of the vagueness you point out here, but that's still a few weeks away from being ready. Monitoring performance isn't really covered in any of this though. Right now the best simple solution out there is probably Nagios with the PostgreSQL plug-in. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD