CREATE INDEX as bottleneck - Mailing list pgsql-performance

From Marc Mamin
Subject CREATE INDEX as bottleneck
Date
Msg-id C4DAC901169B624F933534A26ED7DF31034BB8D1@JENMAIL01.ad.intershop.net
Whole thread Raw
Responses Re: CREATE INDEX as bottleneck
Re: CREATE INDEX as bottleneck
List 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

pgsql-performance by date:

Previous
From: tv@fuzzy.cz
Date:
Subject: Re: Why dose the planner select one bad scan plan.
Next
From: Kenneth Marshall
Date:
Subject: Re: anti-join chosen even when slower than old plan