From: Richard Huxton <dev@archonet.com>
To: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Re: Slow UPADTE, compared to INSERT
Date: Thu, 4 Dec 2003 22:37:28 +0000
Message-ID: <200312042237.28378.dev@archonet.com> (raw)
In-Reply-To: <bqo3lv$1jdg$1@news.hub.org>
References: <20031204185751.GA15893@alcaron.ee>
<bqo3lv$1jdg$1@news.hub.org>
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
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: dev@archonet.com, wyu@talisys.com
Subject: Re: Slow UPADTE, compared to INSERT
In-Reply-To: <200312042237.28378.dev@archonet.com>
* 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