Received: from localhost (postgresql.org [64.49.215.8])
	by postgresql.org (Postfix) with ESMTP id CE2D34754A7
	for <pgsql-sql@postgresql.org>; Sat, 10 Aug 2002 17:01:30 -0400 (EDT)
Received: from metrony.com (webware.metrony.com [207.159.131.106])
	by postgresql.org (Postfix) with ESMTP id 0FA1A47546C
	for <pgsql-sql@postgresql.org>; Sat, 10 Aug 2002 17:01:30 -0400 (EDT)
Received: from metrony.com (metrony.com [207.159.131.106])
	by metrony.com (8.11.0/8.11.0) with SMTP id g7AL1VT69466
	for <pgsql-sql@postgresql.org>; Sat, 10 Aug 2002 21:01:31 GMT
	(envelope-from aaron@metrony.com)
Received: from 66.108.80.175 (SquirrelMail authenticated user aaron)
	by metrony.com with HTTP; Sat, 10 Aug 2002 21:01:31 -0000 (GMT)
Message-ID: <1633.66.108.80.175.1029013291.squirrel@metrony.com>
Date: Sat, 10 Aug 2002 21:01:31 -0000 (GMT)
Subject: update on a large table
From: "Aaron Held" <aaron@metrony.com>
To: <pgsql-sql@postgresql.org>
In-Reply-To: <1028901334.1423.18.camel@kaos>
References: <1028901334.1423.18.camel@kaos>
X-Priority: 3
Importance: Normal
X-MSMail-Priority: Normal
X-Mailer: SquirrelMail (version 1.2.5)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by AMaViS new-20020517
X-Archive-Number: 200208/178
X-Sequence-Number: 9024

I need to do an UPDATE on a large (100 million record) table.  Is there
any way to speed up the process (Like turning off the transaction log)?

So far postgres has been handling the large database exceptionally well
(large \copy imports and WHERE clauses w/ multiple params) but it is
killing me on UPDATES.  It takes about 4 hours to run an UPDATE (the WHERE
clause is against an INDEX) but about 50 sec for a similar SELECT.

Thank You,
-Aaron Held