Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id ADEC32E00FC for ; Thu, 17 Jan 2008 15:08:38 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 39934-06 for ; Thu, 17 Jan 2008 15:08:35 -0400 (AST) Received: from hs-out-2122.google.com (hs-out-0708.google.com [64.233.178.242]) by postgresql.org (Postfix) with ESMTP id 8B3D02E2E7E for ; Thu, 17 Jan 2008 15:08:35 -0400 (AST) Received: by hs-out-2122.google.com with SMTP id k27so652811hsc.3 for ; Thu, 17 Jan 2008 11:08:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=O57shicosGMNjx28MJJwlLNF/DJaIIk2NHjIq0bm35s=; b=tASUxkhd2FLFtGI3w9AKrOfPfRZH37aTaeGDmXelVdTVFSk9r65Olt0bXMCdTTfa6RVIRaWnpOZ1OZI6+raYtJ6S9lxuNc2nXwJAKvPJbL3vQeDY09vKnC2GxO6Ci1aEnImpRrLo/OkZaq5kD+i8/yBblDbrsJl/aNE+FMWzt9c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=csOg4UXnLFjClSfv/ledfUtcLVjkNsg9kjCgQ9xAXrf7A5R43n8rYrjz0SkBXgNcfrgOT0gwgXYshlfEnBVZqSqsQYZHIxOelRPXKy2HRGqu6WDzil7HQQUl5SNxmI980WiN3xDOE8mwnTbsd7lQ/lnLJnst7mvgdkULW7x2XPg= Received: by 10.115.54.1 with SMTP id g1mr2783944wak.132.1200596913311; Thu, 17 Jan 2008 11:08:33 -0800 (PST) Received: by 10.114.133.5 with HTTP; Thu, 17 Jan 2008 11:08:33 -0800 (PST) Message-ID: Date: Thu, 17 Jan 2008 13:08:33 -0600 From: "Scott Marlowe" To: "Jerome Blomart" Subject: Re: pgsql and net-snmp Cc: pgsql-admin@postgresql.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/206 X-Sequence-Number: 27980 On Jan 17, 2008 11:43 AM, Jerome Blomart wrote: > > I am working for a small company offering IT services. > We are in the acceptance stage for a migration of an old UNIX app > managing a huge load of data. > > This acceptance environment is using a VMWARE ESX platform, a jboss as > application server ( java servlet as client application ) > and a pgsql database. As the developpers knew there will be a lot of data, > the server specs are quite high... > ( on RAM space for instance... jboss + pgsql on the same server ). > > As it is ... this environement gets poor results ... You don't mention your I/O subsystem or what type of load you're putting on your database. Lots of disks on a fast RAID controller are often needed to get good db performance. You can use some kind of system monitoring tool that will tell you how much wait time you have versus idle versus user CPU versus system CPU usage. > How-to monitor pgsql ? It's a good idea to keep abreast of what's in the logs, especially ERROR and PANIC type messages. > - database healthiness ? > ------------------------------ > For that part i have only google'd and looked into the pgsql manual ( and > extracted a "SELECT * from pg_stats" from pgsql ). > I could use an extraction script that maps selected data into snmp ( as a > have done for the processes informations ). > But using such a way to pack pgsql's pg_stats into snmp will include regular > query to this table. > > Is there any performance issues generated by this type of monitoring ? Of course there's some load, but it's a small table, and generally speaking this won't be a noticeable load. Also run occasional vacuum verbose against the main db and email the output to yourself for review. Try to keep an eye on how many dead pages your db is collecting.