X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C5BE5D1D313 for ; Wed, 11 Feb 2004 15:54:05 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 69185-05 for ; Wed, 11 Feb 2004 11:54:01 -0400 (AST) Received: from anchor-post-35.mail.demon.net (anchor-post-35.mail.demon.net [194.217.242.85]) by svr1.postgresql.org (Postfix) with ESMTP id 92449D1CCBE for ; Wed, 11 Feb 2004 11:53:56 -0400 (AST) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-35.mail.demon.net with esmtp (Exim 3.35 #1) id 1Aqwga-0004yD-0Z; Wed, 11 Feb 2004 15:54:01 +0000 Received: by mainbox.archonet.com (Postfix, from userid 529) id 20E8A17AD5; Wed, 11 Feb 2004 15:54:00 +0000 (GMT) Received: from client17.archonet.com (client17.archonet.com [192.168.1.17]) by mainbox.archonet.com (Postfix) with ESMTP id 1BCC116729; Wed, 11 Feb 2004 15:53:58 +0000 (GMT) From: Richard Huxton To: stefan bogdan , pgsql-performance@postgresql.org Subject: Re: update performance Date: Wed, 11 Feb 2004 15:53:57 +0000 User-Agent: KMail/1.5 References: <402A3747.8000906@rsb.ro> In-Reply-To: <402A3747.8000906@rsb.ro> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200402111553.57724.dev@archonet.com> X-Bogosity: No, tests=bogofilter, spamicity=0.000000, version=0.15.3 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/128 X-Sequence-Number: 5652 On Wednesday 11 February 2004 14:08, stefan bogdan wrote: > hello > i have postgres 7.3.2.,linux redhat 9.0 > a database,and 20 tables > a lot of fields are char(x) > when i have to make update for all the fields except index > postgres works verry hard > what should i've changed in configuration to make it work faster Stefan - we need more information to help you. We'll want to know: 1. The query being run 2. EXPLAIN ANALYSE ... results for that query 3. The size of the tables involved. 4. That the tables have been VACCUM ANALYSE'd PS - you should upgrade to 7.3.4 (or is it 7.3.5 now?) -- Richard Huxton Archonet Ltd