From: Ivan Voras <ivoras@fer.hr>
To: pgsql-performance@postgresql.org
Subject: Re: MVCC & indexes?
Date: Wed, 01 Nov 2006 13:06:09 +0100
Message-ID: <45488DB1.9010005@fer.hr> (raw)
In-Reply-To: <20061031223632.GG12008@alvh.no-ip.org>
References: <4547C65C.6090208@fer.hr>
<20061031223632.GG12008@alvh.no-ip.org>
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 :(
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: ivoras@fer.hr
Subject: Re: MVCC & indexes?
In-Reply-To: <45488DB1.9010005@fer.hr>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox