X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id E83E09DC83F for ; Tue, 14 Feb 2006 12:39:06 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 63096-02 for ; Tue, 14 Feb 2006 12:39:03 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail.logix-tt.com (serval.logix-tt.com [213.239.221.42]) by postgresql.org (Postfix) with ESMTP id 4CE149DC804 for ; Tue, 14 Feb 2006 12:39:03 -0400 (AST) Received: from kingfisher.intern.logix-tt.com (Md10e.m.pppool.de [89.49.209.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.logix-tt.com (Postfix) with ESMTP id 84B66244080; Tue, 14 Feb 2006 17:39:06 +0100 (CET) Received: from [127.0.0.1] (localhost [127.0.0.1]) by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id 3596D18189F88; Tue, 14 Feb 2006 17:39:04 +0100 (CET) Message-ID: <43F207A7.1030303@logix-tt.com> Date: Tue, 14 Feb 2006 17:39:03 +0100 From: Markus Schaber Organization: Logical Tracking and Tracing International AG, Switzerland User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: ken@scottshill.com, pgsql-sql@postgresql.org Subject: Re: Slow update SQL References: <1139881725.3183.2.camel@localhost.localdomain> <20060214021434.GA75196@winnie.fuhr.org> <1139885286.3183.10.camel@localhost.localdomain> <20060214051721.GA76364@winnie.fuhr.org> <1139934917.3083.2.camel@localhost.localdomain> In-Reply-To: <1139934917.3083.2.camel@localhost.localdomain> X-Enigmail-Version: 0.93.0.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.121 required=5 tests=[AWL=0.121] X-Spam-Score: 0.121 X-Spam-Level: X-Archive-Number: 200602/150 X-Sequence-Number: 24160 Hi, Ken, Ken Hill wrote: > Removing the indexes, running the update SQL, and then adding back the > indexes worked much faster. Thank you for you help. It might be a good idea to run VACUUM FULL between updating and reindexing. If you want to CLUSTER on an index, it will be best to create this index first, then CLUSTER the table, and then recreate the other indices. HTH, Markus -- Markus Schaber | Logical Tracking&Tracing International AG Dipl. Inf. | Software Development GIS Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org