Skip site navigation (1) Skip section navigation (2)

Re: CREATE INDEX as bottleneck

From: "Marc Mamin" <M(dot)Mamin(at)intershop(dot)de>
To: "Alex Hunsaker" <badalex(at)gmail(dot)com>
Cc: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: CREATE INDEX as bottleneck
Date: 2010-11-11 20:05:27
Message-ID: C4DAC901169B624F933534A26ED7DF31034BB8D7@JENMAIL01.ad.intershop.net (view raw or flat)
Thread:
Lists: pgsql-performance
No, CONCURRENTLY is to improve table availability during index creation, but it degrades the performances.

best regards,

Marc Mamin


-----Original Message-----
From: Alex Hunsaker [mailto:badalex(at)gmail(dot)com] 
Sent: Donnerstag, 11. November 2010 19:55
To: Marc Mamin
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] CREATE INDEX as bottleneck

On Thu, Nov 11, 2010 at 06:41, Marc Mamin <M(dot)Mamin(at)intershop(dot)de> wrote:
> There are a few places in our data flow where we have to wait for index
> creation before being able to distribute the process on multiple threads
> again.

Would CREATE INDEX CONCURRENTLY help here?

In response to

pgsql-performance by date

Next:From: Andres FreundDate: 2010-11-11 20:11:04
Subject: Re: anti-join chosen even when slower than old plan
Previous:From: Jon NelsonDate: 2010-11-11 19:52:12
Subject: Re: anti-join chosen even when slower than old plan

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group