Re: MVCC & indexes?

Alvaro Herrera wrote:

> Well, there certainly is locking involved in inserting index entries,
> but it's more fine-grained than you seem to think.  Only one page of the
> index is locked at any time, resulting in that typically there's very
> little blocking involved.  Two processes can be inserting into the same
> index concurrently (btree and GiST indexes at least; GiST only gained
> concurrency in a recent release, I don't remember if it was 8.0 or 8.1).

Thank you, this was the bit I was missing. In retrospect, I don't really
know how I came to conclusion the whole index was being locked :(