From: Greg Smith <greg@2ndquadrant.com>
To: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-performance@postgresql.org, Rob Wultsch <wultsch@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Building multiple indexes concurrently
Date: Wed, 17 Mar 2010 16:49:01 -0400
Message-ID: <4BA1403D.9030402@2ndquadrant.com> (raw)
In-Reply-To: <20100317202401.GC3902@alvh.no-ip.org>
References: <2c5ef4e31003161804l5e32ceb9v6b7019118f30004d@mail.gmail.com>
<2c5ef4e31003170807x3f26dd77v57a1631094bc5270@mail.gmail.com>
<4BA12328.4080803@2ndquadrant.com>
<201003172024.10538.andres@anarazel.de>
<20100317202401.GC3902@alvh.no-ip.org>
Alvaro Herrera wrote:
> Andres Freund escribió:
>
>
>> I find it way much easier to believe such issues exist on a tables in
>> constrast to indexes. The likelihood to get sequential accesses on an index is
>> small enough on a big table to make it unlikely to matter much.
>>
>
> Vacuum walks indexes sequentially, for one.
>
That and index-based range scans were the main two use-cases I was
concerned would be degraded by interleaving index builds, compared with
doing them in succession. I work often with time-oriented apps that
have heavy "give me every record between <a> and <b>" components to
them, and good sequential index performance can be an important
requirement for that kind of application.
--
Greg Smith 2ndQuadrant US Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com www.2ndQuadrant.us
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: greg@2ndquadrant.com, alvherre@commandprompt.com, andres@anarazel.de, wultsch@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: Building multiple indexes concurrently
In-Reply-To: <4BA1403D.9030402@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox