Re: MVCC cons

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