| From: | "Marinos J(dot) Yannikos" <mjy(at)geizhals(dot)at> |
|---|---|
| To: | Ron St-Pierre <rstpierre(at)syscor(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Table UPDATE is too slow |
| Date: | 2004-09-05 23:28:04 |
| Message-ID: | 413BA104.1040508@geizhals.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rory Campbell-Lange | 2004-09-05 23:35:05 | Schema and Group permissions question |
| Previous Message | Carlos Correia | 2004-09-05 23:02:24 | Confused with db client encoding |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Foster | 2004-09-06 01:15:24 | Tanking a server with shared memory |
| Previous Message | Pierre-Frédéric Caillaud | 2004-09-05 18:03:04 | Re: fsync vs open_sync |