Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id C1D299FB2FE for ; Sat, 3 Mar 2007 02:41:57 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 79515-07 for ; Sat, 3 Mar 2007 02:41:52 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from mxfep04.bredband.com (mxfep04.bredband.com [195.54.107.79]) by postgresql.org (Postfix) with ESMTP id 800E09FB25B for ; Sat, 3 Mar 2007 02:41:53 -0400 (AST) Received: from ironport2.bredband.com ([195.54.107.84] [195.54.107.84]) by mxfep04.bredband.com with ESMTP id <20070303064152.ISMI2732.mxfep04.bredband.com@ironport2.bredband.com> for ; Sat, 3 Mar 2007 07:41:52 +0100 Received: from ua-83-227-204-174.cust.bredbandsbolaget.se (HELO zigo.dhs.org) ([83.227.204.174]) by ironport2.bredband.com with ESMTP; 03 Mar 2007 07:41:52 +0100 Received: from [192.168.0.3] (cosmo.zigo.dhs.org [192.168.0.3]) by zigo.dhs.org (Postfix) with ESMTP id 97D158640; Sat, 3 Mar 2007 07:41:51 +0100 (CET) Message-ID: <45E918AF.7040309@zigo.dhs.org> Date: Sat, 03 Mar 2007 07:41:51 +0100 From: Dennis Bjorklund User-Agent: Thunderbird 1.5.0.10 (X11/20070221) MIME-Version: 1.0 To: Carlos Moreno Cc: PostgreSQL Performance Subject: Re: Upgraded to 8.2.3 --- still having performance issues References: <45E5B7D2.5020306@mochima.com> In-Reply-To: <45E5B7D2.5020306@mochima.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.138 tagged_above=0 required=5 tests=AWL, BAYES_50, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200703/78 X-Sequence-Number: 23483 Carlos Moreno skrev: > The system does very frequent insertions and updates --- the longest > table has, perhaps, some 20 million rows, and it's indexed (the primary > key is the combination of two integer fields). This longest table only > has inserts (and much less frequent selects), at a peak rate of maybe > one or a few insertions per second. One or a few inserts per second doesn't sound like that much. I would have expected it to work. If you can you might want to group several inserts into a single transaction. A standard hint is also to move the WAL onto its own disk. Or get a disk controller with battery backed up ram. But it's hard to say from your description what the bottleneck is and thus hard to give any advice. > Any help/tips/guidance in troubleshooting this issue? It will be > much appreciated! You could try to find specific queries that are slow. Pg can for example log queries for you that run for longer than X seconds. /Dennis