From: Rob Wultsch <wultsch@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Building multiple indexes concurrently
Date: Wed, 17 Mar 2010 08:07:16 -0700
Message-ID: <2c5ef4e31003170807x3f26dd77v57a1631094bc5270@mail.gmail.com> (raw)
In-Reply-To: <27969.1268836243@sss.pgh.pa.us>
References: <2c5ef4e31003161804l5e32ceb9v6b7019118f30004d@mail.gmail.com>
<4BA0AAD1.5040508@2ndquadrant.com>
<27969.1268836243@sss.pgh.pa.us>
On Wed, Mar 17, 2010 at 7:30 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Greg Smith <greg@2ndquadrant.com> writes:
>> Rob Wultsch wrote:
>>> At a minimum I assume that if both of the commands were started at
>>> about the same time they would each scan the table in the same
>>> direction and whichever creation was slower would benefit from most of
>>> the table data it needed being prepopulated in shared buffers. Is this
>>> the case?
>
>> This might be optimistic;
>
> No, it's not optimistic in the least, at least not since we implemented
> synchronized seqscans (in 8.3 or thereabouts).
>
> regards, tom lane
>
Where can I find details about this in the documentation?
--
Rob Wultsch
wultsch@gmail.com
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: wultsch@gmail.com, tgl@sss.pgh.pa.us, greg@2ndquadrant.com
Subject: Re: Building multiple indexes concurrently
In-Reply-To: <2c5ef4e31003170807x3f26dd77v57a1631094bc5270@mail.gmail.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