From: Hannu Krosing <hannu@2ndquadrant.com>
To: Greg Smith <greg@2ndquadrant.com>
Cc: 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 23:18:47 +0200
Message-ID: <1268860727.19220.1089.camel@hvost> (raw)
In-Reply-To: <4BA1403D.9030402@2ndquadrant.com>
References: <2c5ef4e31003161804l5e32ceb9v6b7019118f30004d@mail.gmail.com>
<2c5ef4e31003170807x3f26dd77v57a1631094bc5270@mail.gmail.com>
<4BA12328.4080803@2ndquadrant.com>
<201003172024.10538.andres@anarazel.de>
<20100317202401.GC3902@alvh.no-ip.org>
<4BA1403D.9030402@2ndquadrant.com>
On Wed, 2010-03-17 at 16:49 -0400, Greg Smith wrote:
> 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 guess that tweaking file systems to allocate in bigger chunks help
here ? I know that xfs can be tuned in that regard, but how about other
common file systems like ext3 ?
-
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
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: hannu@2ndquadrant.com, 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: <1268860727.19220.1089.camel@hvost>
* 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