Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 64151633F90 for ; Thu, 18 Mar 2010 17:12:27 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 09917-08 for ; Thu, 18 Mar 2010 20:12:11 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ew0-f227.google.com (mail-ew0-f227.google.com [209.85.219.227]) by mail.postgresql.org (Postfix) with ESMTP id C670B6337FF for ; Thu, 18 Mar 2010 17:12:15 -0300 (ADT) Received: by ewy27 with SMTP id 27so2059162ewy.34 for ; Thu, 18 Mar 2010 13:12:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=ozODN3epig+phEKsiunnP84Oz3nZxSM15Kjlqo5ZMO0=; b=d4vBcvFKWeJEjK78bdb61yIzJ/v6UyG9JKLN62vvyf9BLS7aEdR24VJbEsT8vn1WqC PRAvXqMc4bh2QejNQ+NzT5PfbL8/tR8QDyXbqDOQcAwYbvri8Slb7uswFWWlP3eZoKoU B08XQ+O7wyyskLtpWDfbnckDID0Ez7DrvZ1Ys= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=C9K2hTurEdIUZFJxBEcT5n1MsAvgvDyv/lBS8cEWsU16RBln8TYP+d4v2dgAuW5FXK jYg/5Ib2UUwg5S0JP1TybJIWD7Xn+jS8dGJhOH+QkTWhjGs5mJoSItATq/xUoFnSGZHZ mFvlhdnXcudafDcb/mHS7MoNIz9hzFDD5RJJg= Received: by 10.213.24.21 with SMTP id t21mr856131ebb.99.1268943133997; Thu, 18 Mar 2010 13:12:13 -0700 (PDT) Received: from [10.0.1.10] (cpe-24-31-174-25.columbus.res.rr.com [24.31.174.25]) by mx.google.com with ESMTPS id 16sm253555ewy.11.2010.03.18.13.12.10 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 18 Mar 2010 13:12:12 -0700 (PDT) Subject: Re: Building multiple indexes concurrently Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=iso-8859-1 From: Justin Pitts In-Reply-To: <1268860727.19220.1089.camel@hvost> Date: Thu, 18 Mar 2010 16:12:08 -0400 Cc: Greg Smith , Alvaro Herrera , Andres Freund , pgsql-performance@postgresql.org, Rob Wultsch , Tom Lane Content-Transfer-Encoding: quoted-printable Message-Id: <19B3D67A-3182-4323-B70D-CAD612F167A8@gmail.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> <1268860727.19220.1089.camel@hvost> To: Hannu Krosing X-Mailer: Apple Mail (2.1077) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/275 X-Sequence-Number: 38100 It seems to me that a separate partition / tablespace would be a much = simpler approach. On Mar 17, 2010, at 5:18 PM, Hannu Krosing wrote: > On Wed, 2010-03-17 at 16:49 -0400, Greg Smith wrote: >> Alvaro Herrera wrote: >>> Andres Freund escribi=F3: >>>=20 >>>=20 >>>> I find it way much easier to believe such issues exist on a tables = in=20 >>>> constrast to indexes. The likelihood to get sequential accesses on = an index is=20 >>>> small enough on a big table to make it unlikely to matter much. >>>>=20 >>>=20 >>> Vacuum walks indexes sequentially, for one. >>>=20 >>=20 >> That and index-based range scans were the main two use-cases I was=20 >> concerned would be degraded by interleaving index builds, compared = with=20 >> doing them in succession.=20 >=20 > 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 ? >=20 > -=20 > Hannu Krosing http://www.2ndQuadrant.com > PostgreSQL Scalability and Availability=20 > Services, Consulting and Training >=20 >=20 >=20 > --=20 > Sent via pgsql-performance mailing list = (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance