From: Markus Schaber <schabi@logix-tt.com>
To: ken@scottshill.com
To: pgsql-sql@postgresql.org
Subject: Re: Slow update SQL
Date: Tue, 14 Feb 2006 17:39:03 +0100
Message-ID: <43F207A7.1030303@logix-tt.com> (raw)
In-Reply-To: <1139934917.3083.2.camel@localhost.localdomain>
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>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: schabi@logix-tt.com, ken@scottshill.com
Subject: Re: Slow update SQL
In-Reply-To: <43F207A7.1030303@logix-tt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox