From: | Herouth Maoz <herouth(at)oumail(dot)openu(dot)ac(dot)il> |
---|---|
To: | jim(at)reptiles(dot)org (Jim Mercer) |
Cc: | pgsql-general(at)postgreSQL(dot)org |
Subject: | Re: [GENERAL] slow inserts and updates on large tables |
Date: | 1999-02-17 14:57:24 |
Message-ID: | l03110702b2f0889c1321@[147.233.159.109] |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
At 16:47 +0200 on 17/2/99, Jim Mercer wrote:
> i will test this with my insertama program, but i see some problems with
>this.
>
> firstly, it assumes that all of your applications programs are updated each
> time you modify the structure of the table.
This is true. That's the sacrifice you get for COPY's fast transfers.
> also, it doesn't seem to address the issue of updates, which suffer
>from worse performance than inserts.
Did you try my trick, but without removing the indices? Move the data over
to a temporary table, delete from the original, insert updated data back?
(Assuming you don't have a separate update for each line).
Herouth
--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Davis | 1999-02-17 17:05:36 | RE: [GENERAL] Replication of databases (esp. postgres) |
Previous Message | Jim Mercer | 1999-02-17 14:47:26 | Re: [GENERAL] slow inserts and updates on large tables |