Re: Parallel query execution - Mailing list pgsql-hackers

From Claudio Freire
Subject Re: Parallel query execution
Date
Msg-id CAGTBQpY_iw4-ouQdjg_Gkqkr1-L7aF1Gz-EBT4=FHbrww5W6qg@mail.gmail.com
Whole thread Raw
In response to Re: Parallel query execution  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On Wed, Jan 16, 2013 at 10:04 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
>> Hmm...
>>
>> How about being aware of multiple spindles - so if the requested data
>> covers multiple spindles, then data could be extracted in parallel.  This
>> may, or may not, involve multiple I/O channels?
>
>
>
> effective_io_concurrency does this for bitmap scans.  I thought there was a
> patch in the commitfest to extend this to ordinary index scans, but now I
> can't find it.

I never pushed it to the CF since it interacts so badly with the
kernel. I was thinking about pushing the small part that is a net win
in all cases, the back-sequential patch, but that's independent of any
spindle count. It's more related to rotating media and read request
merges than it is to multiple spindles or parallelization.

The kernel guys basically are waiting for me to patch the kernel. I
think I convinced our IT guy at the office to lend me a machine for
tests... so it might happen soon.



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: log_lock_waits to identify transaction's relation
Next
From: Bruce Momjian
Date:
Subject: Re: Parallel query execution