| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | William Yu <wyu(at)talisys(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Slow UPADTE, compared to INSERT |
| Date: | 2003-12-04 22:37:28 |
| Message-ID: | 200312042237.28378.dev@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Thursday 04 December 2003 19:59, William Yu wrote:
> Ivar Zarans wrote:
> > I am experiencing strange behaviour, where simple UPDATE of one field is
> > very slow, compared to INSERT into table with multiple indexes. I have
> > two tables - one with raw data records (about 24000), where one field
>
> In Postgres and any other DB that uses MVCC (multi-version concurrency),
> UPDATES will always be slower than INSERTS. With MVCC, what the DB does
> is makes a copy of the record, updates that record and then invalidates
> the previous record.
[snip]
Yes, but he's seeing 0.25secs to update one row - that's something odd.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2003-12-04 22:45:21 | Re: Slow UPADTE, compared to INSERT |
| Previous Message | Ivar Zarans | 2003-12-04 22:13:12 | Re: Slow UPADTE, compared to INSERT |