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-09T11:31:31Z
Lists: pgsql-hackers 
On 01/09/2017 04:36 PM, Dilip Kumar wrote:
> I have taken the latest code, applied all 3 patches and compiled.
> Initdb is working fine for me.
>
> Can you please verify, do you have any extra patch along with my patch?
> Did you properly clean the code?
Thanks Dilip. issue is reproducible  if  we  uses '--enable-cassert' 
switch in the configure. We are able to reproduce it only with 
--enable-cassert' .

-- 
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.