Re: [GENERAL] Concurrency problem building indexes
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Wes <wespvp(at)syntegra(dot)com>
- Cc: Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at>, "Jim C. Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: [GENERAL] Concurrency problem building indexes
- Date: Tue, 25 Apr 2006 11:50:49 -0400
- Message-id: <19810(dot)1145980249(at)sss(dot)pgh(dot)pa(dot)us>
Wes <wespvp(at)syntegra(dot)com> writes:
> A while back, I saw a posting (I think from Tom) to the effect of index
> creation converging due to disk caching. It was along the lines of the
> slower index would be reading from disk data cached by the first index
> creation's read. When the faster creation went out to read from disk, the
> one reading from memory could catch up. Possible?
There would be some convergence effect while reading the table contents,
but the subsequent sorting and index-writing would be competitive and
ought to diverge again.
regards, tom lane
Home |
Main Index |
Thread Index