Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 67E5D632588 for ; Sat, 10 Apr 2010 15:54:17 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 86079-05 for ; Sat, 10 Apr 2010 18:53:46 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ww0-f46.google.com (mail-ww0-f46.google.com [74.125.82.46]) by mail.postgresql.org (Postfix) with ESMTP id 6907F633605 for ; Sat, 10 Apr 2010 15:54:06 -0300 (ADT) Received: by wwi17 with SMTP id 17so1457465wwi.19 for ; Sat, 10 Apr 2010 11:54:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=hKhYK/HUmPnFzluk648603KMjMnEbsAW6fCR7mNOwj8=; b=vsIX6Gd716SKXMkataOwENjdFw52E2vAWzPF8NpX1QxhexOIpWaF560BZErh+kzqJs vwvpomRv+6/DeraBhOkqh/sVJci7rIY1GApHNVP+Arb2D0hsbUmx0gyKubxMfX7gfOp2 Gm1CflAvUqhC/wUpPm9XnXbvNDAt6VnOcuU2Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=KltljrgVG+DiQyJeV8riNEd3SFQt8XEB7H8ZfiYXm8klwMUAjSpoQNkG9zH1XROAun VSg8SZycu4kRoWvstRFIR+96kcHQoxTf0Cd6uUaoE/vCPjPn7EYHnsn9VtGzaf0Vv6YA WDVr0ruFqPFM7Jp83D5bk4y5jSzAy7h3SdKHE= MIME-Version: 1.0 Received: by 10.216.59.137 with HTTP; Sat, 10 Apr 2010 11:54:04 -0700 (PDT) In-Reply-To: References: <4BBF4FDD.3090008@2ndquadrant.com> Date: Sat, 10 Apr 2010 20:54:04 +0200 Received: by 10.216.89.81 with SMTP id b59mr1005426wef.97.1270925644901; Sat, 10 Apr 2010 11:54:04 -0700 (PDT) Message-ID: Subject: Re: PostgreSQL with Zabbix - problem of newbe From: Krzysztof Kardas To: Scott Marlowe Cc: Merlin Moncure , Greg Smith , pgsql-performance@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=-10 required=5 tests=AWL=0.001 X-Spam-Level: X-Archive-Number: 201004/134 X-Sequence-Number: 38384 2010/4/9 Scott Marlowe : > On Fri, Apr 9, 2010 at 10:30 AM, Merlin Moncure wrot= e: >> On Fri, Apr 9, 2010 at 12:03 PM, Greg Smith wrote= : >>> The main problem with this configuration is that work_mem is set to an >>> unsafe value--1.6GB. =A0With potentially 400 connections and about 2GB = of RAM >>> free after starting the server, work_mem=3D'4MB' is as large as you can= safely >>> set this. >> >> if you need more work_mem for this or that and also need to serve a >> lot of connections, you can always set it locally (1.6GB is still too >> high though -- maybe 64mb if you need to do a big sort or something >> like that). >> >> Another path to take is to install pgbouncer, which at 400 connections >> is worth considering -- but only if your client stack doesn't use >> certain features that require a private database session. =A0zabbix will >> _probably_ work because it is db portable software (still should check >> however). > > Also remember you can set it by user or by db, depending on your > needs. =A0I had a server that had a reporting db and an app db. =A0The ap= p > db was set to 1 or 2 Meg work_mem, and the reporting db that had only > one or two threads ever run at once was set to 128Meg. =A0Worked > perfectly for what we needed. > Thanks for all Your advices. I will set up new parameters on Monday morning and see how it perform. Greetings for all PostgreSQL Team --=20 Krzysztof Kardas