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(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [GENERAL] Concurrency problem building indexes
Date: 2006-04-25 15:50:49
Message-ID: 19810.1145980249@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ben Clewett 2006-04-25 15:53:32 Installation on Duel-Core Pentium XP
Previous Message Tom Lane 2006-04-25 15:47:19 Re: FOR UPDATE lock problem ?