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 624515E3F15 for ; Tue, 31 Aug 2004 21:16:47 -0300 (ADT) 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 21408-06 for ; Wed, 1 Sep 2004 00:16:43 +0000 (GMT) Received: from silmaril.syscor.priv (h24-108-208-253.sbm.shawcable.net [24.108.208.253]) by svr1.postgresql.org (Postfix) with ESMTP id AF0755E470A for ; Tue, 31 Aug 2004 21:16:40 -0300 (ADT) Received: from syscor.com (strider.syscor.priv [192.168.1.3]) by silmaril.syscor.priv (8.12.8/8.12.8) with ESMTP id i810GpYe021386 for ; Tue, 31 Aug 2004 17:16:51 -0700 Message-ID: <41351546.7090600@syscor.com> Date: Tue, 31 Aug 2004 17:18:14 -0700 From: Ron St-Pierre User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: pgsql-performance@postgresql.org Subject: Re: Table UPDATE is too slow References: <4134BF36.3000504@syscor.com> In-Reply-To: <4134BF36.3000504@syscor.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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: 200408/492 X-Sequence-Number: 8128 Thanks for everyone's comments (Thomas, Steinar, Frank, Matt, William). Right now I'm bench-marking the time it takes for each step in the end of day update process and then I am going to test a few things: - dropping most indexes, and check the full processing time and see if there is any noticeable performance degradation on the web-end - wrapping the updates in a transaction, and check the timing - combining the two - reviewing my shared_buffers and sort_memory settings Thanks Ron