Re: Parallel Index Scans

tushar <tushar.ahuja@enterprisedb.com>

From: tushar <tushar.ahuja@enterprisedb.com>
To: Amit Kapila <amit.kapila16@gmail.com>, Anastasia Lubennikova <lubennikovaav@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Rahila Syed <rahilasyed.90@gmail.com>, Prabhat Sahu <prabhat.sahu@enterprisedb.com>
Date: 2016-12-22T08:05:37Z
Lists: pgsql-hackers

Attachments

On 12/22/2016 09:49 AM, Amit Kapila wrote:
> I think you can focus on the handling of array scan keys for testing.
> In general, one of my colleagues has shown interest in testing this
> patch and I think he has tested as well but never posted his findings.
> I will request him to share his findings and what kind of tests he has
> done, if any.
Sure, We (Prabhat and I) have done some testing for this feature 
internally but never published the test-scripts on this forum. PFA the 
sql scripts ( along with the expected .out files) we have used for 
testing for your ready reference.

In addition we had generated the LCOV (code coverage) report and 
compared the files which are changed for the "Parallel index scan" patch.
You can see the numbers for  "with patch" V/s "Without patch"  (.pdf 
file is attached)

-- 
regards,tushar

Commits

  1. Replace min_parallel_relation_size with two new GUCs.

  2. Factor out logic for computing number of parallel workers.

  3. Support condition variables.

  4. Allow parallel custom and foreign scans.

  5. Add a C API for parallel heap scans.