Re: Performance UPDATE/INSERT - Mailing list pgsql-general

From Alban Hertroys
Subject Re: Performance UPDATE/INSERT
Date
Msg-id 443B81CD.8060902@magproductions.nl
Whole thread Raw
In response to Re: Performance UPDATE/INSERT  ("MG" <pgsql-general@carladata.de>)
Responses Re: Performance UPDATE/INSERT
List pgsql-general
MG wrote:
> I have to improve the performance of the UPDATES and I was wondering why
> the UPDATEs need twice as long as the INSERTs.

IIRC, an UPDATE is a DELETE/INSERT combo. That's because the original
record still needs to be visible to other existing transactions (because
of MVCC). You can't change its data but need to create a new record
instead and mark the original as obsolete.

--
Alban Hertroys
alban@magproductions.nl

magproductions b.v.

T: ++31(0)534346874
F: ++31(0)534346876
M:
I: www.magproductions.nl
A: Postbus 416
    7500 AK Enschede

// Integrate Your World //

pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: pg_restore 7.4.7 locks itself out
Next
From: Alban Hertroys
Date:
Subject: Re: trigger firing order