From: Marinos J. Yannikos <mjy@geizhals.at>
To: Ron St-Pierre <rstpierre@syscor.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Table UPDATE is too slow
Date: Mon, 06 Sep 2004 01:28:04 +0200
Message-ID: <413BA104.1040508@geizhals.at> (raw)
In-Reply-To: <4134BF36.3000504@syscor.com>
References: <4134BF36.3000504@syscor.com>
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
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-performance@postgresql.org
Cc: mjy@geizhals.at, rstpierre@syscor.com
Subject: Re: Table UPDATE is too slow
In-Reply-To: <413BA104.1040508@geizhals.at>
* 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