On Thu, May 24, 2012 at 11:25 AM, Gurjeet Singh <singh.gurjeet@gmail.com> wrote:
> It'd be great if one of standard utilities like pg_restore supported this,
> by spawning every concurrent index build in separate backends. Just a
> thought.
If parallel restore doesn't already take this into account when doing
job scheduling, that would be a worthwhile improvement to consider.
Personally, I think the big win in this area is likely to be parallel
sort. There may well be some more we can squeeze out of our existing
sort implementation first, and I'm all in favor of that, but
ultimately if you've got 60GB of data to sort and it's all in cache,
you want to be able to use more than one CPU for that.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
