| From: | Ivan Voras <ivoras(at)fer(dot)hr> |
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: MVCC & indexes? |
| Date: | 2006-11-01 12:06:09 |
| Message-ID: | 45488DB1.9010005@fer.hr |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
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 :(
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ben | 2006-11-01 15:49:15 | Re: big transaction slows down over time - but disk seems almost unused |
| Previous Message | Heikki Linnakangas | 2006-11-01 09:39:59 | Re: big transaction slows down over time - but disk seems |