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
On Thu, Nov 11, 2010 at 02:41:12PM +0100, Marc Mamin wrote:
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
On Thu, Nov 11, 2010 at 06:41, Marc Mamin m.ma...@intershop.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?
--
Sent via
@postgresql.org
Subject: Re: [PERFORM] CREATE INDEX as bottleneck
On Thu, Nov 11, 2010 at 06:41, Marc Mamin m.ma...@intershop.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