From: Alvaro Herrera <alvherre@commandprompt.com>
To: Andres Freund <andres@anarazel.de>
Cc: pgsql-performance@postgresql.org, Greg Smith <greg@2ndquadrant.com>
Cc: Rob Wultsch <wultsch@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Building multiple indexes concurrently
Date: Wed, 17 Mar 2010 17:24:01 -0300
Message-ID: <20100317202401.GC3902@alvh.no-ip.org> (raw)
In-Reply-To: <201003172024.10538.andres@anarazel.de>
References: <2c5ef4e31003161804l5e32ceb9v6b7019118f30004d@mail.gmail.com>
<2c5ef4e31003170807x3f26dd77v57a1631094bc5270@mail.gmail.com>
<4BA12328.4080803@2ndquadrant.com>
<201003172024.10538.andres@anarazel.de>
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.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
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: alvherre@commandprompt.com, andres@anarazel.de, greg@2ndquadrant.com, wultsch@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: Building multiple indexes concurrently
In-Reply-To: <20100317202401.GC3902@alvh.no-ip.org>
* 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