CREATE INDEX as bottleneck

From: "Marc Mamin" <M(dot)Mamin(at)intershop(dot)de>
To: <pgsql-performance(at)postgresql(dot)org>
Subject: CREATE INDEX as bottleneck
Date: 2010-11-11 13:41:12
Message-ID: C4DAC901169B624F933534A26ED7DF31034BB8D1@JENMAIL01.ad.intershop.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hello,

in the last years, we have successfully manage to cope with our data
growth
using partitioning and splitting large aggregation tasks on multiple
threads.
The partitioning is done logically by our applicationn server, thus
avoiding trigger overhead.

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.

With the expected growth, create index will probably become a severe
bottleneck for us.

Is there any chance to see major improvement on it in a middle future ?
I guess the question is naive, but why can't posgres use multiple
threads for large sort operation ?

best regards,

Marc Mamin

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kenneth Marshall 2010-11-11 13:51:22 Re: anti-join chosen even when slower than old plan
Previous Message tv 2010-11-11 08:43:35 Re: Why dose the planner select one bad scan plan.