MVCC & indexes?

From: Ivan Voras <ivoras(at)fer(dot)hr>
To: pgsql-performance(at)postgresql(dot)org
Subject: MVCC & indexes?
Date: 2006-10-31 21:55:40
Message-ID: 4547C65C.6090208@fer.hr
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Ok, so MVCC is the best thing since a guy put a round stone on a stick
and called it "the wheel", but I've seen several references on this list
about "indexes not being under MVCC" - at least that's how I read it,
the original posts were explaining why indexes can't be used for solving
MIN()/MAX()/COUNT() aggregates. Is this correct?

In particular, I'm trying to find out is there (b)locking involved when
concurrently updating and/or inserting records in an indexed table. My
guess is that, since PG does copy+delete on updating, even updating a
non-indexed field will require fixups in the index tree (to point to the
new record) and thus (b)locking.

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Alvaro Herrera 2006-10-31 22:36:32 Re: MVCC & indexes?
Previous Message Worky Workerson 2006-10-31 21:13:59 Re: Best COPY Performance