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 812305E46E9 for ; Mon, 6 Sep 2004 00:28:08 +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 67610-07 for ; Sun, 5 Sep 2004 23:28:06 +0000 (GMT) Received: from morework.geizhals.at (home.geizhals.at [213.229.14.34]) by svr1.postgresql.org (Postfix) with ESMTP id 6D1435E46F8 for ; Mon, 6 Sep 2004 00:28:02 +0100 (BST) Received: from localhost (morework [127.0.0.1]) by morework.geizhals.at (Postfix) with ESMTP id 9AD87DED21; Mon, 6 Sep 2004 01:28:04 +0200 (CEST) Received: from [192.168.0.3] (chello080110242194.117.11.tuwien.teleweb.at [80.110.242.194]) by morework.geizhals.at (Postfix) with ESMTP; Mon, 6 Sep 2004 01:28:04 +0200 (CEST) Message-ID: <413BA104.1040508@geizhals.at> Date: Mon, 06 Sep 2004 01:28:04 +0200 From: "Marinos J. Yannikos" User-Agent: Mozilla Thunderbird 0.7.3 (Windows/20040803) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ron St-Pierre Cc: 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=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new-20030616-p10 at geizhals.at 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: 200409/32 X-Sequence-Number: 8160 Ron St-Pierre wrote: > We have a web based application with data that is updated daily. The > biggest bottleneck occurs when we try to update > one of the tables. This table contains 58,000 rows and 62 columns, and > EVERY column is indexed. Have you thought of / tried using 2 separate databases or tables and switching between them? Since you seem to be updating all the values, it might be a lot faster to re-create the table from scratch without indexes and add those later (maybe followed by a VACUUM ANALYZE) ... That said, I'm not entirely sure how well postgres' client libraries can deal with tables being renamed while in use, perhaps someone can shed some light on this. Regards, Marinos -- Dipl.-Ing. Marinos Yannikos, CEO Preisvergleich Internet Services AG Obere Donaustraße 63/2, A-1020 Wien Tel./Fax: (+431) 5811609-52/-55