Re: MVCC cons - Mailing list pgsql-general

From Jeff Davis
Subject Re: MVCC cons
Date
Msg-id 1187203532.5203.24.camel@dogma.ljc.laika.com
Whole thread Raw
In response to Re: MVCC cons  ("Merlin Moncure" <mmoncure@gmail.com>)
Responses Re: MVCC cons  ("Scott Marlowe" <scott.marlowe@gmail.com>)
List pgsql-general
On Wed, 2007-08-15 at 07:06 +0530, Merlin Moncure wrote:
> You were half right.  Inserts in PostgreSQL perform similar to other
> databases (or at least, use similar mechanisms).  It's the updates
> that suffer, because this translates to delete + insert essentially.
> Databases that use simple locking strategies can simply update the
> record in place.

I think in some databases that use locking, an INSERT can actually block
a SELECT, and vice-versa. So wouldn't that mean PostgreSQL MVCC is
better for INSERT performance?

Regards,
    Jeff Davis


pgsql-general by date:

Previous
From: "D. Dante Lorenso"
Date:
Subject: SELECT ... FOR UPDATE performance costs? alternatives?
Next
From: Martijn van Oosterhout
Date:
Subject: Re: Best practice for: ERROR: invalid byte sequence for encoding "UTF8"