Horton

Re: Parallel bitmap heap scan

tushar <tushar.ahuja@enterprisedb.com>

View thread View on postgr.es
From: tushar <tushar.ahuja@enterprisedb.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: Amit Khandekar <amitdkhan.pg@gmail.com>, Amit Kapila <amit.kapila16@gmail.com>, Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-01-12T12:27:21Z
Lists: pgsql-hackers

Attachments

On 01/11/2017 05:33 PM, tushar wrote:
> On 01/10/2017 05:16 PM, Dilip Kumar wrote:
>>   Please try attached patch and confirm from your
>> side.
> Thanks,issue seems to be fixed now. 
Prabhat and I have done some testing for this feature and written few 
testcases.  PFA the sql script(along with the expected .out files)

In addition we have generated the LCOV (code coverage) report and 
compared the files which are changed for the "Parallel Bitmap Heap scan" 
patch.
You can see the numbers for  "with_patch" V/s "with_patch+TestCases"  
(.pdf file is attached)

-- 
regards,tushar
EnterpriseDB  https://www.enterprisedb.com/
The Enterprise PostgreSQL Company

Commits

  1. Pass DSA_ALLOC_HUGE when allocating a shared TIDBitmap.

  2. Support parallel bitmap heap scans.

  3. tidbitmap: Support shared iteration.

  4. Shut down Gather's children before shutting down Gather itself.

  5. Revise the way the element allocator for a simplehash is specified.

  6. Refactor bitmap heap scan estimation of heap pages fetched.

  7. Use more efficient hashtable for tidbitmap.c to speed up bitmap scans.