pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Andres Freund <andres@anarazel.de>
To: pgsql-performance@postgresql.org
Cc: Hannu Krosing <hannu@2ndquadrant.com>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: Alvaro Herrera <alvherre@commandprompt.com>
Cc: Rob Wultsch <wultsch@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Building multiple indexes concurrently
Date: Fri, 19 Mar 2010 18:38:08 +0100
Message-ID: <201003191838.09087.andres@anarazel.de> (raw)
In-Reply-To: <1268860727.19220.1089.camel@hvost>
References: <2c5ef4e31003161804l5e32ceb9v6b7019118f30004d@mail.gmail.com>
	<4BA1403D.9030402@2ndquadrant.com>
	<1268860727.19220.1089.camel@hvost>

On Wednesday 17 March 2010 22:18:47 Hannu Krosing wrote:
> 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 ?
ext4 should do that now by allocating the space for the files only after some 
time or uppon things like fsync (xfs does the same).
ext3 has, as far as I know, neither the ability to change allocation size nor 
can do delayed allocation.

Andres



view thread (14+ messages)

Message-ID: <201003191838.09087.andres@anarazel.de>
Permalink:  ../201003191838.09087.andres@anarazel.de/
Also on:    postgresql.org/message-id/201003191838.09087.andres@anarazel.de

 · 

reply

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: andres@anarazel.de, hannu@2ndquadrant.com, greg@2ndquadrant.com, alvherre@commandprompt.com, wultsch@gmail.com, tgl@sss.pgh.pa.us
  Subject: Re: Building multiple indexes concurrently
  In-Reply-To: <201003191838.09087.andres@anarazel.de>

* 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