Re: Building multiple indexes concurrently

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: Rob Wultsch <wultsch(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Building multiple indexes concurrently
Date: 2010-03-17 14:30:43
Message-ID: 27969.1268836243@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Greg Smith <greg(at)2ndquadrant(dot)com> writes:
> Rob Wultsch wrote:
>> At a minimum I assume that if both of the commands were started at
>> about the same time they would each scan the table in the same
>> direction and whichever creation was slower would benefit from most of
>> the table data it needed being prepopulated in shared buffers. Is this
>> the case?

> This might be optimistic;

No, it's not optimistic in the least, at least not since we implemented
synchronized seqscans (in 8.3 or thereabouts).

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Brad Nicholson 2010-03-17 14:41:31 Re: Testing FusionIO
Previous Message Tom Lane 2010-03-17 14:27:04 Re: Block at a time ...