X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id B74B432A05F for ; Mon, 4 Oct 2004 18:33:34 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 91468-02 for ; Mon, 4 Oct 2004 17:33:29 +0000 (GMT) Received: from gp.word-to-the-wise.com (gp.word-to-the-wise.com [64.71.176.18]) by svr1.postgresql.org (Postfix) with ESMTP id B577E32A050 for ; Mon, 4 Oct 2004 18:33:28 +0100 (BST) Received: by gp.word-to-the-wise.com (Postfix, from userid 500) id 451CF90000E; Mon, 4 Oct 2004 10:40:19 -0700 (PDT) Date: Mon, 4 Oct 2004 10:40:19 -0700 From: Steve Atkins To: pgsql-performance@postgresql.org Subject: Performance suggestions for an update-mostly database? Message-ID: <20041004174019.GA25671@gp.word-to-the-wise.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200410/30 X-Sequence-Number: 8506 I'm putting together a system where the operation mix is likely to be >95% update, <5% select on primary key. I'm used to performance tuning on a select-heavy database, but this will have a very different impact on the system. Does anyone have any experience with an update heavy system, and have any performance hints or hardware suggestions? Cheers, Steve