Re: Building multiple indexes concurrently

From: Justin Pitts <justinpitts(at)gmail(dot)com>
To: Hannu Krosing <hannu(at)2ndquadrant(dot)com>
Cc: Greg Smith <greg(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, pgsql-performance(at)postgresql(dot)org, Rob Wultsch <wultsch(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: Building multiple indexes concurrently
Date: 2010-03-18 21:45:53
Message-ID: D0B205C3-B316-43D0-8D8F-B1FBEFB52287@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Yes.
On Mar 18, 2010, at 5:20 PM, Hannu Krosing wrote:

> On Thu, 2010-03-18 at 16:12 -0400, Justin Pitts wrote:
>> It seems to me that a separate partition / tablespace would be a much simpler approach.
>
> Do you mean a separate partition/ tablespace for _each_ index built
> concurrently ?

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Dave Crooke 2010-03-19 00:08:49 Re: Forcing index scan on query produces 16x faster
Previous Message Hannu Krosing 2010-03-18 21:20:35 Re: Building multiple indexes concurrently