Re: Suggestion for concurrent index creation using a single full scan operation - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Suggestion for concurrent index creation using a single full scan operation
Date
Msg-id 20130723132940.GI21996@alap2.anarazel.de
Whole thread Raw
In response to Re: Suggestion for concurrent index creation using a single full scan operation  (Greg Stark <stark@mit.edu>)
List pgsql-hackers
On 2013-07-23 14:17:13 +0100, Greg Stark wrote:
> We already do this in pg_restore by starting multiple worker processes.
> Those processes should get the benefit of synchronised sequential scans.
> 
> The way the api for indexes works y wouldn't really be hard to start
> multiple parallel index builds. I'm not sure how well the pg_restore thing
> works and sometimes the goal isn't to maximise the speed so starting
> multiple processes isn't always ideal.  It might sometimes be interesting
> to be able to do it explicit in a single process.

That's true for normal index modifications, but for ambuild (the initial
index creation function) much less so. That's pretty much a black box
from the outside. It's possible to change that, but it's certainly not
trivial.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Performance Improvement by reducing WAL for Update Operation
Next
From: Andres Freund
Date:
Subject: Re: make --silent