Re: Using quicksort for every external sort run - Mailing list pgsql-hackers

From Marc Mamin
Subject Re: Using quicksort for every external sort run
Date
Msg-id B6F6FD62F2624C4C9916AC0175D56D88420729E0@jenmbs02.ad.intershop.net
Whole thread Raw
In response to Re: Using quicksort for every external sort run  (Peter Geoghegan <pg@heroku.com>)
Responses Re: Using quicksort for every external sort run  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
>I will sketch a simple implementation of parallel sorting based on the
>patch series that may be workable, and requires relatively little
>implementation effort compare to other ideas that were raised at
>various times:

Hello,

I've only a very superficial understanding on your work,
please apologize if this is off topic or if this was already discussed...

Have you considered performances for cases where multiple CREATE INDEX are running in parallel?
One of our typical use case are large daily tables (50-300 Mio rows) with up to 6 index creations
that start simultaneously.
Our servers have 40-60 GB RAM , ca. 12 CPUs and we set maintenance mem to 1-2 GB for this.
If the create index themselves start using parallelism, I guess that we might need to review our workflow...

best regards,

Marc Mamin


pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: Multi-column distinctness.
Next
From: Peter Geoghegan
Date:
Subject: Re: Using quicksort for every external sort run